Home › AWS SysOps Associate › cloudcomputing › sysopsmonitoring › An EC2 Auto Scaling group is set to launch from …
An EC2 Auto Scaling group is set to launch from an AMI baked weekly. After the latest AMI bake, instances boot and immediately fail their health check. Which is the FIRST place to investigate?
AAmazon Macie's classification reports
BThe Route 53 hosted zone — perhaps DNS is wrong
CAWS billing — check whether the account ran out of credit
DThe launch template / configuration's user-data script and the AMI's boot logs (likely the new AMI broke initialisation)
Answer & Solution
Correct answer: D. The launch template / configuration's user-data script and the AMI's boot logs (likely the new AMI broke initialisation)
If new AMI instances fail boot health checks, the AMI / user-data is the obvious suspect — review the boot logs (cloud-init / console output). Billing, DNS, and Macie are unrelated.
Related questions
A team needs disaster recovery with an RTO ≤ 15 minutes and RPO ≤ 5 minutes across two AWSWhich service detects unexpected drift between an AWS resource's actual configuration and A multi-AZ RDS deployment for a write-heavy database experiences a primary AZ failure. WhaWhich automation pattern is BEST for self-healing a stuck EC2 instance — for example, restAn RDS database needs point-in-time-restore for 14 days plus a guaranteed daily backup. WhAn EC2 instance's CPU steady-state is fine but bursts to 100% during scheduled jobs. The tWhich Route 53 routing policy is used to fail traffic over from a primary endpoint to a stAn EC2 fleet behind an ALB needs to scale out when average CPU goes above 70% for 5 minute