Skip to content

Commit 24c7a32

Browse files
committed
1 parent 5cf5942 commit 24c7a32

File tree

1 file changed

+1
-1
lines changed
  • src/connections/storage/catalog/amazon-s3

1 file changed

+1
-1
lines changed

src/connections/storage/catalog/amazon-s3/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ This section contains information for enabling encryption on your S3 bucket.
7878
Segment supports optional, S3-managed Server-Side Encryption, which you can disable or enable from the Destination Configuration UI. By default, the destination now automatically enables encryption, and Segment recommends that you continue to encrypt.
7979
If you've had the S3 destination enabled since before October 2017, you might need to enable encryption manually on your bucket.
8080

81-
While most client libraries transparently decrypt the file when fetching it, you should make sure that any applications that are consume data in the S3 bucket are ready to decrypt the data before you enable this feature. When you're ready, you can enable encryption from the setting in the destination configuration UI.
81+
While most client libraries transparently decrypt the file when fetching it, you should make sure that any applications that consume data in the S3 bucket are ready to decrypt the data before you enable this feature. When you're ready, you can enable encryption from the setting in the destination configuration UI.
8282

8383
### Server-Side Encryption with AWS KMS-Managed Keys (SSE-KMS)
8484
Segment can also write to S3 buckets with Default Encryption set to AWS-KMS. This ensures that objects written to your bucket are encrypted using customer managed keys created in your AWS Key Management Service (KMS).

0 commit comments

Comments
 (0)