This use case automates the process of copying your AMI across regions. The AMI’s from one region backed up across a different region enables your Disaster Recovery (DR) setup, and also quickly recovers instances in case the EC2 service in the entire region fails (though this is a rare case). You can scale your applications globally much easier with cross-region AMIs, without any code.
There are two parts to this workflow. The first workflow collects and filters out the EC2 images. Then the endpoint URL of the account in the second region is sent as a payload to the second workflow where the filtered images are pasted on.
In this particular template, the trigger is set to a recurrent schedule that runs every day. This means that backups are carried out everyday. This trigger setting can be customized as well. The resources node collects the EC2 images and the filter node identifies the appropriate images by tags. The http node will post the filtered image onto the account of the second region which is connected using an endpoint URL. The second workflow then copies the image and sends a report via slack or mail.
Use this to initiate a workflow based on time, events or call.
Select resources on which you want to work on.
Enter parameters to filter resources in the workflow.
Invoke external http(s) endpoint
Use this to initiate a workflow based on time, events or call.
Select resources on which you want to work on.
Enter parameters to filter resources in the workflow.
Invoke external http(s) endpoint
You can publish templates created by you on this platform.