Data Protection in Amazon Kinesis Data Analytics for Apache Flink - Amazon Kinesis Data Analytics

Data Protection in Amazon Kinesis Data Analytics for Apache Flink

You can protect your data using tools that are provided by AWS. Kinesis Data Analytics can work with services that support encrypting data, including Kinesis Data Analytics, Kinesis Data Firehose, and Amazon S3.

Data Encryption in Kinesis Data Analytics for Apache Flink

Encryption at Rest

Note the following about encrypting data at rest with Kinesis Data Analytics for Apache Flink:

  • You can encrypt data on the incoming Kinesis data stream using StartStreamEncryption. For more information, see What Is Server-Side Encryption for Kinesis Data Streams?.

  • Output data can be encrypted at rest using Kinesis Data Firehose to store data in an encrypted Amazon S3 bucket. You can specify the encryption key that your Amazon S3 bucket uses. For more information, see Protecting Data Using Server-Side Encryption with AWS KMS–Managed Keys (SSE-KMS).

  • A Kinesis Data Analytics for Apache Flink application can read from any streaming source, and write to any streaming or database destination. Ensure that your sources and destinations encrypt all data in transit and data at rest.

  • Your application's code is encrypted at rest.

  • Durable application storage is encrypted at rest.

  • Running application storage is encrypted at rest.

Encryption In Transit

Kinesis Data Analytics encrypts all data in transit. Encryption in transit is enabled for all Kinesis Data Analytics applications and cannot be disabled.

Kinesis Data Analytics encrypts data in transit in the following scenarios:

  • Data in transit from Kinesis Data Streams to Kinesis Data Analytics.

  • Data in transit between internal components within Kinesis Data Analytics.

  • Data in transit between Kinesis Data Analytics and Kinesis Data Firehose.

Key Management

Data encryption in Kinesis Data Analytics uses service-managed keys. Customer-managed keys are not supported.