AWS S3 Bucket in Cape Town region not accessible

Advertisement

pcza
Donor
Joined:
Posts:
3
Location:
South Africa

AWS S3 Bucket in Cape Town region not accessible

WinSCP Error Message when attempting to connect to an S3 bucket in the new af-south-1 location:
The af-south-1 location constraint is incompatible for the region specific endpoint this request was sent to.
Screenshot of error dialog attached.

Description: ScreenShot of Error Dialog

snap0000232.png

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
36,205
Location:
Prague, Czechia

Re: AWS S3 Bucket in Cape Town region not accessible

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

pcza
Donor

Re: AWS S3 Bucket in Cape Town region not accessible

It is not possible to select the af-south-1 region from within the current version of WinSCP.

There is also no provision to select the new Milan Italy region eu-south-1 in the current version of WinSCP.

Reply with quote

Advertisement

Guest

I'm still having this issue even if configuring the region from the dropdown menu:
The eu-south-1 location constraint is incompatible for the region specific endpoint this request was sent to.
With the same set of key/secret S3 Browser is working fine.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
36,205
Location:
Prague, Czechia

@Guest: Please attach a full session log file showing the problem (using the latest version of WinSCP). And also a log file from S3 browser.

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum