No clue whether t3, m6i or c7g for this workload
Families: t = burst, m = balanced, c = compute, r = memory, g/i = generation, ARM suffix (g) is cheaper.
Try this first
- 1Webserver with variable load: t-family with unlimited mode
- 2Steady CPU load (API, batch): m-family
- 3CPU heavy (build, encoding): c-family
- 4ARM variants (Graviton, t4g/c7g/m7g) are 20 percent cheaper if your software runs on ARM
When to bring us in
Unsure: Compute Optimizer recommends based on actual usage.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.