Migrating from AWS Proton.
AWS is shutting down Proton on October 7, 2026. If your team uses Proton to manage ECS Fargate environments, Fortem is the purpose-built replacement — and your Terraform doesn't need to change.
“On October 7, 2026, AWS will discontinue support for AWS Proton. After this date, you will no longer be able to access the AWS Proton console or AWS Proton resources.”
Source: aws.amazon.com/proton — confirmed live on their page.
Everything Proton did — and the operations layer it never had.
- Environment scheduling — stop paying for dev/staging compute when nobody is working
- Environment templates — define once, clone to any region or account in seconds
- Fleet-wide visibility — all ECS services, RDS, ElastiCache, external deps in one view
- Developer self-service — RBAC-scoped restart, redeploy, logs without AWS Console access
- AI diagnostics — when a task fails, a diagnostic agent reads logs, checks IAM, proposes the fix
- Works with your existing Terraform — no HCL rewrite, no proprietary config layer
From Proton to Fortem in one business week.
We review your current Proton setup — templates, environments, pipelines. We tell you honestly what maps directly to Fortem and what doesn't.
We connect to your AWS account via a cross-account IAM role. Fortem picks up your existing ECS environments automatically — via tags and naming conventions. No re-provisioning.
We translate your Proton service templates into Fortem environment templates. Scheduling rules configured per environment, per timezone. Takes 7 business days for a standard fleet.
We run a team training session so your platform engineers and developers know the new workflows. Then you delete the Proton resources before the October deadline. Your Terraform stays unchanged.
Fortem does not replace your Terraform. When your Terraform provisions ECS services, RDS instances, or other resources, Fortem picks them up automatically via tags and naming conventions. Your HCL stays unchanged. You don't give Fortem access to your Terraform repo. Uninstall Fortem at any time — your infrastructure runs exactly the same. For the full access model — what IAM permissions Fortem requests and what it never touches — see the security page.
The October deadline is fixed. We can have you migrated well before it.
Book a 20-minute call — we'll review your Proton setup and tell you exactly what the migration looks like for your fleet.
Run Fleet Audit →