General integrations with CodePipeline - Amazon CodePipeline
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).

General integrations with CodePipeline

The following Amazon Web Service integrations are not based on CodePipeline action types.

Amazon CloudWatch

Amazon CloudWatch monitors your Amazon resources.

Learn more:

Amazon EventBridge Amazon EventBridge is a web service that detects changes in your Amazon Web Services based on rules that you define and invokes an action in one or more specified Amazon Web Services when a change occurs.
Amazon Cloud9

Amazon Cloud9 is an online IDE, which you access through your web browser. The IDE offers a rich code editing experience with support for several programming languages and runtime debuggers, as well as a built-in terminal. In the background, an Amazon EC2 instance hosts an Amazon Cloud9 development environment. For more information, see the Amazon Cloud9 User Guide.

Learn more:

Amazon CloudTrail

CloudTrail captures Amazon API calls and related events made by or on behalf of an Amazon account and delivers log files to an Amazon S3 bucket that you specify. You can configure CloudTrail to capture API calls from the CodePipeline console, CodePipeline commands from the Amazon CLI, and from the CodePipeline API.

Learn more:

AWS CodeStar Notifications You can set up notifications to make users aware of important changes, such as when a pipeline starts execution. For more information, see Create a notification rule.
Amazon Key Management Service

Amazon KMS is a managed service that makes it easy for you to create and control the encryption keys used to encrypt your data. By default, CodePipeline uses Amazon KMS to encrypt artifacts for pipelines stored in Amazon S3 buckets.

Learn more:

For an Amazon KMS key, you can use the key ID, the key ARN, or the alias ARN.

Note

Aliases are recognized only in the account that created the KMS key. For cross-account actions, you can only use the key ID or key ARN to identify the key. Cross-account actions involve using the role from the other account (AccountB), so specifying the key ID will use the key from the other account (AccountB).