Hidden Features and Shortcuts for AWS CodePipeline

Welcome to this tutorial on hidden features and shortcuts for AWS CodePipeline. CodePipeline is a powerful continuous integration and continuous delivery (CI/CD) service provided by Amazon Web Services (AWS). In this tutorial, we will uncover some lesser-known features and handy shortcuts that can enhance your productivity and streamline your CI/CD workflows.


Before we begin, ensure that you have the following:

  • An AWS account
  • Basic knowledge of AWS CodePipeline
  • Experience with creating and managing CodePipeline pipelines

Hidden Features and Shortcuts

1. Keyboard Shortcuts in the CodePipeline Console

The CodePipeline console provides several keyboard shortcuts to navigate and interact with your pipelines more efficiently. Here are a few examples:

  • Shift + D - Toggles the pipeline details pane
  • Shift + F - Filters pipelines based on a specific string
  • Shift + R - Refreshes the console view
  • Shift + B - Builds the pipeline and starts the execution

2. Pipeline Execution ID Placeholder

When configuring actions or settings that require a unique identifier for the current pipeline execution, you can use the {codepipeline:execution-id} placeholder. For example:

aws codepipeline start-pipeline-execution \ --name MyPipeline \ --client-request-token "MyToken-{codepipeline:execution-id}"

This ensures that each pipeline execution receives a unique token based on the execution ID, which can be useful for tracing and identification purposes.

Common Mistakes to Avoid

  • Not exploring the available keyboard shortcuts in the CodePipeline console
  • Missing out on productivity-enhancing features due to lack of awareness
  • Not utilizing placeholders or dynamic values to automate repetitive tasks
  • Overlooking advanced configuration options and settings
  • Not taking advantage of integrations with other AWS services

Frequently Asked Questions

Q1: Can I use custom plugins or extensions with CodePipeline?

A1: No, CodePipeline does not support custom plugins or extensions. However, you can integrate with other AWS services or use AWS Lambda to extend functionality.

Q2: Can I trigger a pipeline execution from an external event?

A2: Yes, you can use AWS CloudWatch Events or AWS Lambda to trigger a pipeline execution based on various events, such as code commits, S3 bucket changes, or even scheduled intervals.

Q3: How can I share artifacts between pipelines?

A3: You can use the outputArtifacts property to specify the artifacts that should be made available for other pipelines. These artifacts can be consumed by downstream pipelines for further processing.

Q4: Can I run CodePipeline in a VPC?

A4: No, CodePipeline does not run within a VPC. It interacts with various AWS services that reside outside the VPC boundaries.

Q5: Is it possible to roll back a deployment in CodePipeline?

A5: CodePipeline itself does not provide built-in rollback functionality. However, you can design your pipeline to trigger a rollback action in case of deployment failures using AWS services like AWS CloudFormation.


In this tutorial, we uncovered hidden features and shortcuts for AWS CodePipeline. By leveraging keyboard shortcuts in the console and utilizing placeholders for dynamic values, you can enhance your productivity and automate repetitive tasks. We also discussed common mistakes to avoid and answered frequently asked questions. Now you have the knowledge to uncover hidden gems in CodePipeline and streamline your CI/CD workflows.