[BUG] Deploy Failed (Bucket already exists)
doongsilee opened this issue · comments
Error Symptoms
AWS Cloud Formation deployment is failed and rollbacked
The error message is clear. but the problem is that I don't have the incoming bucket.
I tried a couple of times with other names, and It's the same always.
Error Message
//Incoming is the bucket name for EamilRestingPlace
S3Email | CREATE_FAILED | incoming already exists
Param
AutoDeployParam No -
CodePipelineArtifactsParam configure-s3-mail -
EmailRestingPlace incoming -
GitHubAccountOwnerParam 0x4447 -
GitHubTokenParam **** -
StageParam master -
And what is the name of the bucket that already exists?
"incoming", "incoming-mails", "received"
Those are the names that I've tried and It seems like it doesn't matter what the name is.
bucket names are global.
https://stackoverflow.com/questions/59639110/s3-bucket-global-uniqueness
meaning someone else on earth has already picked that name. Try
"hyunwooincoming", "hyunwooincoming-mails", "hyunwooreceived"
…On Fri, Jan 22, 2021 at 10:47 AM Hyunwoo Lee ***@***.***> wrote:
"incoming", "incoming-mails", "received"
Those are the names that I've tried and It seems like it doesn't matter
what the name is.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA6TES7DFDILD3OBH3LI63S3DKKPANCNFSM4WMJE2GA>
.
--
--
Mike Cariaso
http://www.cariaso.com
Aha. that's right! I'm sorry. I forgot that rule even I created a bucket for the configuration just before.
thanks. I'll close the issue.