Monitor Amazon Web Services with Amazon CloudWatch metrics
Follow this guide to start ingesting data remotely from Amazon CloudWatch.
This guide focuses on infrastructure monitoring of Amazon Web Services services: Dynatrace monitoring AWS services via CloudWatch. See What's next? for Full-Stack and Log Monitoring of your AWS services.
After you have established the initial monitoring, you can add, remove, or modify service monitoring using the Dynatrace web UI or, at scale, using the Dynatrace API.
To learn the measurements collected for each of the AWS services, see:
The Amazon Web Services infrastructure monitoring provides metrics from CloudWatch, infrastructure data available via public AWS API, and specific events. The data is collected in five-minute intervals.
Cost of monitoring
-
Each service monitored by Dynatrace through CloudWatch, as well as log processing and analysis, consumes DDUs.
-
Amazon may charge you extra for CloudWatch metric queries. For the details on these additional costs, please consult Amazon CloudWatch pricing online documentation.
Monitoring prerequisites
There are three prerequisites for the AWS monitoring setup:
Dynatrace admin permissions
ActiveGate capable of AWS monitoring
AWS monitoring policy and role-based authentication
Dynatrace admin permissions
To manage AWS monitoring configuration, you need permissions to read and modify the builtin:cloud.aws schema.
- Both
settings:objects:readandsettings:objects:writeare required. - They are included in the Change monitoring settings permissions.
Read-only access is not supported.
See Manage user permissions with roles for details on how to manage and set permissions.
ActiveGate capable of AWS Monitoring
To monitor Amazon Web services, Dynatrace needs to be able to connect to the Amazon CloudWatch API and query it periodically. At least one ActiveGate needs to be able to connect to Amazon CloudWatch to perform the monitoring tasks.
If you're a SaaS customer, an ActiveGate capable of monitoring your AWS account is already provided and available within the Dynatrace AWS account.
To add an ActiveGate that is capable of cloud monitoring, follow the ActiveGate installation guide and resume this guide when done.
You must install and configure an Environment ActiveGate if you want to monitor either or both of the following:
More than 2,000 AWS resources (AWS service instances)
- Non-default AWS Cloud services
Allow ActiveGate to access AWS URLs
The integration accesses the following AWS API endpoints, so they must be accessible from your ActiveGate:
AWS Security Token Service
1https://sts.amazonaws.com/
The AWS Security Token Service is a global endpoint by default. In case of using a regional endpoint, sts.<REGION>.amazonaws.com needs to be accessible.
AWS Resource Groups Tagging
1https://tagging.<REGION>.amazonaws.com/
Amazon CloudWatch
1https://monitoring.<REGION>.amazonaws.com/
Amazon EC2
1ec2.<REGION>.amazonaws.com
Other endpoints may be required depending on the services you need to monitor. Consult the table below for endpoints specific to each service you might want to monitor.
| Endpoint | Service |
|---|---|
autoscaling.<REGION>.amazonaws.com | Amazon EC2 Auto Scaling (built-in), Amazon EC2 Auto Scaling |
elasticbeanstalk.<REGION>.amazonaws.com | AWS Elastic Beanstalk (built-in), AWS Elastic Beanstalk |
lambda.<REGION>.amazonaws.com | AWS Lambda (built-in), Amazon Lambda |
elasticloadbalancing.<REGION>.amazonaws.com | AWS Application and Network Load Balancer (built-in), AWS Elastic Load Balancing (ELB) (built-in) |
dynamodb.<REGION>.amazonaws.com | Amazon DynamoDB (built-in), Amazon DynamoDB |
ec2.<REGION>.amazonaws.com | Amazon EBS (built-in), Amazon EC2 (built-in), Amazon EBS, Amazon EC2, Amazon EC2 Spot Fleet, Amazon VPC NAT Gateways, AWS Transit Gateway, AWS Site-to-Site VPN |
rds.<REGION>.amazonaws.com | Amazon RDS (built-in), Amazon Aurora, Amazon DocumentDB, Amazon Neptune, Amazon RDS |
s3.<REGION>.amazonaws.com | Amazon S3 (built-in) |
acm-pca.<REGION>.amazonaws.com | AWS Certificate Manager Private Certificate Authority |
apigateway.<REGION>.amazonaws.com | Amazon API Gateway |
apprunner.<REGION>.amazonaws.com | AWS App Runner |
appstream2.<REGION>.amazonaws.com | Amazon AppStream |
appsync.<REGION>.amazonaws.com | AWS AppSync |
athena.<REGION>.amazonaws.com | Amazon Athena |
cloudfront.amazonaws.com | Amazon CloudFront |
cloudhsmv2.<REGION>.amazonaws.com | AWS CloudHSM |
cloudsearch.<REGION>.amazonaws.com | Amazon CloudSearch |
codebuild.<REGION>.amazonaws.com | AWS CodeBuild |
datasync.<REGION>.amazonaws.com | AWS DataSync |
dax.<REGION>.amazonaws.com | Amazon DynamoDB Accelerator (DAX) |
dms.<REGION>.amazonaws.com | Amazon Database Migration Service |
directconnect.<REGION>.amazonaws.com | AWS Direct Connect |
ecs.<REGION>.amazonaws.com | Amazon Elastic Container Service (ECS), Amazon ECS ContainerInsights |
elasticfilesystem.<REGION>.amazonaws.com | Amazon Elastic File System (EFS) |
eks.<REGION>.amazonaws.com | Amazon Elastic Kubernetes Service (EKS) |
elasticache.<REGION>.amazonaws.com | Amazon ElastiCache (EC) |
elastictranscoder.<REGION>.amazonaws.com | Amazon Elastic Transcoder |
es.<REGION>.amazonaws.com | Amazon Elasticsearch Service (ES) |
events.<REGION>.amazonaws.com | Amazon EventBridge |
fsx.<REGION>.amazonaws.com | Amazon FSx |
gamelift.<REGION>.amazonaws.com | Amazon GameLift |
glue.<REGION>.amazonaws.com | AWS Glue |
inspector.<REGION>.amazonaws.com | Amazon Inspector |
kafka.<REGION>.amazonaws.com | Amazon Managed Streaming for Kafka |
models.lex.<REGION>.amazonaws.com | Amazon Lex |
logs.<REGION>.amazonaws.com | Amazon CloudWatch Logs |
api.mediatailor.<REGION>.amazonaws.com | Amazon MediaTailor |
mediaconnect.<REGION>.amazonaws.com | AWS Elemental MediaConnect |
mediapackage.<REGION>.amazonaws.com | Amazon MediaPackage Live |
mediapackage-vod.<REGION>.amazonaws.com | Amazon MediaPackage Video on Demand |
opsworks.<REGION>.amazonaws.com | AWS OpsWorks |
qldb.<REGION>.amazonaws.com | Amazon QLDB |
redshift.<REGION>.amazonaws.com | Amazon Redshift |
robomaker.<REGION>.amazonaws.com | AWS RoboMaker |
route53.amazonaws.com | Amazon Route 53 |
route53resolver.<REGION>.amazonaws.com | Amazon Route 53 Resolver |
api.sagemaker.<REGION>.amazonaws.com | Amazon SageMaker Endpoints, Amazon SageMaker Endpoint Instances |
sns.<REGION>.amazonaws.com | Amazon Simple Notification Service (SNS) |
sqs.<REGION>.amazonaws.com | Amazon Simple Queue Service (SQS) |
storagegateway.<REGION>.amazonaws.com | AWS Storage Gateway |
swf.<REGION>.amazonaws.com | Amazon SWF |
transfer.<REGION>.amazonaws.com | Amazon Transfer Family |
workmail.<REGION>.amazonaws.com | Amazon WorkMail |
workspaces.<REGION>.amazonaws.com | Amazon WorkSpaces |
AWS monitoring policy and role-based authentication
To perform these steps, you need to have AWS admin privileges.
The AWS monitoring policy defines the minimal scope of permissions you need to give to Dynatrace to monitor the services running in your AWS account. Create it once and use it any time when enabling Dynatrace access to your AWS account. If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each cloud service, a list of optional permissions specific to that service.
| Name | Additional permissions |
|---|---|
| AWS Certificate Manager Private Certificate Authority | "acm-pca:ListCertificateAuthorities" |
| All monitored Amazon services | "cloudwatch:GetMetricData", "cloudwatch:GetMetricStatistics", "cloudwatch:ListMetrics", "sts:GetCallerIdentity", "tag:GetResources", "tag:GetTagKeys", "ec2:DescribeAvailabilityZones" |
| Amazon MQ | |
| Amazon API Gateway | "apigateway:GET" |
| AWS App Runner | "apprunner:ListServices" |
| Amazon AppStream | "appstream:DescribeFleets" |
| AWS AppSync | "appsync:ListGraphqlApis" |
| Amazon Athena | "athena:ListWorkGroups" |
| Amazon Aurora | "rds:DescribeDBClusters" |
| Amazon EC2 Auto Scaling | "autoscaling:DescribeAutoScalingGroups" |
| Amazon EC2 Auto Scaling (built-in) | "autoscaling:DescribeAutoScalingGroups" |
| AWS Billing | |
| Amazon Keyspaces | |
| AWS Chatbot | |
| Amazon CloudFront | "cloudfront:ListDistributions" |
| AWS CloudHSM | "cloudhsm:DescribeClusters" |
| Amazon CloudSearch | "cloudsearch:DescribeDomains" |
| AWS CodeBuild | "codebuild:ListProjects" |
| Amazon Cognito | |
| Amazon Connect | |
| Amazon Elastic Kubernetes Service (EKS) | "eks:ListClusters" |
| AWS DataSync | "datasync:ListTasks" |
| Amazon DynamoDB Accelerator (DAX) | "dax:DescribeClusters" |
| Amazon Database Migration Service | "dms:DescribeReplicationInstances" |
| Amazon DocumentDB | "rds:DescribeDBClusters" |
| AWS Direct Connect | "directconnect:DescribeConnections" |
| Amazon DynamoDB | "dynamodb:ListTables" |
| Amazon DynamoDB (built-in) | "dynamodb:ListTables", "dynamodb:ListTagsOfResource" |
| Amazon EBS | "ec2:DescribeVolumes" |
| Amazon EBS (built-in) | "ec2:DescribeVolumes" |
| Amazon EC2 API | |
| Amazon EC2 (built-in) | "ec2:DescribeInstances" |
| Amazon EC2 Spot Fleet | "ec2:DescribeSpotFleetRequests" |
| Amazon Elastic Container Service (ECS) | "ecs:ListClusters" |
| Amazon ECS ContainerInsights | "ecs:ListClusters" |
| Amazon ElastiCache (EC) | "elasticache:DescribeCacheClusters" |
| AWS Elastic Beanstalk | "elasticbeanstalk:DescribeEnvironments" |
| Amazon Elastic File System (EFS) | "elasticfilesystem:DescribeFileSystems" |
| Amazon Elastic Inference | |
| Amazon Elastic Map Reduce (EMR) | "elasticmapreduce:ListClusters" |
| Amazon Elasticsearch Service (ES) | "es:ListDomainNames" |
| Amazon Elastic Transcoder | "elastictranscoder:ListPipelines" |
| AWS Elastic Load Balancing (ELB) (built-in) | "elasticloadbalancing:DescribeInstanceHealth", "elasticloadbalancing:DescribeListeners", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeRules", "elasticloadbalancing:DescribeTags", "elasticloadbalancing:DescribeTargetHealth" |
| Amazon EventBridge | "events:ListEventBuses" |
| Amazon FSx | "fsx:DescribeFileSystems" |
| Amazon GameLift | "gamelift:ListFleets" |
| AWS Glue | "glue:GetJobs" |
| Amazon Inspector | "inspector:ListAssessmentTemplates" |
| AWS Internet of Things (IoT) | |
| AWS IoT Analytics | |
| Amazon Managed Streaming for Kafka | "kafka:ListClusters" |
| Amazon Kinesis Data Analytics | "kinesisanalytics:ListApplications" |
| Amazon Kinesis Data Firehose | "firehose:ListDeliveryStreams" |
| Amazon Kinesis Data Streams | "kinesis:ListStreams" |
| Amazon Kinesis Video Streams | "kinesisvideo:ListStreams" |
| Amazon Lambda | "lambda:ListFunctions" |
| AWS Lambda (built-in) | "lambda:ListFunctions", "lambda:ListTags" |
| Amazon Lex | "lex:GetBots" |
| AWS Application and Network Load Balancer (built-in) | "elasticloadbalancing:DescribeInstanceHealth", "elasticloadbalancing:DescribeListeners", "elasticloadbalancing:DescribeLoadBalancers", "elasticloadbalancing:DescribeRules", "elasticloadbalancing:DescribeTags", "elasticloadbalancing:DescribeTargetHealth" |
| Amazon CloudWatch Logs | "logs:DescribeLogGroups" |
| AWS Elemental MediaConnect | "mediaconnect:ListFlows" |
| Amazon MediaConvert | "mediaconvert:DescribeEndpoints" |
| Amazon MediaPackage Live | "mediapackage:ListChannels" |
| Amazon MediaPackage Video on Demand | "mediapackage-vod:ListPackagingConfigurations" |
| Amazon MediaTailor | "mediatailor:ListPlaybackConfigurations" |
| Amazon VPC NAT Gateways | "ec2:DescribeNatGateways" |
| Amazon Neptune | "rds:DescribeDBClusters" |
| AWS OpsWorks | "opsworks:DescribeStacks" |
| Amazon Polly | |
| Amazon QLDB | "qldb:ListLedgers" |
| Amazon RDS | "rds:DescribeDBInstances" |
| Amazon RDS (built-in) | "rds:DescribeDBInstances", "rds:DescribeEvents", "rds:ListTagsForResource" |
| Amazon Redshift | "redshift:DescribeClusters" |
| Amazon Rekognition | |
| AWS RoboMaker | "robomaker:ListSimulationJobs" |
| Amazon Route 53 | "route53:ListHostedZones" |
| Amazon Route 53 Resolver | "route53resolver:ListResolverEndpoints" |
| Amazon S3 | "s3:ListAllMyBuckets" |
| Amazon S3 (built-in) | "s3:ListAllMyBuckets" |
| Amazon SageMaker Batch Transform Jobs | |
| Amazon SageMaker Endpoint Instances | "sagemaker:ListEndpoints" |
| Amazon SageMaker Endpoints | "sagemaker:ListEndpoints" |
| Amazon SageMaker Ground Truth | |
| Amazon SageMaker Processing Jobs | |
| Amazon SageMaker Training Jobs | |
| AWS Service Catalog | |
| Amazon Simple Email Service (SES) | |
| Amazon Simple Notification Service (SNS) | "sns:ListTopics" |
| Amazon Simple Queue Service (SQS) | "sqs:ListQueues" |
| AWS Systems Manager - Run Command | |
| AWS Step Functions | |
| AWS Storage Gateway | "storagegateway:ListGateways" |
| Amazon SWF | "swf:ListDomains" |
| Amazon Textract | |
| AWS IoT Things Graph | |
| Amazon Transfer Family | "transfer:ListServers" |
| AWS Transit Gateway | "ec2:DescribeTransitGateways" |
| Amazon Translate | |
| AWS Trusted Advisor | |
| AWS API Usage | |
| AWS Site-to-Site VPN | "ec2:DescribeVpnConnections" |
| Amazon WAF Classic | |
| Amazon WAF | |
| Amazon WorkMail | "workmail:ListOrganizations" |
| Amazon WorkSpaces | "workspaces:DescribeWorkspaces" |
To get the information required for comprehensive AWS cloud-computing monitoring, you have to authorize Dynatrace to access your Amazon metrics. Dynatrace will identify all the virtualized infrastructure components in your AWS environment and collect performance metrics related to those components.
Next, select the deployment model that best describes your environment and follow the procedure for that model.
Key-based authentication is only allowed for AWS GovCloud and China partitions.
In this scenario you have to create an AWS monitoring policy and generate a key pair with that policy.
AWS Identity and Access Management (IAM) permission boundaries may deny AWS actions required by Dynatrace. If you use IAM permission boundary on your AWS account, make sure that actions from policy are allowed in all AWS regions within permission boundary.
To create the AWS monitoring policy
- In your Amazon Console, go to Identity and Access Management.
- Go to Policies and select Create policy.
- Select the JSON tab and paste the predefined policy from the box below.
1{2 "Version": "2012-10-17",3 "Statement": [4 {5 "Sid": "VisualEditor0",6 "Effect": "Allow",7 "Action": [8 "acm-pca:ListCertificateAuthorities",9 "apigateway:GET",10 "apprunner:ListServices",11 "appstream:DescribeFleets",12 "appsync:ListGraphqlApis",13 "athena:ListWorkGroups",14 "autoscaling:DescribeAutoScalingGroups",15 "cloudformation:ListStackResources",16 "cloudfront:ListDistributions",17 "cloudhsm:DescribeClusters",18 "cloudsearch:DescribeDomains",19 "cloudwatch:GetMetricData",20 "cloudwatch:GetMetricStatistics",21 "cloudwatch:ListMetrics",22 "codebuild:ListProjects",23 "datasync:ListTasks",24 "dax:DescribeClusters",25 "directconnect:DescribeConnections",26 "dms:DescribeReplicationInstances",27 "dynamodb:ListTables",28 "dynamodb:ListTagsOfResource",29 "ec2:DescribeAvailabilityZones",30 "ec2:DescribeInstances",31 "ec2:DescribeNatGateways",32 "ec2:DescribeSpotFleetRequests",33 "ec2:DescribeTransitGateways",34 "ec2:DescribeVolumes",35 "ec2:DescribeVpnConnections",36 "ecs:ListClusters",37 "eks:ListClusters",38 "elasticache:DescribeCacheClusters",39 "elasticbeanstalk:DescribeEnvironmentResources",40 "elasticbeanstalk:DescribeEnvironments",41 "elasticfilesystem:DescribeFileSystems",42 "elasticloadbalancing:DescribeInstanceHealth",43 "elasticloadbalancing:DescribeListeners",44 "elasticloadbalancing:DescribeLoadBalancers",45 "elasticloadbalancing:DescribeRules",46 "elasticloadbalancing:DescribeTags",47 "elasticloadbalancing:DescribeTargetHealth",48 "elasticmapreduce:ListClusters",49 "elastictranscoder:ListPipelines",50 "es:ListDomainNames",51 "events:ListEventBuses",52 "firehose:ListDeliveryStreams",53 "fsx:DescribeFileSystems",54 "gamelift:ListFleets",55 "glue:GetJobs",56 "inspector:ListAssessmentTemplates",57 "kafka:ListClusters",58 "kinesis:ListStreams",59 "kinesisanalytics:ListApplications",60 "kinesisvideo:ListStreams",61 "lambda:ListFunctions",62 "lambda:ListTags",63 "lex:GetBots",64 "logs:DescribeLogGroups",65 "mediaconnect:ListFlows",66 "mediaconvert:DescribeEndpoints",67 "mediapackage-vod:ListPackagingConfigurations",68 "mediapackage:ListChannels",69 "mediatailor:ListPlaybackConfigurations",70 "opsworks:DescribeStacks",71 "qldb:ListLedgers",72 "rds:DescribeDBClusters",73 "rds:DescribeDBInstances",74 "rds:DescribeEvents",75 "rds:ListTagsForResource",76 "redshift:DescribeClusters",77 "robomaker:ListSimulationJobs",78 "route53:ListHostedZones",79 "route53resolver:ListResolverEndpoints",80 "s3:ListAllMyBuckets",81 "sagemaker:ListEndpoints",82 "sns:ListTopics",83 "sqs:ListQueues",84 "storagegateway:ListGateways",85 "sts:GetCallerIdentity",86 "swf:ListDomains",87 "tag:GetResources",88 "tag:GetTagKeys",89 "transfer:ListServers",90 "workmail:ListOrganizations",91 "workspaces:DescribeWorkspaces"92 ],93 "Resource": "*"94 }95 ]96}
Give the policy a name.
- Select Create policy.
You'll need to generate an Access key and a Secret access key that Dynatrace can use to get metrics from Amazon Web Services.
- In your Amazon Console, go to Users and select Add Users.
- Enter the User name.
- In the next screen, choose Attach policies directly and attach the policy that you created before.
- Review the user details and select Create user.
- From the list of users, select your newly created user name and go to Security credentials, then select Create access key.
- In the Access key best practices & alternatives screen, select Third-party service, then select Next.
- You will be transferred to the Retrieve access keys screen, where both your Access key and a Secret access key are present.
- Store the Access Key ID name (AKID) and Secret access key values.
- You can either download the user credentials or copy the credentials displayed online (select Show).
Create monitoring configuration
You can create, activate, and manage multiple monitoring connections. Each connection is defined by the credentials and/or access tokens required for Dynatrace to be able to pull in the data.
Allowing for multiple connections and configurations makes it possible to monitor even extremely complex environments. With such an approach, you don't need to configure everything at once. Instead, you can gradually add monitoring configurations to your existing setup. Such an architecture also makes it easy to react to the dynamic changes of the monitored environment, without needing to reconfigure the unaffected elements.
Add a new AWS connection
If you have followed all the prior steps, you are ready to configure Amazon Web Services monitoring.
To add a new AWS connection
-
In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS. The AWS page lists AWS connections already configured.
If you haven't provided an ActiveGate required for AWS monitoring (check Prerequisites for details), the respective information will be provided on the screen and you will not be able to continue with the configuration process.
You can go back to changing the already configured connections at any later point in time.
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS. The page lists existing connections.
- Edit connections as needed.
- To edit an existing connection or the monitored services within, select Edit
in that row. - To delete an existing connection, select Delete
in that row.
- To edit an existing connection or the monitored services within, select Edit
-
Select Connect new instance and complete the following fields.
- Connection name—enter a descriptive name for the connection.
- Authentication method—select
Role-based authentication. - IAM role…—enter the name of the role you created in Amazon for Dynatrace.
- Your Amazon account ID—enter your Amazon account ID (the account you want Dynatrace to pull metrics from).
-
Select Connect to verify and save the connection.
If your AWS account is on a different partition than the default AWS partition, you can use the AWS partition list to select your partition.
You can limit the data acquired from the CloudWatch by defining a tag-based filter of specific resources. See Limit API calls to AWS using tags for more details on tag-based filtering.
AWS cloud services monitored by default
After Dynatrace connects to your AWS environment, it immediately starts monitoring selected AWS services. Built-in AWS metrics lists the metrics of AWS cloud services monitored by default.
Monitor other AWS services
In addition to AWS services, it's also possible to monitor all other AWS cloud services. AWS cloud services are enabled for monitoring per AWS connection.
To add a service to monitoring:
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- On the AWS overview page, find the connection that you want to change and select Edit in that row.
- Under Services, select Manage services.
- Select Add service.
- Select the service from the list and then select Add service.
- Select Save changes to save your configuration.
You can add multiple cloud services by repeating the steps above.
After you add a service, Dynatrace automatically starts collecting a set of metrics for this particular service.
Recommended metrics:
Enabled by default
Can not be disabled
Can come with recommended dimensions (enabled by default, can't be disabled)
Can come with optional dimensions (disabled by default, can be enabled)
Apart from the recommended metrics, most services have the possibility of enabling optional metrics that can be added and configured manually.
To see the complete list of AWS cloud services and learn about the metrics collected for each of them, see All AWS cloud services.
Alternatively, you can check the list of supported AWS Services on Dynatrace Hub or within the in-product Hub: in the Dynatrace menu, go to Dynatrace Hub and search for AWS.
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- On the AWS overview page, find the connection that you want to change and select the edit icon next to its name.
- Go to Services and select Manage services.
- To add a metric select the service for which you want to add metrics and select Add new metric.
- From the menu select Add metric for the metric you want to monitor.
- Select Edit to configure the metric.
- Select Apply to save your configuration.
After you select the cloud services and save your changes, monitoring of the newly added services starts automatically.
What's next?
Within minutes, you'll see the data on your dashboards.
To see the core measurements per each of the AWS connections
- In the Dynatrace menu, go to Infrastructure > AWS.
Select the connection for which you want to see an overview of the AWS infrastructure.
You can also build your own dashboard from the metrics collected for your AWS instances. For details on building dashboards, see Dashboards Classic.
Dynatrace OneAgent offers unparalleled depth of insight into hosts, containers, and code. To learn more, see Amazon Web Services Integrations.
After you set up AWS monitoring, you can:
- Set up metric events for alerting. This enables you to create, enable, disable and configure recommended alerting rules.
- Limit API calls to AWS using tags. By default, Dynatrace monitors all Amazon Web Services that have been specified in your permission policy. Optionally, you can use tagging to limit the AWS resources that are monitored by Dynatrace.
This method of monitoring does not require an ActiveGate. Dynatrace integration with Amazon CloudWatch Metric Streams provides a simple and safe way to ingest AWS metrics. Amazon CloudWatch Metric Streams allows all metrics issued in a given AWS region to be streamed through Kinesis Firehose to the Dynatrace API. For details, see Amazon CloudWatch Metric Streams.
It is also possible to trace AWS Lambda .NET Core functions with OpenTelemetry .NET.