Create a VPC, subnets, and an IAM role for several environments.
Remove manual differences and reproduce the same infrastructure.
Which method is most appropriate?
Define the resources in an AWS CloudFormation template and manage them as a stack.
Detailed explanation
A template declaratively creates, updates, and deletes multiple resources in a repeatable stack.
A template declaratively creates, updates, and deletes multiple resources in a repeatable stack.
A DNS record does not create resources as a CloudFormation stack.
A DNS record does not create resources as a CloudFormation stack.
CloudFront is not the service for defining VPC resources.
CloudFront is not the service for defining VPC resources.
Manual work makes environment drift and missed steps more likely.
Manual work makes environment drift and missed steps more likely.
Check official documentation
Compare the following points with the official documentation.
AWS CloudFormation stacks and templatesの公式説明を確認する。
What to confirm
手動構築とInfrastructure as Codeの違いを説明できる。
Key points
- CloudFormation
- Template
- Stack
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Repeatability
The same template can be applied to multiple environments with fewer manual differences.
Desired state
The template expresses what should exist rather than a sequence of console clicks.