Data protection in Amazon CodePipeline - Amazon CodePipeline
Internetwork traffic privacyEncryption at restEncryption in transit
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 protection in Amazon CodePipeline

The Amazon shared responsibility model applies to data protection in Amazon CodePipeline. As described in this model, Amazon is responsible for protecting the global infrastructure that runs all of the Amazon Web Services Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the Amazon Web Services that you use. For more information about data privacy, see the Data Privacy FAQ.

For data protection purposes, we recommend that you protect Amazon Web Services account credentials and set up individual users with Amazon IAM Identity Center or Amazon Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:

  • Use multi-factor authentication (MFA) with each account.

  • Use SSL/TLS to communicate with Amazon resources. We require TLS 1.2 and recommend TLS 1.3.

  • Set up API and user activity logging with Amazon CloudTrail.

  • Use Amazon encryption solutions, along with all default security controls within Amazon Web Services.

  • Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.

  • If you require FIPS 140-2 validated cryptographic modules when accessing Amazon through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-2.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a Name field. This includes when you work with CodePipeline or other Amazon Web Services using the console, API, Amazon CLI, or Amazon SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

The following security best practices also address data protection in CodePipeline:

Internetwork traffic privacy

Amazon VPC is an Amazon Web Service that you can use to launch Amazon resources in a virtual network (virtual private cloud) that you define. CodePipeline supports Amazon VPC endpoints powered by Amazon PrivateLink, an Amazon technology that facilitates private communication between Amazon Web Services using an elastic network interface with private IP addresses. This means you can connect directly to CodePipeline through a private endpoint in your VPC, keeping all traffic inside your VPC and the Amazon network. Previously, applications running inside a VPC required internet access to connect to CodePipeline. With a VPC, you have control over your network settings, such as:

  • IP address range,

  • Subnets,

  • Route tables, and

  • Network gateways.

To connect your VPC to CodePipeline, you define an interface VPC endpoint for CodePipeline. This type of endpoint makes it possible for you to connect your VPC to Amazon Web Services. The endpoint provides reliable, scalable connectivity to CodePipeline without requiring an internet gateway, network address translation (NAT) instance, or VPN connection. For information about setting up a VPC, see the VPC User Guide.

Encryption at rest

Data in CodePipeline is encrypted at rest using Amazon KMS keys. Code artifacts are stored in a customer-owned S3 bucket and encrypted with either the Amazon managed key or a customer managed key. For more information, see Configure server-side encryption for artifacts stored in Amazon S3 for CodePipeline.

Encryption in transit

All service-to-service communication is encrypted in transit using SSL/TLS.