Connect to Amazon Web Services (AWS) to:
- See automatic AWS status updates in your event stream
- Get CloudWatch metrics for EC2 hosts without installing the Agent
- Tag your EC2 hosts with EC2-specific information
- See EC2 scheduled maintenance events in your stream
- Collect CloudWatch metrics and events from many other AWS products
- See CloudWatch alarms in your event stream
To quickly get started using the AWS integration, check out the AWS getting started guide.
Datadog's Amazon Web Services integration is built to collect ALL metrics from CloudWatch
. Datadog strives to continually update the docs to show every sub-integration, but cloud services rapidly release new metrics and services so the list of integrations are sometimes lagging.
|API Gateway||Create, publish, maintain, and secure APIs|
|App Runner||A service that provides a fast, simple, and cost-effective way to deploy from source code or a container image.|
|Appstream||Fully managed application streaming on AWS|
|AppSync||A GraphQL service with real-time data synchronization and offline programming features|
|Athena||Serverless interactive query service|
|Autoscaling||Scale EC2 capacity|
|Billing||Billing and budgets|
|CloudFront||Local content delivery network|
|Cloudhsm||Managed hardware security module (HSM)|
|CloudSearch||Access to log files and AWS API calls|
|CloudTrail||Access to log files and AWS API calls|
|CodeBuild||Fully managed build service|
|CodeDeploy||Automate code deployments|
|Cognito||Secure user sign-up and sign-in|
|Connect||A self-service, cloud-based contact center service|
|Direct Connect||Dedicated network connection to AWS|
|DMS||Database Migration Service|
|Dynamo DB||NoSQL Database|
|EBS (Elastic Block Store)||Persistent block level storage volumes|
|EC2 (Elastic Cloud Compute)||Resizable compute capacity in the cloud|
|EC2 Spot||Take advantage of unused EC2 capacity|
|ECS (Elastic Container Service)||Container management service that supports Docker containers|
|EFS (Elastic File System)||Shared file storage|
|EKS||Elastic Container Service for Kubernetes|
|Elastic Transcoder||Media and video transcoding in the cloud|
|ElastiCache||In-memory cache in the cloud|
|Elastic Beanstalk||Service for deploying and scaling web applications and services|
|ELB (Elastic Load Balancing)||Distributes incoming application traffic across multiple Amazon EC2 instances|
|EMR (Elastic Map Reduce)||Data processing using Hadoop|
|ES (Elasticsearch)||Deploy, operate, and scale Elasticsearch clusters|
|Firehose||Capture and load streaming data|
|FSx||Managed service providing scalable storage for Windows File Server or Lustre.|
|Gamelift||Dedicated game server hosting|
|Glue||Extract, transform, and load data for analytics|
|GuardDuty||Intelligent threat detection|
|Health||Visibility into the state of your AWS resources, services, and accounts|
|Inspector||Automated security assessment|
|IOT (Internet of Things)||Connect IOT devices with cloud services|
|Keyspaces||Managed Apache Cassandra–compatible database service|
|Kinesis||Service for real-time processing of large, distributed data streams|
|KMS (Key Management Service)||Create and control encryption keys|
|Lex||Build conversation bots|
|Machine Learning||Create machine learning models|
|MediaConnect||Transport for live video|
|MediaConvert||Video processing for broadcast and multiscreen delivery|
|MediaPackage||Prepare and protect video for delivery over the internet|
|MediaTailor||Scalable server-side ad insertion|
|MQ||Managed message broker for ActiveMQ|
|Managed Streaming for Kafka||Build and run applications that use Apache Kafka to process streaming data|
|NAT Gateway||Enable instances in a private subnet to connect to the internet or other AWS services|
|Neptune||Fast, reliable graph database built for the cloud|
|Network Firewall||Filter traffic at the perimeter of a VPC|
|RDS (Relational Database Service)||Relational database in the cloud|
|Redshift||Data warehouse solution|
|Rekognition||Image and video analysis for applications|
|Route 53||DNS and traffic management with availability monitoring|
|S3 (Simple Storage Service)||Highly available and scalable cloud storage service|
|SageMaker||Machine learning models and algorithms|
|SES (Simple Email Service)||Cost-effective, outbound-only email-sending service|
|SNS (Simple Notification System)||Alerts and notifications|
|SQS (Simple Queue Service)||Messaging queue service|
|Storage Gateway||Hybrid cloud storage|
|SWF (Simple Workflow Service)||Cloud workflow management|
|VPC (Virtual Private Cloud)||Launch AWS resources into a virtual network|
|Web Application Firewall (WAF)||Protect web applications from common web exploits|
|Workspaces||Secure desktop computing service|
|X-Ray||Tracing for distributed applications|
AWS role delegation is not supported on the Datadog for Government site. Access keys
must be used.
Use one of the following methods to integrate your AWS accounts into Datadog for metric, event, tag, and log collection.
To set up the AWS integration manually with role delegation, see the manual setup guide.
Access keys (GovCloud or China Only)
To set up the AWS integration with access keys, see the manual setup guide.
AWS IAM Permissions
AWS IAM permissions enable Datadog to collect metrics, tags, CloudWatch events, and other data necessary to monitor your AWS environment.
To correctly set up the AWS Integration, you must attach the relevant IAM policies to the Datadog AWS Integration IAM Role in your AWS account.
AWS Integration IAM Policy
The set of permissions necessary to use all the integrations for individual AWS services.
The following permissions included in the policy document use wild cards such as
Get*. If you require strict policies, use the complete action names as listed and reference the Amazon API documentation for your respective services.
AWS Security Audit Policy
To use Cloud Security Posture Management, attach AWS’s managed SecurityAudit Policy to your Datadog IAM role.
There are two ways of sending AWS service logs to Datadog:
- Kinesis Firehose destination: Use the Datadog destination in your Kinesis Firehose delivery stream to forward logs to Datadog. It is recommended to use this approach when sending logs from CloudWatch in a very high volume.
- Forwarder Lambda function: Deploy the Datadog Forwarder Lambda function, which subscribes to S3 buckets or your CloudWatch log groups and forwards logs to Datadog. You must use this approach to send traces, enhanced metrics, or custom metrics from Lambda functions asynchronously through logs. Datadog also recommends you use this approach to sending logs from S3 or other resources that cannot directly stream data to Kinesis.
There are two ways to send AWS metrics to Datadog:
- Metric polling: API polling comes out of the box with the AWS integration. A metric-by-metric crawl of the CloudWatch API pulls data and sends it to Datadog. New metrics are pulled every ten minutes, on average.
- Metric streams with Kinesis Firehose: You can use Amazon CloudWatch Metric Streams and Amazon Kinesis Data Firehose to see your metrics. Note: This method has a two to three minute latency, and requires a separate setup.
Some Datadog products leverage information about how your AWS resources (such as S3 Buckets, RDS snapshots, and CloudFront distributions) are configured. Datadog collects this information by making read only API calls into your AWS account.
Cloud Security Posture Management
If you do not have the AWS integration set up for your AWS account, complete the set up process above. Ensure to enable resource collection when mentioned.
Note: The AWS integration must be set up with Role delegation to use this feature.
To add Cloud Security Posture Management to an existing AWS integration, follow the steps below to enable resource collection.
Provide the necessary permissions to the Datadog IAM role with the automatic or manual steps:
Automatic - Update your CloudFormation template.
a. In the CloudFormation console, find the main stack you used to install the Datadog integration and select
Replace current template.
Amazon S3 URL, enter
https://datadog-cloudformation-template.s3.amazonaws.com/aws/main.yaml and click
true and click
Next without modifying other existing parameters until you reach the
Review page. Here you can verify the change set preview.
e. Check the two acknowledgment boxes at the bottom and click
Manual - Attach the AWS managed
SecurityAudit policy to your Datadog AWS IAM role. You can find this policy in the AWS console.
Complete the setup in the Datadog AWS integration tile with the steps below. Alternatively, you can use the Update an AWS Integration API endpoint.
- Click on the AWS account where you wish to enable resource collection.
- Go to the Resource collection section for that account and check the box
Expanded collection required for Cloud Security Posture Management.
- At the bottom left of the tile, click
There are two ways to send AWS CloudWatch alarms to the Datadog Event Stream:
- Alarm polling: Alarm polling comes out of the box with the AWS integration and fetches metric alarms through the DescribeAlarmHistory API. If you follow this method, your alarms are categorized under the event source
Amazon Web Services. Note: The crawler does not collect composite alarms.
- SNS topic: You can see all AWS CloudWatch alarms in your event stream by subscribing the alarms to an SNS topic, then forwarding the SNS messages to Datadog. To learn how to receive SNS messages as events in Datadog, see Receive SNS messages. If you follow this method, your alarms are categorized under the event source
|The volume of log events in uncompressed bytes uploaded to Cloudwatch Logs.|
Shown as byte
|The number of log events uploaded to Cloudwatch Logs.|
Shown as event
|The volume of log events in compressed bytes forwarded to the subscription destination.|
Shown as byte
|The number of log events forwarded to the subscription destination.|
Shown as event
|The number of log events for which CloudWatch Logs received an error when forwarding data to the subscription destination.|
Shown as event
|The number of log events for which CloudWatch Logs was throttled when forwarding data to the subscription destination.|
Shown as event
|Measures the number of times a target is invoked for a rule in response to an event. This includes successful and failed invocations but does not include throttled or retried attempts until they fail permanently.|
|Measures the number of invocations that failed permanently. This does not include invocations that are retried or that succeeded after a retry attempt|
|Measures the number of triggered rules that matched with any event.|
|Measures the number of events that matched with any rule.|
|Measures the number of triggered rules that are being throttled.|
|The number of specified operations performed in your account|
Shown as operation
|The number of specified resources in your account|
Shown as resource
Events from AWS are collected on a per AWS-service basis. See the your AWS service’s documentation to learn more about collected events.
The following tags are collected with the AWS integration. Note: Some tags only display on specific metrics.
|Integration||Datadog Tag Keys|
|SES||Tag keys are custom set in AWS.|
CRITICAL if one or more AWS regions are experiencing issues. Returns
Statuses: ok, critical
See the AWS Integration Troubleshooting guide to resolve issues related to the AWS integration.
Additional helpful documentation, links, and articles: