This library provides an S3 client that supports client-side encryption. For more information and detailed instructions
for how to use this library, refer to the
Amazon S3 Encryption Client Developer Guide.
Testing
Integration tests are included. To test them, certain environment variables need to be set:
AWS_S3EC_TEST_BUCKET - The bucket to write test values to
AWS_S3EC_TEST_KMS_KEY_ID - The key ID for the KMS key used for KMS tests
AWS_S3EC_TEST_KMS_KEY_ALIAS - An alias for the KMS key used for KMS tests. The alias must reference the key ID above.
AWS_REGION - The region the AWS resources (KMS key, S3 bucket) resides e.g. “us-east-1”
To create these resources, refer to the included CloudFormation template (cfn/S3EC-GitHub-CF-Template).
The IAM Role S3ECGithubTestRole SHOULD BE manually customized by you.
Make sure that the repo in the trust policy of the IAM role refers to your fork instead of the aws organization.
Also, remove the ToolsDevelopment clause of the S3ECGithubTestRole‘s AssumeRolePolicyDocument.
NOTE: Your account may incur charges based on the usage of any resources beyond the AWS Free Tier.
If you have forked this repo, there are additional steps required.
You will need to configure your fork’s Github Actions settings to be able to run CI:
Under Settings -> Actions -> General -> Workflow permissions, ensure “Read and write permissions” is selected.
Under Settings -> Security -> Secrets and variables -> Actions -> Repository secrets, add new secret:
CI_AWS_ACCOUNT_ID - the AWS account ID which contains the required resources, e.g. 111122223333.
The other values are added as variables (by clicking the “New repository variable” button):
CI_AWS_ROLE - the IAM role to assume during CI, e.g. S3EC-GitHub-test-role. It must exist in the above account and have permission to call S3 and KMS.
CI_AWS_REGION - the AWS region which contains the required resources, e.g. us-west-2.
CI_S3_BUCKET - the S3 bucket to use, e.g. s3ec-github-test-bucket.
CI_KMS_KEY_ID - the short KMS key ID to use, e.g. c3eafb5f-e87d-4584-9400-cf419ce5d782.
CI_KMS_KEY_ALIAS - the KMS key alias to use, e.g. S3EC-Github-KMS-Key. Note that the alias must reference the key ID above.
CI_ALT_ROLE - an alternate role to use that is different from the role defined above. It must have permission to use the KMS key below and the S3 bucket above.
CI_ALT_KMS_KEY_ID- the KMS key of an alternate KMS key to use. The alternate role must have access to use the key and the role for CI_AWS_ROLE must not have access to the key.
Migration
This version of the library supports reading encrypted objects from previous versions.
It also supports writing objects with non-legacy algorithms.
The list of legacy modes and operations is provided below.
However, this version does not support V2’s Unencrypted Object Passthrough.
This library can only read encrypted objects from S3,
unencrypted objects MUST be read with the base S3 Client.
Client Configuration
The S3 Encryption Client uses “wrapped” clients to make its requests to S3 and/or KMS.
You can configure each client independently, or apply a “top-level” configuration which is applied to all wrapped clients.
Refer to the Client Configuration Example in the Examples directory for examples of each configuration method.
Examples
V3 to V4 Migration
V4 introduces enhanced security with commitment policies. To migrate from V3:
Amazon S3 Encryption Client
This library provides an S3 client that supports client-side encryption. For more information and detailed instructions for how to use this library, refer to the Amazon S3 Encryption Client Developer Guide.
Testing
Integration tests are included. To test them, certain environment variables need to be set:
AWS_S3EC_TEST_BUCKET- The bucket to write test values toAWS_S3EC_TEST_KMS_KEY_ID- The key ID for the KMS key used for KMS testsAWS_S3EC_TEST_KMS_KEY_ALIAS- An alias for the KMS key used for KMS tests. The alias must reference the key ID above.AWS_REGION- The region the AWS resources (KMS key, S3 bucket) resides e.g. “us-east-1”To create these resources, refer to the included CloudFormation template (cfn/S3EC-GitHub-CF-Template). The IAM Role
S3ECGithubTestRoleSHOULD BE manually customized by you. Make sure that the repo in the trust policy of the IAM role refers to your fork instead of theawsorganization. Also, remove theToolsDevelopmentclause of theS3ECGithubTestRole‘sAssumeRolePolicyDocument. NOTE: Your account may incur charges based on the usage of any resources beyond the AWS Free Tier.If you have forked this repo, there are additional steps required. You will need to configure your fork’s Github Actions settings to be able to run CI:
Under Settings -> Actions -> General -> Workflow permissions, ensure “Read and write permissions” is selected. Under Settings -> Security -> Secrets and variables -> Actions -> Repository secrets, add new secret:
CI_AWS_ACCOUNT_ID- the AWS account ID which contains the required resources, e.g. 111122223333.The other values are added as variables (by clicking the “New repository variable” button):
CI_AWS_ROLE- the IAM role to assume during CI, e.g. S3EC-GitHub-test-role. It must exist in the above account and have permission to call S3 and KMS.CI_AWS_REGION- the AWS region which contains the required resources, e.g. us-west-2.CI_S3_BUCKET- the S3 bucket to use, e.g. s3ec-github-test-bucket.CI_KMS_KEY_ID- the short KMS key ID to use, e.g. c3eafb5f-e87d-4584-9400-cf419ce5d782.CI_KMS_KEY_ALIAS- the KMS key alias to use, e.g. S3EC-Github-KMS-Key. Note that the alias must reference the key ID above.CI_ALT_ROLE- an alternate role to use that is different from the role defined above. It must have permission to use the KMS key below and the S3 bucket above.CI_ALT_KMS_KEY_ID- the KMS key of an alternate KMS key to use. The alternate role must have access to use the key and the role forCI_AWS_ROLEmust not have access to the key.Migration
This version of the library supports reading encrypted objects from previous versions. It also supports writing objects with non-legacy algorithms. The list of legacy modes and operations is provided below.
However, this version does not support V2’s Unencrypted Object Passthrough. This library can only read encrypted objects from S3, unencrypted objects MUST be read with the base S3 Client.
Client Configuration
The S3 Encryption Client uses “wrapped” clients to make its requests to S3 and/or KMS. You can configure each client independently, or apply a “top-level” configuration which is applied to all wrapped clients. Refer to the Client Configuration Example in the Examples directory for examples of each configuration method.
Examples
V3 to V4 Migration
V4 introduces enhanced security with commitment policies. To migrate from V3:
For detailed migration guidance and step-by-step examples, refer to the Migration Examples. For more information, refer to the Developer Guide.
V2 KMS Materials Provider to V4
V2 AES Key Materials Provider to V4
V2 RSA Key Materials Provider to V4
V1 Key Materials Provider to V4
To allow legacy modes (for decryption only), you must explicitly allow them
Legacy Algorithms and Modes
Content Encryption
Key Wrap Encryption
Security
See CONTRIBUTING for more information.
License
This project is licensed under the Apache-2.0 License.