S3 bucket name collision conflict when used across multiple accounts
ericblade opened this issue · comments
When using the same configuration across two different accounts, there is a collision in S3 buckets, if both accounts are creating the lambdas in the same region. Seems like there should be some more uniqueness included in the name of the S3 buckets.