End of support notice: On October 7, 2026, AWS will end support for AWS Proton. After October 7, 2026, you will no longer be able to access the AWS Proton console or AWS Proton resources. Your deployed infrastructure will remain intact. For more information, see [AWS Proton Service Deprecation and Migration Guide](https://docs.aws.amazon.com/proton/latest/userguide/proton-end-of-support.html).
# What is AWS Proton?
**AWS Proton is:**
+ **Automated infrastructure as code provisioning and deployment of serverless and container-based applications**
The AWS Proton service is a two-pronged automation framework. As an administrator, you create *versioned service templates* that define standardized infrastructure and deployment tooling for serverless and container-based applications. As an application developer, you can select from the available *service templates* to automate your application or service deployments.
AWS Proton identifies all existing *service instances* that are using an outdated template version for you. As an administrator, you can request AWS Proton to upgrade them with one click.
+ **Standardized infrastructure**
Platform teams can use AWS Proton and versioned infrastructure as code templates. They can use these templates to define and manage standard application stacks that contain the architecture, infrastructure resources, and the CI/CD software deployment pipeline.
+ **Deployments integrated with CI/CD**
When developers use the AWS Proton self-service interface to select a *service template*, they're selecting a standardized application stack definition for their code deployments. AWS Proton automatically provisions the resources, configures the CI/CD pipeline, and deploys the code into the defined infrastructure.
## AWS Proton for platform teams
As an administrator, you or members of your platform team, create *environment templates* and *service templates* containing infrastructure as code. The *environment template* defines shared infrastructure used by multiple applications or resources. The *service template* defines the type of infrastructure that's needed to deploy and maintain a single application or microservice in an *environment*. An AWS Proton *service* is an instantiation of a *service template*, which normally includes several *service instances* and a *pipeline*. An AWS Proton *service instance* is an instantiation of a *service template* in a specific *environment*. You or others in your team can specify which *environment templates* are compatible with a given *service template*. For more information about *templates*, see [AWS Proton templates](ag-templates.md).
You can use the following infrastructure as code providers with AWS Proton:
+ [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html)
+ [Terraform](https://www.terraform.io/)
## AWS Proton for developers
As an application developer, you select a standardized *service template* that AWS Proton uses to create a *service* that deploys and manages your application in a *service instance*. An AWS Proton *service* is an instantiation of a *service template*, which normally includes several *service instances* and a *pipeline*.
## AWS Proton workflow
The following diagram is a visualization of the main AWS Proton concepts discussed in the preceding paragraph. It also offers a high-level overview of what constitutes a simple AWS Proton workflow.
![\[A diagram that describes the main AWS Proton concepts discussed in the preceding paragraph. It also offers a high-level overview of what constitutes a simple AWS Proton workflow divided into the following six steps.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/service-diagram_1.png)
![\[Red circle with the number 1 inside, typically used as a notification icon.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-one.png)As an **Administrator**, you create and register an **Environment Template** with AWS Proton, which defines the shared resources.
![\[Number 2 icon in a pink circle.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-two.png)AWS Proton deploys one or more **Environments**, based on an **Environment Template**.
![\[Pink square icon with a white exclamation mark inside a circle.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-three.png) As an **Administrator**, you create and register a **Service Template** with AWS Proton, which defines the related infrastructure, monitoring, and CI/CD resources as well as compatible **Environment Templates**.
![\[Number 4 in a red circle icon, commonly used to indicate a notification count.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-four.png) As a **Developer**, you select a registered **Service Template** and provide a link to your **Source code** repository.
![\[Pink square icon with number 5 inside, representing a notification or count.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-five.png) AWS Proton provisions the **Service** with a **CI/CD Pipeline** for your **Service instances**.
![\[Red circle icon with number 6 inside, representing a notification or count.\]](http://docs.aws.amazon.com/proton/latest/userguide/images/label-six.png) AWS Proton provisions and manages the **Service** and the **Service Instances** that are running the **Source code** as was defined in the selected **Service Template**. A **Service Instance** is an instantiation of the selected **Service Template** in an **Environment** for a single stage of a **Pipeline** (for example Prod).
# AWS Proton Service Deprecation and Migration Guide
AWS has decided to discontinue AWS Proton, with support ending on October 7, 2026. New customers will not be able to sign up after October 7, 2025, but existing customers can continue to use the service until October 7, 2026.
## Service Status Until Deprecation
Until October 7, 2026, existing AWS Proton customers can continue to use the service normally. During this period, AWS will:
1. Provide security patches and critical bug fixes
1. Maintain service availability and performance
1. Continue to offer support through AWS Support channels
1. Not add new features to the service
## Important Migration Information
AWS Proton is primarily a CI/CD tool for deploying infrastructure. When AWS Proton is deprecated, your deployed CloudFormation stacks and the resources they manage will remain intact and continue to function. The deprecation affects only the delivery pipelines and the AWS Proton service itself, not your deployed infrastructure.
## Alternative Solutions
We've identified several alternatives to AWS Proton that can help you maintain your infrastructure as code and CI/CD capabilities.
### CloudFormation Git Sync
**Best for:** Teams using CloudFormation who want a GitOps workflow
Git sync enables platform teams to model CloudFormation templates in a git repository that development teams can fork. Developers update parameter files, push changes to their forked repository, and Git sync updates the stack.
#### Key Benefits:
1. Similar developer experience to AWS Proton
1. Leverages existing CloudFormation knowledge
1. Clear separation between platform and developer teams
#### Limitations:
1. No concept of environments
1. No advanced pipeline features
1. Relies on GitHub features that may not be available in other Git providers
Learn more: [Git sync](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/git-sync.html)
### Harmonix On AWS
**Best for:** Enterprises needing a comprehensive internal developer portal
Harmonix is an AWS Partner solution based on Backstage.io and provides an AWS plugin that allows teams to create templates, environments, and services similar to Proton.
#### Key Benefits:
1. Similar functionality to AWS Proton
1. Built on the popular Backstage framework
1. Complete developer portal experience
#### Limitations:
1. Not maintained by an AWS service team
1. Reference implementation that may require customization
Learn more: [https://harmonixonaws.io/](https://harmonixonaws.io/)
### AWS CodePipeline and AWS CodeBuild
**Best for:** Teams needing maximum flexibility and control
Use the AWS foundational CI/CD services to replicate AWS Proton functionality with greater flexibility and control.
#### Key Benefits:
1. Maximum flexibility
1. Deep integration with AWS services
1. Active maintenance and new features
#### Limitations:
1. Requires more implementation work
1. Less out-of-box developer self-service
#### Learn more:
[What is AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html)
[What is AWS CodeBuild](https://docs.aws.amazon.com/codebuild/latest/userguide/welcome.html)
### GitHub Actions
**Best for:** Smaller teams using GitHub who want simplicity
#### >Key Benefits
1. Easy integration with GitHub repositories
1. Simple setup for GitHub users
1. Large marketplace of reusable actions
#### Limitations:
1. Tied to GitHub ecosystem
1. May require more work for platform team controls
#### Learn more:
[GitHub Actions documentation](https://docs.github.com/en/actions)
CI/CD example: [Integrating with GitHub Actions – CI/CD pipeline to deploy a Web App to Amazon EC2](https://aws.amazon.com/blogs/devops/integrating-with-github-actions-ci-cd-pipeline-to-deploy-a-web-app-to-amazon-ec2/)
## Migration Guidance
The migration process depends on your implementation and chosen alternative. General steps:
1. Inventory your Proton resources:
1. Select an alternative solution:
1. Extract your template data:
1. Implement your chosen alternative:
1. Migrate production workloads:
For specific migration assistance, contact AWS Support or your account team.
## FAQs
**Q: Why is AWS discontinuing AWS Proton?** A: We've identified better opportunities to meet customer needs for Infrastructure as Code policy enforcement through other AWS and AWS Partner solutions.
**Q: Will my existing infrastructure continue to function after the deprecation date?** A: Yes. AWS Proton is primarily a CI/CD tool. Your deployed CloudFormation stacks and the resources they manage will remain intact and continue to function. The deprecation affects only the delivery pipelines, not your deployed infrastructure.
**Q: How can I get help with migration?** A: AWS Support can assist with your migration. Please contact [AWS Support](https://console.aws.amazon.com/support), or you can reach out to your AWS account manager for assistance.
**Q: Which alternative should I choose?** A: The best alternative depends on your specific use case:
1. For a simple GitOps workflow: CloudFormation Git Sync
1. For enterprises needing a developer portal: Harmonix On AWS
1. For maximum flexibility: AWS CodePipeline and AWS CodeBuild
1. For teams already on GitHub: GitHub Actions
**Q: What happens if I don't migrate by October 7, 2026?** A: You'll no longer be able to access AWS Proton. Your existing infrastructure will continue to function, but you won't be able to use AWS Proton to manage or update it.
**Q: How long will my data be retained?** A: Until October 7, 2026. After this date, all data will be deleted.
If you have additional questions, please contact AWS Support.