article AWS monitoring setup: Unable to connect to the regional AWS STS endpoint for AWS integration in Troubleshooting

AWS monitoring setup: Unable to connect to the regional AWS STS endpoint for AWS integration

karolinaboba — Tue, 09 Jul 2024 14:52:08 GMT

To fix it, you need to set up an environment variable in AG's VM. This applies also to all regions that used to use only global endpoint:

ap-northeast-1
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-north-1
eu-west-1
eu-west-2
eu-west-3
sa-east-1
us-east-1
us-east-2
us-west-1
us-west-2

See AWS STS Regionalized endpoints.

The environment variable should be visible by ActiveGate.

For Linux, you can just run these two commands with root user permission:

systemctl set-environment AWS_STS_REGIONAL_ENDPOINTS=regional
service dynatracegateway restart

Re: AWS monitoring setup: Unable to connect to the regional AWS STS endpoint for AWS integration

patmis — Wed, 05 Feb 2025 13:10:21 GMT

@karolinaboba
Our recently installed ActiveGate always tries to connect to another region than eu-central-1. Can you explain how to configure the ActiveGate exactly to use only eu-central-1 as region?

Re: AWS monitoring setup: Unable to connect to the regional AWS STS endpoint for AWS integration

Blazej_dt — Mon, 23 Feb 2026 09:32:28 GMT

@patmis
here are two solutions to accomplish it:

You can use a hidden AG config option:

[aws_monitoring] aws_client_regions = "us-east-1;us-east-2"
If you want per-credentials configuration, you can add the undocumented suffix to credentials label:

My Prod AWS Credentials @REGIONS={us-east-1|us-east-2}

Please mind from Dynatrace version 1.329 AWS STS global endpoint is not supported and now it uses regional endpoint. `us-west-2` region became the default region for `ActiveGate` so you need to ensure that `sts.us-west-2.amazonaws.com` endpoint is enabled to maintain connectivity.

More information: https://docs.dynatrace.com/docs/shortlink/aws-monitoring-guide#capable-activegate