Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyΒ© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
aws-perimeter β€” A terminal-based AWS Security Scanner with 102+ security checks across VPC, IAM, S3, CloudTrail, containers (ECS/EKS), and AI attack detection. Detects dangerous IAM permissions, exposed secrets, misconfigured S3 buckets, container vulnerabilities, and emerging LLMjacking threats. | Kitploit
Tools/GitHubGitHub/thirukguru/aws-perimeter
Cloud Infrastructure SecurityVulnerability ScannersContainer SecurityConfiguration AuditingPenetration TestingCloud SecurityDevSecOpsSecret DetectionThreat Intelligence
Identity & Access Management (IAM)
Misconfiguration
AI Security
GitHubthirukguru/aws-perimeter

aws-perimeter

View Repository
3399 months agoNot yet reviewed

Most Popular

View all β†’

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools β†’

About

A terminal-based AWS Security Scanner with 102+ security checks across VPC, IAM, S3, CloudTrail, containers (ECS/EKS), and AI attack detection. Detects dangerous IAM permissions, exposed secrets, misconfigured S3 buckets, container vulnerabilities, and emerging LLMjacking threats.

Share

aws-perimeter

Go Version Go Reference Go Report Card License

A terminal-based AWS Security Scanner with 100+ security checks across VPC, IAM, S3, CloudTrail, containers (ECS/EKS), and AI attack detection. Detects dangerous IAM permissions, exposed secrets, misconfigured S3 buckets, container vulnerabilities, and emerging LLMjacking threats.

Product overview: docs/CAPABILITIES_OVERVIEW.md

Features

VPC Security

  • Security group analysis (open SSH/RDP, database ports)
  • Public exposure detection & management port risks
  • Network ACL analysis & VPC Flow Log audit
  • VPC peering risks, bastion host detection
  • NAT Gateway status & VPC endpoint coverage

IAM Security

  • Privilege escalation detection (17 patterns)
  • Stale credentials (90+ days)
  • Cross-account trust analysis
  • MFA enforcement gaps
  • Overly permissive policies (*:*)
  • Role chaining, external ID, permission boundaries

S3 Security

  • Public bucket detection
  • Encryption audit & risky bucket policies
  • Public access block status
  • Sensitive file/object discovery (.env, .git, credentials)
  • Deep text-content secret detection in S3 objects

CloudTrail & Logging

  • Trail coverage gaps & multi-region logging
  • Log validation status
  • CloudWatch Logs integration

Secrets Detection

  • Lambda env vars (10 secret patterns)
  • Lambda deployment package (ZIP) scanning
  • EC2 user data scanning
  • Public S3 object content scanning
  • ECR image layer scanning for embedded credentials
  • AWS keys, GitHub/Slack/Stripe tokens

Container Security (NEW)

ECS Security (10 checks)

  • Privileged containers
  • Secrets in environment variables
  • Public IP exposure
  • Host network mode
  • Non-ECR images
  • Writable root filesystem
  • Dangerous Linux capabilities
  • ECS Exec enabled
  • Container Insights status
  • Admin task role

EKS Security (12 checks)

  • Public endpoint access
  • Private endpoint disabled
  • Control plane logging
  • Secrets encryption
  • Kubernetes version
  • OIDC provider for IRSA
  • Legacy auth modes
  • Public subnet nodes
  • Unrestricted SSH access
  • Admin-level node IAM role
  • AMI type (Bottlerocket preference)

AI Attack Detection (NEW)

Based on Feb 2025 threat intelligence: 8-minute AWS breach

  • GPU Instance Monitoring: Detection of p2/p3/p4/p5, g3/g4/g5, inf1/inf2, trn1 instances
  • GPU Public Exposure: GPU instances with public IPs
  • GPU IMDSv1 Risk: GPU instances vulnerable to credential theft
  • Bedrock Abuse: High-capacity provisioned throughput detection
  • Custom Models: Unauthorized Bedrock model training
  • Bedrock Logging: Missing model invocation logging
  • Rapid Provisioning: EC2 API throttle detection (attack pattern)

Security Checks Summary

