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.
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.
Related challenges
- DynamoDB Is Throttling but Capacity Looks Idle. Crank It Up?
DynamoDB throttles some requests while table capacity looks underused. A teammate wants to raise capacity or flip to on-demand. Defend the real cause.
- Your S3 Website Returns 403. Make the Bucket Public?
Objects in S3 return 403 and a teammate wants to turn off Block Public Access to fix it fast. Defend the right way to grant access.
- Access Keys Are Hardcoded on the EC2 Box. Just Rotate Them?
An app on EC2 authenticates to AWS with long-lived IAM user keys in a config file. One leaked. Defend the real fix.
- Lambda Is Exhausting Your RDS Connections. Raise the Limit?
Under load, Lambda functions fail with too many connections to RDS. A teammate wants to bump max_connections. Defend the real fix.