quickstart-bitnami-wordpress icon indicating copy to clipboard operation
quickstart-bitnami-wordpress copied to clipboard

Published 20 hours ago • verified publisher icon aws-quickstart

S3 Bucket doesn't exist

Open MikeW83 opened this issue 5 years ago • 7 comments

Hello guys,

I'm trying to use the templae and I change the values for QSS3BucketName and QSS3KeyPrefix to my own values and I receive this error. Is it not possible to change the values?

image Thank you!

Best regards, Michael

MikeW83 avatar Dec 17 '19 15:12 MikeW83

Now I tried to leave all settings as is. I have chosen a password for database and WordPress an set the mail adddess.

Now a rollback startet with this error:

Type AWS::CloudFormation::Stack Logical ID WordPressStack Physical ID arn:aws:cloudformation:eu-central-1:299389137464:stack/WordPress-HA-by-Bitnami-WordPressStack-OUOK70A0FXCT/797fc2a0-2114-11ea-94b4-069442661d72 Status Reason Embedded stack arn:aws:cloudformation:eu-central-1:299389137464:stack/WordPress-HA-by-Bitnami-WordPressStack-OUOK70A0FXCT/797fc2a0-2114-11ea-94b4-069442661d72 was not successfully created: The following resource(s) failed to create: [ElastiCacheStack, RDSAuroraStack].

I don't get this template to successfully published.

MikeW83 avatar Dec 17 '19 21:12 MikeW83

I'm getting the same problems was there any resolution to these issues?

stjohnalex avatar Jun 25 '20 14:06 stjohnalex

I'm getting the same problems was there any resolution to these issues?

No, there was no response or something else.

MikeW83 avatar Jun 26 '20 10:06 MikeW83

Sorry for the very late response.

We weren't correctly tracking the issues/PRs from this repository in our support workflow.

It is likely that this issue is no longer applicable. Are you still affected? Please do not hesitate to let us know if that is the case, and one of our agents would help you with it.

juan131 avatar Mar 24 '21 12:03 juan131

I am experiencing the same error

dukai1011 avatar May 09 '21 05:05 dukai1011

This problem will occur if you specify your bucket or the prefix and either is incorrect. OR it will also occur if access is not properly granted. Without a bucket specified the cloudformation template works fine.

MichaelDBrown avatar Jun 01 '21 18:06 MichaelDBrown

This problem will occur if you specify your bucket or the prefix and either is incorrect. OR it will also occur if access is not properly granted. Without a bucket specified, the cloud formation template works fine.

Thanks, I have already figured it out, indeed Without the bucket parameter specified will work fine,

dukai1011 avatar Jun 01 '21 18:06 dukai1011