AWS App Mesh End of Life: September 30, 2026.[¹] New customers locked out since September 24, 2024. Existing customers have 8 months to migrate. Only critical security updates until shutdown.
AWS Official Replacements for App Mesh
ECS Service Connect (for ECS) - AWS-managed mesh without sidecars
VPC Lattice (for EKS) - Application networking across VPCs and accounts
Direct ALB routing - Simplest option for basic use cases
Real-World Migration Case Study
Migrated one production service: App Mesh → Direct ALB
Timeline: ~6 hours total
- Active migration: 2 hours
- Troubleshooting: 4 hours
Breakdown:
- Planning & setup: 30 min
- Task definition changes: 15 min
- Service deployment: 20 min
- Security group fixes: 1 hour
- Health check troubleshooting: 2 hours
- ALB configuration: 15 min
- Testing: 1 hour
Results: Zero downtime. Full App Mesh removal. Instant rollback capability maintained.
Key insight: First service takes 4-6 hours (learning curve). Subsequent services: 1-2 hours each.
Critical Pre-Migration Requirements
Rollback Strategy is Non-Negotiable
- Ensure all changes are reversible
- Don't remove App Mesh infrastructure until new setup is validated in production
- Avoid destructive configuration changes
- Maintain instant revert capability
Phased Migration Approach
- Deploy new configuration alongside existing App Mesh
- Test thoroughly without affecting production traffic
- Gradually shift traffic to new infrastructure
- Validate stability and performance
- Remove App Mesh components only after proven success
Common Migration Challenges
Security Groups: Update rules for direct service-to-service communication (no more Envoy proxies)
Health Checks: Reconfigure ALB health checks for direct container access
Service Discovery: Implement AWS Cloud Map or ALB target groups
Migration Resources
Action Required: 8 months until shutdown. Start migration planning now.
SOCIAL SHARE CARD GENERATOR