# Anyone used the Organization template feature under "Cloud and virtualization" -\> AWS -\> Organization Template section?

**URL:** <https://community.dynatrace.com/t/anyone-used-the-organization-template-feature-under-cloud-and-virtualization-aws-organization-template-section/56448>\
**Category:** Cloud platforms\
**Tags:** aws, clouds\
**Created:** [July 14, 2026, 8:47pm UTC](https://community.dynatrace.com/t/anyone-used-the-organization-template-feature-under-cloud-and-virtualization-aws-organization-template-section/56448 "2026-07-14T20:47:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkani](https://avatars.discourse-cdn.com/v4/letter/p/edb3f5/32.png) [@pkani](https://community.dynatrace.com/u/pkani)\
**Post date:** [July 14, 2026, 8:47pm UTC](https://community.dynatrace.com/t/anyone-used-the-organization-template-feature-under-cloud-and-virtualization-aws-organization-template-section/56448/1 "2026-07-14T20:47:38Z")

</div>

I am trying not to connect account by account from our organization. We have around 60+ Aws accounts.

 ![Screenshot 2026-07-14 164719.png](https://global.discourse-cdn.com/dynatrace/original/3X/a/3/a3833cde1ca998abae5b39e779b2d643c89d14c7.png)

---

<div class="post-metadata">

**Author:** ![sujit\_k\_singh](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sujit\_k\_singh](https://community.dynatrace.com/u/sujit_k_singh)\
**Post date:** [July 15, 2026, 1:15am UTC](https://community.dynatrace.com/t/anyone-used-the-organization-template-feature-under-cloud-and-virtualization-aws-organization-template-section/56448/2 "2026-07-15T01:15:57Z")

</div>

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

Yes, for an environment with 60+ AWS accounts, the AWS Organization Template feature is designed to avoid configuring each account individually.

How it works: instead of creating individual AWS connections, you create an Organization template (Collect and capture \> Cloud and virtualization \> AWS \> Organization templates \> New Organization template), give it a name, and enter your AWS Organizations ID. Then choose an observability path:

- **Recommended (Opinionated)** – simpler setup with Dynatrace best-practice defaults; only monitored regions are customizable.
- **Advanced** – full control over monitoring settings.

Once the template is set, Dynatrace uses AWS CloudFormation StackSets to deploy the monitoring resources across your targeted AWS member accounts (or OUs) in one shot, and each account shows up in the Accounts tab as “Organization member” once healthy.

Thanks,

Sujit
