AWS CodeBuild
User Guide (API Version 2016-10-06)

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Data Encryption

Encryption is an important part of CodeBuild security. Some encryption, such as for data in-transit, is provided by default and does not require you to do anything. Other encryption, such as for data at-rest, you can configure when you create your project or build.

  • Encryption of data at-rest - Build artifacts, such as a cache, logs, and build results, are encrypted by default using customer master keys (CMKs) for Amazon S3 that are managed by the AWS Key Management Service. If you do not want to use these CMKs, you must create and configure a customer-managed CMK. For more information Creating KMS Keys and AWS Key Management Service Concepts.

    The Amazon Elastic Block Store volumes of your build fleet are encrypted by default using CMKs managed by AWS.

  • Encryption of data in-transit - All communication between customers and CodeBuild and between CodeBuild and its downstream dependencies is protected using SSL connections that are signed using the Signature Version 4 signing process. All CodeBuild endpoints use SHA-256 certificates that are managed by AWS Certificate Manager Private Certificate Authority. For more information, see Signature Version 4 Signing Process and What is ACM PCA.

  • Build artifact encryption - CodeBuild requires access to an AWS KMS CMK in order to encrypt its build output artifacts. By default, CodeBuild uses an AWS Key Management Service CMK for Amazon S3 in your AWS acccount. If you do not want to use this CMK, you must create and configure a customer-managed CMK. For more information Creating KMS Keys.