The t3 Instance Got Slow. Just Size It Up?

An app on a t3 instance crawls under steady load and a teammate wants a bigger instance. Defend what is actually throttling it.

beginner9 min4 roundsEasy mode availableAWSObservability

Answer key reviewed by Branko Petric

Read first: AWS EC2 Explained

Your decision

Your service runs fine for a while, then gets slow under sustained traffic on a t3.medium. CPU looks pinned near a flat ceiling. A teammate says just upgrade to a bigger t3. What is really happening, and what do you do?

The situation

A service runs smoothly for the first stretch of the day, then noticeably slows down during busy hours. The CPU graph rises and then flattens against a hard line well below 100 percent, staying there while requests pile up.

Context

The instance is a t3.medium. Traffic is steady and growing during business hours rather than spiky. A teammate looked at the slow response times and proposed upgrading to a t3.large or t3.xlarge to give it more headroom. Nobody has looked at the CPU credit metrics yet.

More: AWS scenario interview questions