AWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization. Use when analyzing AWS infrastructure, resource inventory, security compliance, capacity planning, or cost savings. Trigger: "show EC2 instances", "find RDS databases", "VPC resources", "AWS cost optimization", "Lambda functions", "ECS services", "security groups", "unattached EBS volumes", "AWS load balancer topology", "publicly accessible databases",
dt-obs-aws is a Dynatrace skill for monitoring and analyzing AWS cloud infrastructure through Dynatrace Smartscape and the Dynatrace Query Language (DQL). It covers a broad span of AWS services — EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS and more — and helps answer inventory, network-topology, cost, security-compliance, and capacity-planning questions about resources already discovered and modeled in Dynatrace. The problem it solves is translating operator intent ("show EC2 instances", "find publicly accessible databases", "find unattached EBS volumes") into correct DQL against Dynatrace's AWS entity model.
The SKILL.md defines the core concepts — `AWS_*` entity types queried via `smartscapeNodes`, common AWS fields (account, region, ARN, VPC, tags), the fields carried on AWS-originated logs and bizevents, relationship types (is_attached_to, uses, runs_on, balances, etc.), and the CloudWatch metric key naming convention. Task-specific reference files supply ready DQL for capacity planning, cost optimization, security/compliance, database and messaging monitoring, load balancing, resource ownership, VPC networking, serverless/containers, and event/problem-timeline analysis (Auto Scaling, AWS Health, CloudFormation). All examples are read-only queries against Dynatrace; the skill explicitly scopes itself away from generic host metrics, tracing, and log analysis, which have their own skills.
It targets SREs, cloud and platform engineers, and FinOps practitioners who run Dynatrace over AWS environments. Use cases include resource inventory, mapping load balancers to instances through target groups, spotting untagged or publicly exposed resources, planning subnet IP capacity, and correlating infrastructure changes with incidents.
Dynatrace Query Language (DQL), primarily the smartscapeNodes function over AWS_* entity types, plus fetch logs, fetch bizevents, and fetch events for observability data.
No. All documented queries are read-only inventory, analysis, and event-timeline lookups against data Dynatrace has already discovered; nothing changes AWS state.
A Dynatrace environment with AWS monitoring configured so that AWS resources are discovered into Smartscape and CloudWatch metrics are ingested.
Not for explaining existing queries, product-documentation questions, generic host CPU/memory metrics (use dt-obs-hosts), application tracing (dt-obs-tracing), or log analysis (dt-obs-logs).
Use filter isNotNull(aws.region) on logs or bizevents; AWS-originated records carry fields like aws.region, aws.account.id, and aws.service without extra exploration.
Quick Setup:
.claude/skills/Repository
dynatrace/dynatrace-for-ai