Closed studds closed 4 years ago
Background: I copied this template from a more complex example which used s3 events. In CloudFormation, that creates a circular dependency, which you have to break by hard-coding the bucket name: https://aws.amazon.com/blogs/infrastructure-and-automation/handling-circular-dependency-errors-in-aws-cloudformation/
In this simpler example, the fix is just to remove the hardcoded bucket name. By removing the explicit name, CF will generate a name with a random component.
Another more robust fix might be to allow specifying a stack name prefix: https://github.com/studds/nx-aws/issues/49
S3 bucket names need to be globally unique. Because the name of the S3 bucket is derived from the stack name, which in turn is derived from the app name, when multiple people attempt to deploy the sample app, the bucket name collides.