Individual skill
infrastructure-aws
AWS cloud infrastructure inspection. Use when investigating EC2 instances, ECS tasks/services, Lambda functions, CloudWatch logs/metrics, or AWS resource issues.
sre-agent/.claude/skills/infrastructure-aws/SKILL.md
Source commit 2323af0551856ff4669b73dc36329d16aa19ed24
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 179
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-sre Repository topic
- site-reliability-engineering Repository topic
- ai-agent Repository topic
- devops Repository topic
- episodic-memory Repository topic
- incident-investigation Repository topic
- incident-response Repository topic
- knowledge-graph Repository topic
- sre-agent Repository topic
- self-hosted Repository topic
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesSKILL.mdcore · 5,054 bytesscripts/aws_client.pyruns · 2,270 bytesscripts/describe_ec2_instance.pyruns · 3,152 bytesscripts/describe_ecs_service.pyruns · 4,085 bytesscripts/get_cloudwatch_logs.pyruns · 3,121 bytesscripts/get_cloudwatch_metrics.pyruns · 4,129 bytesscripts/get_lambda_logs.pyruns · 3,307 bytesscripts/list_cloudwatch_alarms.pyruns · 3,029 bytesscripts/list_ec2_instances.pyruns · 3,276 bytesscripts/list_ecs_services.pyruns · 2,889 bytesscripts/list_lambda_functions.pyruns · 2,452 bytes
Read excerpt
# AWS Infrastructure
## Authentication
**IMPORTANT**: Credentials are fetched automatically from the credential resolver. Do NOT check for `AWS_ACCESS_KEY_ID` or `AWS_SECRET_ACCESS_KEY` in environment variables — they won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration you CAN check (non-secret):
- `CONFIGURED_INTEGRATIONS` — JSON list, check if `aws` is present
---
## MANDATORY: Logs/Metrics-First Investigation
**Start with CloudWatch logs or metrics, then drill into resources.**