An S3 bucket was created manually.
Add it to an infrastructure-as-code stack without recreating the bucket or losing data.
Which method is most appropriate?
Use CloudFormation resource import to map the existing physical resource to a template resource.
Detailed explanation
S3 lifecycle management does not import a resource into a stack.
S3 lifecycle management does not import a resource into a stack.
Resource import associates an existing physical resource with a stack without recreating it.
Resource import associates an existing physical resource with a stack without recreating it.
Deletion can cause data loss and downtime.
Deletion can cause data loss and downtime.
DNS records do not import resources into CloudFormation.
DNS records do not import resources into CloudFormation.
Check official documentation
Compare the following points with the official documentation.
AWS CloudFormation resource importの公式説明を確認する。
What to confirm
新規作成と既存リソース取り込みを区別できる。
Key points
- Resource import
- CloudFormation
- Existing resource
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Adoption
Import enables gradual migration from manual provisioning to stack management.
Ownership transfer
After import, future changes should be controlled through the stack and its template.