AWS Proton Documentation

AWS Proton helps developers deploy code using containers and serverless technologies, using management tools, and governance.


AWS Proton is designed for platform teams to create application stacks that include the CI/CD pipeline available to developers so they can make a request through the API, CLI, or user interface to deploy an application.

Customer-managed environments

You can bring your existing shared resources into AWS Proton without having to recreate the infrastructure. This is transparent for developers, who can deploy to a customer-managed environment in the same way they deploy to a standard environment.

Flexible definitions

Create service templates with or without a pipeline. AWS Proton gives teams greater flexibility in defining, provisioning, and deploying their services. Developers only need to provide the required inputs for their service, and platform teams can leverage AWS Proton’s central management capabilities to help them keep deployments are up-to-date.

Multi-account support

AWS Proton supports multi-account infrastructures, which helps platform operators configure their architecture across multiple AWS accounts. You can manage your multi-account environments and services from one single account using AWS Proton.

Self-service interface

Customize your user interface using the AWS Management Console or CLI. The AWS Proton interface guides you through the process of creating and deploying shared resources as environments that services can be deployed to. You have end-to-end provisioning support, including the ability to deploy infrastructure through AWS CloudFormation, including compute, database, and many other resources in a simple, declarative style.


AWS Proton supports versioning of infrastructure templates and provides developers with updates for out-of-date deployments.

Tagging capabilities

Establish tagging and tag-based access control for AWS Proton resources, including templates, environments, and services. AWS Proton is designed to help you with consistency in your tagging process by propagating tags applied to a parent resource down to child resources. AWS Proton also tags all provisioned resources with unique identifiers, allowing you to identify provisioned resources that come from an AWS Proton-specific template or environment.

Template management

Platform teams use AWS Proton to create a stack that is presented to developers as a reusable version-controlled template. The stacks are defined using infrastructure as code in a simple, declarative style to help you with provisioning, deploying, and managing a service, including compute, networking, code pipeline, security, and monitoring. Developers log into the AWS Proton console to use published AWS Proton stacks to help automate infrastructure provisioning and deploy their application code. Developers using AWS Proton don’t need to separately provision the components of their stack (like shared resources, continuous integration/continuous deployment (CI/CD) pipeline, and observability tools).

Additional Information

For additional information about service controls, security features and functionalities, including, as applicable, information about storing, retrieving, modifying, restricting, and deleting data, please see This additional information does not form part of the Documentation for purposes of the AWS Customer Agreement available at, or other agreement between you and AWS governing your use of AWS’s services.