CategoryCount
Core (IAM, VPC, S3, CloudTrail, Secrets)38
Extended (Lambda, ELB, Route53, Inspector, etc.)35
Container Security (ECS + EKS)22
AI Attack Detection7
Total102

Critical Security Checks

CheckSeverityDescription
Privilege EscalationπŸ”΄ CriticalUser can escalate to admin
Admin Access (:)πŸ”΄ CriticalFull AWS access granted
Exposed SecretsπŸ”΄ CriticalAPI keys/tokens in Lambda/EC2
Public S3 BucketπŸ”΄ CriticalBucket publicly accessible
No CloudTrailπŸ”΄ CriticalNo audit logging
Open SSH/RDPπŸ”΄ CriticalPort 22/3389 to internet
Privileged ContainerπŸ”΄ CriticalECS container with root access
GPU IMDSv1πŸ”΄ CriticalGPU instance credentials vulnerable
Cross-Account Trust🟠 HighExternal account can assume role
EKS Public Endpoint🟠 HighKubernetes API publicly accessible
Bedrock No Logging🟠 HighAI model usage not audited

Prerequisites

1. AWS CLI Installed

# macOS
brew install awscli

# Linux
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip && sudo ./aws/install

2. AWS Credentials Configured

aws configure
# or use named profiles
aws configure --profile myprofile

3. Required IAM Permissions

Your AWS credentials must have read-only access to the services being scanned. The AWS managed policy ReadOnlyAccess works, or see Required Permissions below.

Note: aws-perimeter only performs read operations and never modifies your AWS resources.

Installation

Quick Install (macOS/Linux)

curl -sSfL https://raw.githubusercontent.com/thirukguru/aws-perimeter/main/install.sh | sh

Using Go

go install github.com/thirukguru/aws-perimeter@latest

Usage

aws-perimeter                          # Run full security scan
aws-perimeter --output json            # JSON output
aws-perimeter --profile prod           # Specific AWS profile
aws-perimeter --region us-west-2       # Specific region
aws-perimeter --regions us-east-1,us-west-2            # Multi-region scan
aws-perimeter --regions us-east-1,us-west-2 --max-parallel 4  # Multi-region with controlled concurrency
aws-perimeter --regions us-east-1,us-west-2 --max-parallel 4 --best-effort  # Exit success if at least one region succeeds
aws-perimeter --rules                   # Print RULES.md to stdout (Markdown)
aws-perimeter --capabilities            # Print capabilities overview to stdout (Markdown)
aws-perimeter --all-regions                            # Scan all enabled regions
aws-perimeter --org-scan --org-role-name OrganizationAccountAccessRole  # Multi-account org scan
aws-perimeter --org-scan --max-parallel 5              # Org+region fanout concurrency
aws-perimeter --output html --output-file report.html  # Generate HTML report
aws-perimeter --store --profile prod --region us-west-2 # Run + persist scan
aws-perimeter --trends --trend-days 30 --account-id 123456789012  # Show historical trend table
aws-perimeter history list --db-path ~/.aws-perimeter/history.db
aws-perimeter dashboard --port 8080

For fanout modes (--regions, --all-regions, --org-scan) with --output html --output-file ..., aws-perimeter writes one report per scan unit with region/account + timestamp suffixes (for example security-report-us-east-1-20260210-213045.html or security-report-123456789012-us-east-1-20260210-213045.html). In HTML mode, terminal table output is suppressed and only concise summary lines are printed.

JSON Automation Mode

When --output json is used, aws-perimeter emits a single valid JSON document with no banner/spinner noise, so it is safe for pipelines.

aws-perimeter --profile prod --region us-west-2 --output json | jq .

# Multi-region JSON emits one aggregated top-level JSON document:
aws-perimeter --profile prod --regions us-east-1,us-west-2 --output json | jq .

# export docs via stdout redirection
aws-perimeter --rules > rules.md
aws-perimeter --capabilities > capabilities.md

Multi-region JSON payload includes:

  • summary (total_regions, success, failed, skipped)
  • results (per-region consolidated scan payloads)
  • failures (region + error details when a region scan fails)

Fanout Summary Output

Download Tool