Examples of using Server-side encryption in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
API Support for Server-Side Encryption.
Server-side encryption protects data at rest.
Enables you to set server-side encryption on the file.
A status of NOT-SSEmeans that the object is not encrypted with server-side encryption.
To learn more about server-side encryption, see PUT Object.
Server-side encryption enables you to request Amazon S3 to encrypt your data at rest.
The AWS Mobile SDK for iOS supports server-side encryption of Amazon S3 data.
Configure Server-Side Encryption for Artifacts Stored in Amazon S3 for AWS CodePipeline.
Use the SSESpecification property to specify the settings to enable server-side encryption.
Configure Server-Side Encryption for S3 Buckets When Using AWS CloudFormation or the CLI.
You can also use the AWS Management Consoleto upload objects and request server-side encryption.
You can also request server-side encryption when uploading objects using AWS Management Console.
The following example creates an EmrCluster activity with server-side encryption disabled.
If you need server-side encryption for all of the objects that are stored in a bucket, use a bucket policy.
Specifies whether Amazon S3 replicates objects created with server-side encryption using an AWS KMS-managed key.
For more information about server-side encryption and AWS KMS, see Protecting Data UsingServer-Side Encryption and.
Contains the status of whether Amazon S3 replicates objects created with server-side encryption using an AWS KMS-managed key.
Objects created with server-side encryption using AWS KMS-managed encryption(SSE-KMS) keys, unless you explicitly enable this option.
You might have objects in your source bucket that are created using server-side encryption using AWS KMS-managed keys.
The objects are encrypted using server-side encryption with either Amazon S3-managed keys(SSE-S3) or AWS KMS-managed keys SSE-KMS.
The SSESpecification property is part of the AWS::DynamoDB::Table resource that specifies the settings to enable server-side encryption.
AWS CloudFormation creates the buckets with server-side encryption enabled by default, thereby encrypting all objects stored in the bucket.
For more information about Amazon S3 storage classes and encryption, see Storage Classes and Protecting Data Using Server-Side Encryption.
When you upload large objects using the multipart upload API,you can specify server-side encryption for the objects that you are uploading, as follows.
If server-side encryption with a customer-provided encryption key was requested, the response will include this header, which confirms the encryption algorithm that was used.
You can also configure to encrypt S3 inventory with server-side encryption(SSE) or SSE-KMS so that all inventory files are encrypted accordingly.
Use Server-Side Encryption with AWS KMS-Managed Keys(SSE-KMS)- Similar to SSE-S3, but with some additional benefits along with some additional charges for using this service.
Currently, Amazon S3 supports only thefilter that you can specify for objects created with server-side encryption using an AWS KMS-managed key.
By default, AWS CodePipeline uses server-side encryption with the AWS KMS-managed keys(SSE-KMS) using the default key for Amazon S3 the aws/s3 key.
Change the encryption method for your log files from server-side encryption with Amazon S3-managed encryption keys(SSE-S3) to server-side encryption with AWS KMS-managed keys SSE-KMS.