The stack won't deploy some times

[davidgatti]

There is a known bug that AWS is aware of in CF, which makes it that the stack won't deploy when you deal with S3 Events. To mitigate this problem the stack could be split in two.

• https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.html
• https://aws.amazon.com/blogs/devops/use-nested-stacks-to-create-reusable-templates-and-support-role-specialization/

Work around

Right now a work around that works 100% of the time is to remove from the S3Email resource this NotificationConfiguration.LambdaConfigurations, build the stack, deploy it, and then re-add the removed section, and perform and update on the stack.

This solution works, since we make sure that the Lambdas are in place before we add the events. For some this will work out of the box, it all depends how fast a Lambda will be deployed, and no, the DependsOn directive dose nothing - hence the bug.

[davidgatti]

I did try the deployment on a fresh AWS account and it worked without a problem. I'm closing this by hoping that AWS fixed this know bug on their side.

[joshuamsmith]

When I open deploy script in CloudFormations I get an error.

Template format error: Unrecognized resource types: [AWS::SES::ReceiptRule, AWS::SES::ReceiptRuleSet]

[davidgatti]

Hmm, check if the Region you are in supports SES.

[joshuamsmith]

ahhh yeah looks like I'm on us-west-1, but it's only for us-east-1, us-west-2, and eu-west-1. Odd. Thanks I'll try to deploy it on west-2!!!

…

________________________________ From: David Gatti <notifications@github.com> Sent: Sunday, July 28, 2019 11:48 PM To: 0x4447/0x4447-product-s3-email <0x4447-product-s3-email@noreply.github.com> Cc: Joshua Smith <me@joshuamsmith.com>; Comment <comment@noreply.github.com> Subject: Re: [0x4447/0x4447-product-s3-email] The stack won't deploy some times (#1) Hmm, check if the Region you are in supports SES. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://us-east-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tLzB4NDQ0Ny8weDQ0NDctcHJvZHVjdC1zMy1lbWFpbC9pc3N1ZXMvMT9lbWFpbF9zb3VyY2U9bm90aWZpY2F0aW9ucyZlbWFpbF90b2tlbj1BQVBOVUNPWlFMWVdXQVhBSzZIU1c2M1FCMkhFTEE1Q05GU000R1Q2U05SS1lZM1BOVldXSzNUVUw1MkhTNERGVlJFWEc0M1ZNVkJXNjNMTk1WWEhKS1RETjVXVzJaTE9PUlBXU1pHT0QyN1lGS1kjaXNzdWVjb21tZW50LTUxNTg2NzMwNw==&e=bWVAam9zaHVhbXNtaXRoLmNvbQ==&t=bklQL2lPUXdLMGwvSlFwL1pKYXZTNXF1MzUzcUFpWFZpRy9EOGR0SkY2cz0=>, or mute the thread<https://us-east-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQVBOVUNPTlBJTk9YWkgyU0tPUVVQTFFCMkhFTEFOQ05GU000R1Q2U05SQQ==&e=bWVAam9zaHVhbXNtaXRoLmNvbQ==&t=VXZYSEcxYTJ2UElTelhrei96NmJZN2JXdmU2ZWtJUzU4MzFkOHdxSjU5MD0=>.