AWS Proton features

AWS Proton makes it easy for platform and DevOps engineers to 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 immediately without needing to cut tickets or manually configure 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 ensure that all deployments are up-to-date.

For team who want to support a wider variety of us 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 help platform operators configure their architecture securely across multiple AWS accounts. You can manage all your multi-account environments and services from a single account using AWS Proton.

Customize your user interface using the familiar 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 all provisioned resources automatically with unique identifiers, allowing you to identify all provisioned resources coming from an AWS Proton-specific template or environment. This makes it easy to implement tag-based cost management and tag-based access control for any AWS Proton resource, including templates, environments, and services. You can streamline and ensure consistency in your tagging process by propagating tags applied to a parent resource down to any of its 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 with everything needed to provision, deploy, and manage a service including compute, networking, code pipeline, security, and monitoring resources. Platform engineers create stacks for environments and services, and typically 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 will automatically sync and create new versions when changes are committed. This reduces manual steps and the chance for human error.

AWS Proton supports updating Proton services using Git. Customers can create a configuration file and choose which branch corresponds to which instance of a Proton service. This enables customers to test changes on a staging branch and push changes to production, all while using Git deployment management.