Issues I ran into while running these stacks in a new account

[geoffmoldenhauer]

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

[matthias-herrmann]

@geoffmoldenhauer thanks :) this saved me quite a lot of time.

Further remarks:
I needed to run aws iam create-service-linked-role --aws-service-name rds.amazonaws.com as well and change the region in the validate-env.py code. Further I had to adjust the keyname in env-details.yml because I created a key with a different name.