aws-samples / codepipeline-nested-cfn Goto Github PK

Is it possible for you to update the repo with a working AMI?

If a sub-stack fails to create, is there a way to have the error bubble upwards for capture, or sent somewhere? Currently, if a stack fails to create, the error reason is deleted with the stack during rollback. Kind of hard to troubleshoot unless you are staring at your pipeline.

Hi,

Great project! Here to report that I ran into several problems while running this stack on a new AWS account:

1. I had to create service-linked roles for autoscaling.amazonaws.com, elasticloadbalancing.amazonaws.com and rds.amazonaws.com services by running these commands in the CLI:

aws iam create-service-linked-role --aws-service-name autoscaling.amazonaws.com
aws iam create-service-linked-role --aws-service-name elasticloadbalancing.amazonaws.com
aws iam create-service-linked-role --aws-service-name rds.amazonaws.com

I'm aware that Amazon now creates these automatically when you provision a resource, but it's a bit faster this way.

2. I had to modify the AMI ID to the newest version of Amazon Linux 2 (ami-0e01ce4ee18447327 at the time of writing this post) in these files: config-test.json, config-uat.json, config-prod.json and env-details.py

3. I had to update the mysql version from 5.7.11 to 5.7.22 in databasestack.yml

Once these changes were made and the stack ran through the Test stage successfully, the UAT and Prod stages ran beautifully. Thank you for creating this, it was a great challenge for me to troubleshoot and I had a lot of fun doing it!

Geoff Moldenhauer

This is a question, not an issue per se.

i note this statement:

Note: While removing the resources, delete the Prod & UAT stacks created by pipeline before deleting the pipeline since those CloudFormations stacks uses the role created by pipeline stack.

I've experienced the pain of having to remove stacks in the right order.

When developing a pipeline you need to repeatedly create and delete the outlying codepipeline stack, and are left to delete the sub-stacks. It would be nice if there was a way to have stacks created by the pipeline be deleted when the pipeline gets deleted (in reverse dependency order).

Is there a way to do this, or does the user have to remember to delete the stacks created by the pipeline manually everytime, in the right order? Any advice is welcome.

Hi, thank you for this work.

I was just wondering where TEMPLATE_BUCKET was set in the build file in the nested templates folder?

thanks

Hi Team,
I have created a lambda with the help of cloud formation [template.yml] file, Created one stack also. The lambda is in holding this stack itself.
Then after creating the new codePipeline also. The source is in GitHub, Build provider is AWS code build, Deploying is AWS cloud formation. What I created the previous, the stack only using it. But while running the pipeline stack is getting an error. already exist the lambda in this stack, like that.

I need exact requirements I a created some lambda with help of AWS cloud formation deploy commends,Now I need that lambda in code pipeline itself. From new pipeline I 'll create and update the lambda, what is the solution to without deleting the already created lambda?