paws.analytics (version 0.1.0)

firehose_start_delivery_stream_encryption: Enables server-side encryption (SSE) for the delivery stream

Description

Enables server-side encryption (SSE) for the delivery stream.

Usage

firehose_start_delivery_stream_encryption(DeliveryStreamName)

Arguments

DeliveryStreamName

[required] The name of the delivery stream for which you want to enable server-side encryption (SSE).

Request syntax

svc$start_delivery_stream_encryption(
  DeliveryStreamName = "string"
)

Details

This operation is asynchronous. It returns immediately. When you invoke it, Kinesis Data Firehose first sets the status of the stream to ENABLING, and then to ENABLED. You can continue to read and write data to your stream while its status is ENABLING, but the data is not encrypted. It can take up to 5 seconds after the encryption status changes to ENABLED before all records written to the delivery stream are encrypted. To find out whether a record or a batch of records was encrypted, check the response elements PutRecordOutput\$Encrypted and PutRecordBatchOutput\$Encrypted, respectively.

To check the encryption state of a delivery stream, use DescribeDeliveryStream.

You can only enable SSE for a delivery stream that uses DirectPut as its source.

The StartDeliveryStreamEncryption and StopDeliveryStreamEncryption operations have a combined limit of 25 calls per delivery stream per 24 hours. For example, you reach the limit if you call StartDeliveryStreamEncryption 13 times and StopDeliveryStreamEncryption 12 times for the same delivery stream in a 24-hour period.