HTML5 Amazon S3 incorrectly configured

I have tried creating keys multiple times with full admin privileges on my Amason S3 account, but adding the credentials to the project files always returns this line after packaging. I’m on 4.10.2.

MainFrameActions: Packaging (HTML5): HTML5Platform.UploadToS3: Amazon S3 Incorrectly configured

The project itself packages and plays correctly locally, but does not upload. I’ve checked, and re-checked everything multiple time. Hopefully I’m missing something elementary here?

Hi steyrboy,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • What steps are you taking to reproduce this on your end?

Hi steyrboy,

We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.

I’m having the exact same issue and I’m on 4.12, any suggestions?

Hi ronellcross,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?

  • What steps are you taking to reproduce this on your end?

Adam, sorry for not responding earlier… projects with crazy deadlines remove me from reality for months at a time.

I just tried to submit to my bucket in a brand new project with no new content (no starter content either) and I still get the error “HTML5Platform.UploadToS3: Amazon S3 Incorrectly configured”.

Repro steps are easy… create a project, add my key/secret key and bucket name and package for HTML5 via File->Package Product->HTML5.

This was with 4.12.5 engine installed form the Epic Games Launcher.

I actually have a sad answer to this problem. I created a new bucket and tried to make the bucket name TestTestMe1717. It told me to use only lowercase letters. I crated a similar bucket name with only lowercase. It worked

I guess my previously “fathered in” bucket with capitol letters is a no-go in the current AWS realm, or maybe an issue with the way Unreal interfaces with AWS? I assume the former.

Hi steyrboy,

I did a bit of research, and it looks like the former is in part correct. While in some areas, uppercase letters can be used, it looks like it causes a problem with the virtual host access and tends to lead to a bucket not found error. I found this:

Which contains naming convention rules and standards used for AWS buckets.