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.
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 Oxtober 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:
-
Provide security patches and critical bug fixes
-
Maintain service availability and performance
-
Continue to offer support through AWS Support channels
-
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:
-
Similar developer experience to AWS Proton
-
Leverages existing CloudFormation knowledge
-
Clear separation between platform and developer teams
Limitations:
-
No concept of environments
-
No advanced pipeline features
-
Relies on GitHub features that may not be available in other Git providers
Learn more: Git sync
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:
-
Similar functionality to AWS Proton
-
Built on the popular Backstage framework
-
Complete developer portal experience
Limitations:
-
Not maintained by an AWS service team
-
Reference implementation that may require customization
Learn more: 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:
-
Maximum flexibility
-
Deep integration with AWS services
-
Active maintenance and new features
Limitations:
-
Requires more implementation work
-
Less out-of-box developer self-service
Learn more:
GitHub Actions
Best for: Smaller teams using GitHub who want simplicity
>Key Benefits
-
Easy integration with GitHub repositories
-
Simple setup for GitHub users
-
Large marketplace of reusable actions
Limitations:
-
Tied to GitHub ecosystem
-
May require more work for platform team controls
Learn more:
CI/CD example: Integrating with
GitHub Actions – CI/CD pipeline to deploy a Web App to Amazon EC2
Spacelift
Best for: Teams needing advanced governance and compliance capabilities
AWS Partner solution that combines Infrastructure as Code and CI/CD capabilities on a single platform. It provides governance controls, drift detection, and approval workflows that help teams maintain security and compliance while enabling developer self-service for infrastructure deployments.
Key Benefits:
-
Advanced drift detection and dashboarding
-
Approval workflows for security and compliance
-
Works with various Infrastructure as Code tools
-
Can be self-hosted on AWS
Limitations:
-
Third-party solution with separate billing
Learn more: https://spacelift.io/
Migration Guidance
The migration process depends on your implementation and chosen alternative. General steps:
-
Inventory your Proton resources:
-
Select an alternative solution:
-
Extract your template data:
-
Implement your chosen alternative:
-
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
Q: Which alternative should I choose? A: The best alternative depends on your specific use case:
-
For a simple GitOps workflow: CloudFormation Git Sync
-
For enterprises needing a developer portal: Harmonix On AWS
-
For maximum flexibility: AWS CodePipeline and AWS CodeBuild
-
For teams already on GitHub: GitHub Actions
-
For advanced governance needs: Spacelift
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.
