Supported Regions - AWS DevOps Agent

Supported Regions

This topic describes the AWS Regions where you can use AWS DevOps Agent. For more information about AWS Regions, see Specify which AWS Regions your account can use in the AWS Account Management Reference Guide.

Cross-Region resource monitoring

AWS DevOps Agent can monitor and investigate resources in AWS accounts located in any AWS Region, regardless of which supported Region you create your Agent Space in. When you associate an AWS account with an Agent Space, the agent discovers and maps resources across all Regions within that account. This means you do not need an Agent Space in every Region where your workloads run.

Choose a supported Region based on your preferred data residency, proximity to your operations team, or organizational requirements.

Supported Regions

AWS DevOps Agent is available in the following AWS Regions.

Region Name Region Code Console Link
US East (N. Virginia) us-east-1 Open console
US West (Oregon) us-west-2 Open console
Asia Pacific (Sydney) ap-southeast-2 Open console
Asia Pacific (Tokyo) ap-northeast-1 Open console
Europe (Frankfurt) eu-central-1 Open console
Europe (Ireland) eu-west-1 Open console

Service endpoints

Region Name Region Code Endpoint Protocol
US East (N. Virginia) us-east-1 aidevops.us-east-1.amazonaws.com HTTPS
US West (Oregon) us-west-2 aidevops.us-west-2.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 aidevops.ap-southeast-2.amazonaws.com HTTPS
Asia Pacific (Tokyo) ap-northeast-1 aidevops.ap-northeast-1.amazonaws.com HTTPS
Europe (Frankfurt) eu-central-1 aidevops.eu-central-1.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 aidevops.eu-west-1.amazonaws.com HTTPS

Considerations

  • Agent Space Region selection — An Agent Space and its data (investigations,

topology, recommendations) are stored in the Region where you create it. Choose a Region that meets your data residency requirements.

  • Cross-Region monitoring — Resources in AWS accounts associated with an Agent

Space are monitored regardless of which Region those resources are deployed in. You do not need to create separate Agent Spaces in each Region where your workloads run.

  • Third-party integrations — Connections to CI/CD providers (GitHub, GitLab),

observability tools (Dynatrace, Datadog, New Relic, Splunk), and MCP servers are configured per Agent Space and are not Region-dependent.