Let me do more tests from CLI and I will be back shortly.

US is S3 default. So do you have actually any reason to believe that your problem is about "country code"?

Special characters in the Secret access key should not be problem in WinSCP GUI (can be a problem in scripting).

Though the error message that you are getting indeed suggests that your credentials are wrong.

Are you able to login with WinSCP to S3 anyhow? (e.g. different set of credentials, different bucket, whatever)

Seems in CrossFTP - default is US.
Could be a problem is the "Secret access key" contains a special ASCII chars - like - "/+_" ?

gintasr wrote:

Setting a s3.us.amazonaws.com did not finds server name, because port 443 redirects to sub server.
We currently using CrossFTP and it works well with current settings - see attachement

How do you change "country code" in CrossFTP?

Setting a s3.us.amazonaws.com did not finds server name, because port 443 redirects to sub server.
We currently using CrossFTP and it works well with current settings - see attachement

So do you have any reference for that hostname?

Also it does not look like you have changed the hostname to s3.us.amazonaws.com. I see the default s3.amazonaws.com hostname in the log.

Please find attached log file.

Thank you in advance for the support.

G.

gintasr wrote:

In our case should be s3.us.amazonaws.com, however, not working in 5.14.1

Are you sure about that? I've never seen such S3 endpoint. Do you have any reference for this?
See https://docs.aws.amazon.com/general/latest/gr/rande.html

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

martin wrote:

Try WinSCP 5.14.1. With it, you should be able to use a hostname like s3.eu-west-1.amazonaws.com
https://winscp.net/tracker/1695

In our case should be s3.us.amazonaws.com, however, not working in 5.14.1

Try WinSCP 5.14.1. With it, you should be able to use a hostname like s3.eu-west-1.amazonaws.com
https://winscp.net/tracker/1695

martin wrote:

gintasr wrote:

Sorry, it's a S3. Need to be Default Region [US], in the debuglog- S3: Default region: us-east-1

us-east-1 is the default region.

We need a possibility to change.

gintasr wrote:

Sorry, it's a S3. Need to be Default Region [US], in the debuglog- S3: Default region: us-east-1

us-east-1 is the default region.

martin wrote:

gintasr wrote:

Need a possibility to change country code in A3 login.

What is A3? Do you mean S3? What is country code for?

Sorry, it's a S3. Need to be Default Region [US], in the debuglog- S3: Default region: us-east-1

gintasr wrote:

Need a possibility to change country code in A3 login.

What is A3? Do you mean S3? What is country code for?

Hi,

Need a possibility to change country code in A3 login.

HAve you a sollution?

Thanks,
G

Thanks for your post.

Can you send me an email, so I can send you back a development version of WinSCP for testing? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

This was with WinSCP v5.13.1

1) Turn on session logging
2) Connect to the regular AWS S3 service
3) search the session log for the line (near the top of the file): "S3: Default region: us-east-1"

Update WinSCP so we can configure the Default Region variable. Receive donation.

In a nutshell: we need the ability to set the default connecting region as part of the configuration for a S3 Login Session.

We are connecting to an S3 clone service (like dreamhost's S3 clone). Our clone service has different region names from the standard AWS s3. On the WinSCP, S3 login page, when we click login, we receive the error: "The autorization header is malformed; the region 'us-east-1' is wrong; expecting '<our providers region name>'.