EC2 and container workloads
Choose a compute model before diving into scaling and performance details. These guides cover virtual machines, container launch types, workload profiling, and related developer tools. Use the monitoring topic when your main task is defining metrics or alarms; use migration and cost guides when you are moving an existing application or evaluating its resource use.
Start here: Amazon EC2 Explained: Instances, AMIs, Storage, and Pricing
Choose and run compute
Build familiarity with EC2 instances and compare container launch types. The integration references explore supporting tools around a workload; they are distinct from the core instance or container setup path.
- Amazon EC2 Explained: Instances, AMIs, Storage, and Pricing
- EC2 Instance Families: How to Compare and Choose
- Amazon ECS Fargate vs. EC2: How to Choose a Capacity Model
- AWS Application Load Balancer Setup: HTTPS, Target Groups, and Health Checks
- AWS CodeArtifact Guide: Formats, Setup, Pricing, and FAQs
- AWS App Mesh End of Support: Migration Options by Runtime
Scale an application
Begin with Auto Scaling setup, then compare dynamic and predictive behavior for the traffic pattern you are investigating. The high-availability article discusses scaling in a wider architecture context rather than replacing a complete recovery plan.
Investigate workload performance
Use workload profiling and monitoring together to narrow a performance problem. EBS bottlenecks, instance right sizing, and Fargate metrics address different parts of the compute stack, so choose an entry that matches the resource or symptom you can observe.