Production EC2 instances are currently patched and configured by hand.
Reduce differences between servers and recreate the same configuration safely.
Which policy is most appropriate?
Create a tested AMI and replace instances through Auto Scaling instead of modifying running servers individually.
Detailed explanation
Shared credentials increase security risk and do not provide controlled, repeatable updates.
Shared credentials increase security risk and do not provide controlled, repeatable updates.
CloudFront distributes content and does not manage operating-system configuration.
CloudFront distributes content and does not manage operating-system configuration.
Individual changes accumulate drift and make the environment harder to reproduce.
Individual changes accumulate drift and make the environment harder to reproduce.
Immutable updates replace instances from a known image and avoid accumulating manual changes.
Immutable updates replace instances from a known image and avoid accumulating manual changes.
Check official documentation
Compare the following points with the official documentation.
EC2 AMIとAuto Scalingの公式説明を確認する。
What to confirm
サーバーを直接変更せず、イメージ置換でインフラを更新できる。
Key points
- AMI
- Immutable infrastructure
- Auto Scaling
Notes
- Environment: AWS公式EC2・Auto Scalingドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Reproducibility
A tested image and launch configuration make replacement repeatable and auditable.
Change control
Replacing an instance creates a clear version boundary and rollback point.