Data encryption - Amazon CodeBuild
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

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, exported raw test report data files, and build results, are encrypted by default using Amazon managed keys. If you do not want to use these KMS keys, you must create and configure a customer managed key. For more information Creating KMS Keys and Amazon Key Management Service concepts in the Amazon Key Management Service User Guide.

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

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

  • Build artifact encryption - The CodeBuild service role associated with the build project requires access to a KMS key in order to encrypt its build output artifacts. By default, CodeBuild uses an Amazon managed key for Amazon S3 in your Amazon account. If you do not want to use this Amazon managed key, you must create and configure a customer managed key. For more information, see Encrypt build outputs and Creating keys in the Amazon KMS Developer Guide.