boozallen
The stack policy for helloworld/app runs successfully, but no instance is created
I was able to Run the cloud-formation stack in helloworld/app using the listed policy with the Environment and SecurityContext value as dev. The change set shows status as completed. But no ec2 instance is created. Don't see any error. I tried both using CLI and GUI with same result. Attached is the image of my changeset.
Looks I am missing something obvious. But can't pinpoint it as yet.
Thanks in advance
@threezerous
Please note that a ChangeSet does not make any actual changes. It merely gives you preview of the changes it will make when you execute the ChangeSet.
It looks though, as if you are mixing different templates in the same stack. IGW, VPC, PublicRoute & PublicRouteTable are virtual network constructs that are intended to be in their own stack. The instance and its wait conditions need to be in a separate stack. If you were to execute the ChangeSet you would likely get failures. Depending on the order in which CloudFormation executes the changes, either you cannot remove VPC constructs, because the instance is using them, or you will be unable to create your nstance, as the VPC is removed.
In essence each template (main.yml) under cloud-formation should become its own CloudFormation stack. Also, there are dependencies between the stacks, as some stacks reference the outputs via "ImportValue" constructs.
Aha... that explains... I was trying to run all updates in one stack. I will try with individual stacks tonight and hopefully the dependencies will resolve correctly. Thanks for the clarity.
Sent from Yahoo Mail for iPhone
On Tuesday, December 19, 2017, 11:41 AM, Rob Proper [email protected] wrote:
@threezerous
Please note that a ChangeSet does not make any actual changes. It merely gives you preview of the changes it will make when you execute the ChangeSet.
It looks though, as if you are mixing different templates in the same stack. IGW, VPC, PublicRoute & PublicRouteTable are virtual network constructs that are intended to be in their own stack. The instance and its wait conditions need to be in a separate stack. If you were to execute the ChangeSet you would likely get failures. Depending on the order in which CloudFormation executes the changes, either you cannot remove VPC constructs, because the instance is using them, or you will be unable to create your nstance, as the VPC is removed.
In essence each template (main.yml) under cloud-formation should become its own CloudFormation stack. Also, there are dependencies between the stacks, as some stacks reference the outputs via "ImportValue" constructs.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.