AWS Proton Documentation

AWS Proton helps platform and DevOps engineers scale their impact by defining and updating infrastructure for self-service deployments. With Proton, users create standard, vetted templates that become the basis for turnkey use by developers in order to meet security, cost, and compliance goals.

Maintaining hundreds or thousands of microservices with continuous integration/continuous delivery (CI/CD) configurations is a challenging task for even the most capable platform teams. AWS Proton helps platform team manage this complexity with a deployment workflow tool optimized to support the full software development lifecycle of modern applications.

AWS Proton helps platform and DevOps engineers create application stack templates. This includes the CI/CD pipeline available to developers, so that to deploy infrastructure for an application they can make a request through the application programming interface (API), command-line interface (CLI), or user interface (UI) to deploy without cutting tickets or manually configuring a pipeline.

You can bring your existing shared resources like an Amazon Virtual Private Cloud (VPC) into AWS Proton. Developers can then deploy to a Proton-managed environment in the same way they deploy to a standard environment.

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

For teams who want to support a variety of use cases with their existing templates. Proton service components can expand the use cases a single template supports. Developers can create a component by providing their infrastructure-as-code template, and then associating the component with their service. 

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 a single account using AWS Proton.

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 such as environments to which you can deploy services. Proton also gives you end-to-end provisioning support, including the ability to deploy infrastructure such as compute, database, and many other resources in a simple, declarative style through AWS CloudFormation.

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

AWS Proton tags provisioned resources with unique identifiers, allowing you to identify provisioned resources coming from an AWS Proton-specific template or environment. This helps you implement tag-based cost management and tag-based access control for AWS Proton resources, including templates, environments, and services. AWS Proton is designed to help you with your tagging process by propagating tags applied to a parent resource down to child resources.

Platform engineers can use AWS Proton to create a stack that is stored and managed in Proton as a reusable version-controlled template. These 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 resources. Platform engineers create stacks for environments and services, and deploy environments. Then, using Proton developers can self-serve to deploy service infrastructure required for their applications.

Customers can use git to manage template updates from their own separate git repository. After creating a template and uploading it to a git repository, Proton can sync and create new versions when changes are committed. 

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