Using the CloudFormation Template to manually deploy in AWS.
When deploying Virtual Machines you will notice an option "EC2 Instance Spin Up".
When you choose ‘Spin up EC2 Instances when Virtual Machines have been converted’ this will run the final step of the deployment process in Amazon Web Services (AWS) by running an auto-generated CloudFormation template to create running instances inside a configured VPC with IP’s assigned.
If you do not wish to start the instances or have the VPC created, you can select the other option, i.e., 'Convert Virtual Machines to Amazon Machine Images to spin up later’, and this will just create AMI’s of the instances, which can be started or modified at your leisure.
If at a later stage you wish to deploy using the CloudFormation template, you can retrieve from the deployment summary.
Copy the URL from the box on Boomerang, then go to the CloudFormation service on the AWS web console (https://console.aws.amazon.com/cloudformation/).
You can use the URL of the CloudFormation template as the source Template (‘Specify an Amazon S3 template URL’) when creating a new CloudFormation stack. When the S3 bucket contains dot (.) in its name, this functionality may fail to locate the CloudFormation template. In this case, you can download the template locally once, and use it via “Upload a template to Amazon S3″ option.
You will need to ensure that the AMI’s that were created at the time of the original deploy still exist and that you have enough resource capacity (VPC’s/ENI’s) in AWS to actually complete the deployment.
Note that Boomerang does not provide any management over AWS resources deployed by this method. Undeployment needs to be performed on AWS console (‘Delete Stack’.) Also, Boomerang cannot copyback.