dt-obs-aws

Solid

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", "AWS dashboards". Do NOT use for explaining existing queries, product documentation questions, generic host CPU/memory metrics (use dt-obs-hosts), application-level tracing (use dt-obs-tracing), or log analysis (use dt-obs-logs).

DevOps & Infrastructure 117 stars 24 forks Updated 3 days ago Apache-2.0

Install

View on GitHub

Quality Score: 88/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# AWS Cloud Infrastructure Monitor and analyze AWS resources using Dynatrace Smartscape and DQL. Query AWS services, optimize costs, manage security, and plan capacity across your AWS infrastructure. ## When to Use This Skill Use this skill when the user needs to work with AWS resources in Dynatrace. Load the reference file for the task type: - **Inventory:** "Show me all EC2 instances in us-east-1" - **Network:** "Find all resources in VPC vpc-abc123" - **Database:** "List all RDS instances with Multi-AZ enabled" - **Serverless:** "Show Lambda functions with VPC access" - **Cost:** "Find unattached EBS volumes for cost savings" - **Security:** "Identify publicly accessible databases" - **Compliance:** "Find resources missing Environment tags" - **Capacity:** "Analyze subnet IP utilization" - **Troubleshoot:** "Map load balancer to instances through target groups" - **Problem Analysis:** "What changed before this AWS problem?" / "What events affected this resource?" - **Workload Context:** "Is this instance behind a load balancer, in an EKS cluster, or managed by ECS?" - **Events:** "Have there been any recent events in AWS affecting this resource?" --- ## Core Concepts ### Entity Types AWS resources use the `AWS_*` prefix and can be queried using the `smartscapeNodes` function. All AWS entities are automatically discovered and modeled in Dynatrace Smartscape. **Compute:** `AWS_EC2_INSTANCE`, `AWS_LAMBDA_FUNCTION`, `AWS_ECS_CLUSTER`, `AWS_ECS_SERVICE`, `AWS_EKS_CLUST...

Details

Author
Dynatrace
Repository
Dynatrace/dynatrace-for-ai
Created
3 months ago
Last Updated
3 days ago
Language
Shell
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

dt-obs-azure

Azure cloud resources including VMs, VMSS, SQL Database, Storage, AKS, App Service, Functions, VNet networking, load balancers, Event Hubs, Container Apps, and Key Vault. Monitor Azure infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across subscriptions and resource groups.

117 Updated 3 days ago
Dynatrace
DevOps & Infrastructure Solid

dt-obs-gcp

GCP cloud resources including Compute Engine, GKE, Cloud Run, Pub/Sub, VPC networking, DNS, IAM, Secret Manager, and monitoring. Monitor GCP infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across projects and folders.

117 Updated 3 days ago
Dynatrace
DevOps & Infrastructure Solid

dt-obs-kubernetes

Kubernetes cluster, pod, node, and workload monitoring. Use when analyzing K8s health, resource optimization, pod failures, OOMKills, scheduling, or security posture. Also use for Kubernetes operational events like pod restarts, OOM events, evictions, and cluster event history. Trigger: "Kubernetes pods", "K8s cluster health", "OOMKill", "pod restarts", "container CPU", "namespace resource usage", "over-provisioned pods", "privileged containers", "pod placement", "K8s node capacity", "running containers by cluster", "workload scheduling", "pod evictions", "K8s labels and annotations", "kubernetes events", "pod restart events", "OOM events", "K8s event history". Do NOT use for explaining existing queries, product documentation questions, AWS-specific resource queries, service-level RED metrics, distributed tracing, or log analysis — use the relevant skill instead.

117 Updated 3 days ago
Dynatrace