AWS S3 Bucket Connection Fails -- Error Code: 403 Forbidden

View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere MFT. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
1 post Page 1 of 1


User avatar
Posts: 8
Joined: Mon May 21, 2018 10:54 am

Post by Support_Nolan » Mon Dec 17, 2018 1:53 pm

My resource test to an Amazon AWS S3 bucket gives the following error code: "403 Forbidden". Is this a problem with GoAnywhere?


The solution to the problem usually comes in one of two forms:

1. Check to see if you are on a release prior to version 5.3.3. (Help > About)
In version 5.3.3 we upgraded the AWS API from 1.1 to 1.11. The older version of the API had inconsistent authentication to the S3 bucket even when the configurations are correct. You could potentially have the correct settings on GoAnywhere AND on the S3 bucket and the test will still fail. Your MFT version should be more recent than 5.3.3 in order to have consistency when using the S3 resource.

2. The permissions on the S3 bucket do not allow for the user to access the contents of the bucket. This means that the test will verify the bucket exists, and then connect to the bucket, but fail to list the contents of the bucket.
To test this, give the S3 buckets user the AmazonS3FullAccess permissions and retest the resource.

That should address the 403 Forbidden error. The best way to test this would be to run a simple project that copies a file to or from your S3 bucket.
Nolan Priebe
Support Analyst
e. [email protected]
p. 1-800-949-4696
w. |
1 post Page 1 of 1