Veeam is hardcoded to us-east-1 endpoints

[davehill]

I am using Veeam Backup and Replication to create a VBA in a private subnet in eu-west-2 and get this error message:

Failed to check region availability. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (sts.us-east-1.amazonaws.com:443)

I want it to use the regional endpoints as I'm in a regulated environment.

I can successfully install a VBA in an identical private VPC in us-east-1.

Is there a registry setting to override the default region?

[nielsengelen]

Hi Dave,

Ideally, please open a support case to have this researched on what can be done here. This way, they can also follow and assist your plans to ensure everything works. Could you also let me know the case ID once you have one created?

[davehill]

Case #07728764 — IAM is hardcoded to us-east-1

[davehill]

The support guys supplied a Registry Key that has changed the default region and we're golden.

[nielsengelen]

Glad to hear the issue got resolved. If you have any other questions, please let us know.