New AWS integration and API

[Jerome]

Hello,

We plan to use the new AWS integration directly from GitHub and we plan to do it all in code.

With all the step  thru API or Terrfaorm script to create role, firehose, .....

Where can we find some documentation about API  call to do all the configuration step.

Jerome

[sujit_k_singh]

Hi @Jerome 

Yes—what you’re trying to do is supported, but the documentation is split across multiple areas

Create AWS connection via API — This covers the Dynatrace side (creating the connection object, configuring credentials, etc.): Create AWS connection via API — Dynatrace Docs

Dynatrace provides an official Terraform provider for managing configuration as code:

Docs overview | dynatrace-oss/dynatrace | Terraform | Terraform Registry

AWS resources (Firehose / IAM / Metric Streams) These are not fully managed by Dynatrace—you need to create them via AWS IaC. Stream logs via Amazon Data Firehose — Dynatrace Docs

GitHub

GitHub - dynatrace-oss/terraform-provider-dynatrace: Dynatrace Terraform provider · GitHub

There is no single “all-in-one” repo, but you can achieve full automation by combining:

Dynatrace API / Terraform, 

AWS Terraform / CloudFormation, 

Your pipeline (GitHub)

Thanks,

Sujit

[ftmazzone]

Hello @sujit_k_singh ,

Do you know if the new AWS monitoring connection deployment is already supported by terraform ? As far as I know, it is still under development.
Looking at the documentation, I see only the previous AWS monitoring implementation. 

Thanks.

Florent

[sujit_k_singh]

Hi Florent,

You're right the new Cloud Platform Monitoring for AWS doesn't have a dedicated Terraform resource yet in the dynatrace-oss provider. It's still under development.

However, the new integration does support full programmatic setup via API:

• Create AWS connection via API & AWS CLI — CloudFormation-based
• Create AWS connection via API (Low-level) — for custom GitOps pipelines

The low-level API doc is specifically for when you want to integrate the connection creation into your own automation pipelines without deploying the CloudFormation stack directly.

Thanks,

Sujit