Individual skill
aws-cloud-pentesting
AWS offensive testing — account and principal identification, IAM enumeration, resource discovery across all regions (S3, EC2, ECS, Lambda, API Gateway, Secrets Manager, SSM, KMS, ECR, snapshots, Cognito, CloudFormation), with AWS CLI as the baseline and Pacu/CloudFox/ScoutSuite as optional accelerators
internal/tools/skills/data/cloud-security/aws-cloud-pentesting/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 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)
- 1,325
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- testing 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
Read excerpt
# AWS Cloud Pentesting
## Purpose
Full AWS offensive methodology: from an identified AWS account/principal to mapped permissions, discovered resources, exposed data, and escalation/impact paths. Works black-box (via discovery chains) and credentialed (operator-supplied or discovered credentials).
## Entry Conditions
- Black-box: account IDs/bucket names/regions from `cloud-attack-surface-discovery` or an SSRF→metadata chain
- Credentialed: validated credentials from `cloud-credential-abuse` (`aws sts get-caller-identity` already recorded)
## Discovery Signals
- 12-digit account IDs (presigned URLs, S3 ARNs, Lambda invocation error leaks)
- Bucket names, API Gateway IDs, Cognito pool IDs in client-side code
- Region hints from endpoint hostnames
