The specified Amazon S3 bucket does not exist

Andre Pfanz asked on February 7, 2017 21:49

We set up a Kentico v9 site and are getting this when we go to it using a browser:

Runtime Error

Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

This error comes up even for the /admin area.

I checked the Windows event log and found this entry:

[AccountInfo.AccountInfo]: The specified Amazon S3 bucket does not exist. at CMS.AmazonStorage.AccountInfo..ctor(String accessKeyID, String accessKey, String bucketName) at CMS.AmazonStorage.AccountInfo.get_Current() at CMS.AmazonStorage.S3ObjectInfoProvider.GetBucketName(String path) at CMS.AmazonStorage.S3ObjectInfo.FetchMetadata() at CMS.AmazonStorage.S3ObjectInfo.Exists() at CMS.IO.Directory.Exists(String path) at CMS.Helpers.HelpersHandlers.InitStorage(Object sender, EventArgs e) at CMS.Base.AbstractHandler.CallEventHandler[TArgs](EventHandler1 h, TArgs e) at CMS.Base.AbstractHandler.Raise[TArgs](String partName, List1 list, TArgs e, Boolean important) at CMS.Base.SimpleHandler2.RaiseExecute(TArgs e) at CMS.Base.SimpleHandler2.RaiseExecute(TArgs e) at CMS.Base.SimpleHandler`2.StartEvent(TArgs e) at CMS.DataEngine.CMSApplication.PreInit() at CMS.DataEngine.CMSHttpApplication.InitApplication() at Global..cctor()

I have the following keys set in web.config:

<add key="CMSExternalStorageName" value="amazon" />
<add key="CMSAmazonBucketName"  value="..." />
<add key="CMSAmazonAccessKeyID" value="..." />
<add key="CMSAmazonAccessKey" value="..." />

<add key="CMSAmazonPublicAccess" value="true" />
<add key="CMSAmazonEndPoint" value="http://d17zmv3wr28ha1.cloudfront.net/" />

I verified the bucket name for the key CMSAmazonBucketName exists on Amazon S3. Does anyone have any ideas what else I can do? Thanks.

Recent Answers


Andre Pfanz answered on February 7, 2017 22:45

I'm starting to think this is not a Kentico problem but rather a problem with Amazon AWS.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.