# AWS Monitoring: Using Two Dedicated ActiveGates for monitoring Separate Regions in single AWS account

**URL:** <https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777>\
**Category:** Troubleshooting\
**Tags:** aws, activegate\
**Created:** [April 3, 2025, 9:02am UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777 "2025-04-03T09:02:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhaveshbjoshi](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@bhaveshbjoshi](https://community.dynatrace.com/u/bhaveshbjoshi)\
**Post date:** [April 3, 2025, 9:02am UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777/1 "2025-04-03T09:02:56Z")

</div>

# **Abstract**

Infrastructure monitoring of AWS services in different regions using Dynatrace ActiveGates.

# **Problem**

How can a single AWS account be configured to use two ActiveGates to monitor separate regions?

For example, there is&nbsp;a single AWS account, and different regions need to be monitored independently. In this example, there is a need to have one ActiveGate monitor the **ap-south-1** region and another ActiveGate monitor the **ap-south-2** region. The ActiveGates in this example are referred to as **DC AG** and **DR AG** , respectively.

The **DC AG** should monitor the **ap-south-1** &nbsp;region, while the **DR AG** should monitor the **ap-south-2** region.

# **Resolution**

In order to achieve the need in the example, two monitoring configurations must be created for the AWS account with different monitoring roles so that only the desired ActiveGate can monitor a specific configuration. The region to be monitored by each ActiveGates should be set in the custom.properties file:

Example:

**Monitoring Configuration for ActiveGate 1 (DC AG)**

- name: \<accountName\>-ap-south-1
- role: Dynatrace\_monitoring\_role\_ap-south-1 (DC AG can assume, but not other ActiveGates)
- DC AG custom properties:

```auto
[aws_monitoring]
aws_monitoring_enabled = true
aws_client_regions = ap-south-1

```

**Monitoring Configuration for ActiveGate 1 (DR AG)**

- name: \<accountName\>-ap-south-2
- role: Dynatrace\_monitoring\_role\_ap-south-2 (DR AG can assume, not others)
- DR AG custom.properties:

```auto
[aws_monitoring]
aws_monitoring_enabled = true
aws_client_regions = ap-south-2

```

Once the above configuration is done, restart the ActiveGate service, dynatracegateway, on both ActiveGates.

> systemctl restart dynatracegateway

After restarting, wait for a few minutes and check the Dynatrace AWS monitoring page. As an end result, you should be able to see DC AG monitoring ap-south-1 and DR AG monitoring ap-south-2 region.

# **What’s next**

If this article did not help, please open a support ticket, mention that this article was used and provide the following in the ticket:  
1. Link to the AWS Account being monitored

2.&nbsp;Dynatrace monitoring role name

3. Logs from the ActiveGate

---

<div class="post-metadata">

**Author:** ![tarjei](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/tarjei/32/39196_2.png) [@tarjei](https://community.dynatrace.com/u/tarjei)\
**Post date:** [February 3, 2026, 9:54am UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777/2 "2026-02-03T09:54:40Z")

</div>

Hi!

Why isnt the aws\_client\_regions documented in the ActiveGate documentation?

---

<div class="post-metadata">

**Author:** ![bhaveshbjoshi](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@bhaveshbjoshi](https://community.dynatrace.com/u/bhaveshbjoshi)\
**Post date:** [February 3, 2026, 10:03am UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777/3 "2026-02-03T10:03:56Z")

</div>

Hi,&nbsp;aws\_client\_regions is a workaround and I don’t see any plans to make it official yet.&nbsp;By default, AWS Monitoring auto-discovers regions to monitor.

---

<div class="post-metadata">

**Author:** ![Adiawal](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Adiawal](https://community.dynatrace.com/u/Adiawal)\
**Post date:** [April 21, 2026, 6:29pm UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777/4 "2026-04-21T18:29:48Z")

</div>

Hi&nbsp;[@bhaveshbjoshi](https://community.dynatrace.com/user/70560)

Why do we need two different monitoring roles?

---

<div class="post-metadata">

**Author:** ![bhaveshbjoshi](https://avatars.discourse-cdn.com/v4/letter/b/5f8ce5/32.png) [@bhaveshbjoshi](https://community.dynatrace.com/u/bhaveshbjoshi)\
**Post date:** [June 4, 2026, 9:28am UTC](https://community.dynatrace.com/t/aws-monitoring-using-two-dedicated-activegates-for-monitoring-separate-regions-in-single-aws-account/50777/5 "2026-06-04T09:28:53Z")

</div>

hi&nbsp;[@Adiawal](https://community.dynatrace.com/user/52196)&nbsp;customer had a specific requirement.