1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
1
To answer specifically, yes it can be done. However, it would require using a Custom Resource which essentially calls the CreateImage Api and so really you would just be wrapping an API call in CloudFormation and I would suggest this might be an anti-pattern so whilst possible I would say perhaps don't do it this way.
Instead you might want to consider using Systems Manage Automation there is a AWS provided document that creates an AMI from an existing instance, the document is called AWS-CreateImage and details of it can be found here.
Assuming your plan is to automate the creation of images there is also a related post here
Contenido relevante
OFICIAL DE AWSActualizada hace 3 años- OFICIAL DE AWSActualizada hace 7 meses
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 4 meses
@danjhd thank you for that, looks like it will do what I am after. does creating an AMI this way capture multiple volumes?
I have just run a test using that SSM Doc and it included all the EBS volumes attached to the instance at the time in the Image,
Instead, you might want to consider using Systems Manage Automation there is an AWS-provided document that creates an AMI from an existing instance, the document is called AWS-CreateImage and details of it can be found here. :
by following this process how I can integrate in the cloud formation template to automatically create the AMI ,