Data encryption - AWS CodeBuild

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 AWS 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 AWS Key Management Service concepts in the AWS Key Management Service User Guide.

    The Amazon Elastic Block Store volumes of your build fleet are encrypted by default using AWS 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 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 a KMS key in order to encrypt its build output artifacts. By default, CodeBuild uses an AWS managed key Amazon S3. If you do not want to use this AWS managed key, you must create and configure a customer managed key. For more information Creating keys.