The AWS integration lets you import targets directly from your AWS infrastructure.Documentation Index
Fetch the complete documentation index at: https://pentest-tools.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Available on NetSec, WebNetSec, and Pentest Suite plans.
Benefits
Automatic discovery
Discover EC2 instances and S3 buckets automatically.
Stay current
Re-import at any time to pick up new instances and buckets.
Multi-region
Import from multiple AWS regions at once.
Private networks
Option to import private EC2 IP addresses.
Setting up AWS integration
IAM Configuration
Create an IAM user with minimal read-only permissions:EC2 Permissions
S3 Permissions
Supported services
| Service | What’s Imported |
|---|---|
| EC2 | Running instance IP addresses (public or private) |
| S3 | S3 bucket URLs |
Import options
EC2 Options
| Option | Description |
|---|---|
| Public IP | Import the public IP address of instances |
| Private IP | Import the private IP address (requires VPN) |
Region selection
Select which AWS regions to import from. EC2 instances are discovered in the selected regions. S3 buckets are global; thes3:ListAllMyBuckets API returns all buckets regardless of region selection.
Imported targets
When targets are imported:- EC2 instances appear as targets with the instance name and ID
- S3 buckets appear as HTTPS URLs
- Targets are added to your current workspace
- You can scan them immediately after import
Example imported targets
| Source | Target Name |
|---|---|
| EC2 | 10.0.1.50 (AWS EC2 - WebServer i-1234567890abcdef0) |
| S3 | https://my-bucket.s3.amazonaws.com |
Best practices
- Create a dedicated IAM user for Pentest-Tools.com
- Use read-only permissions only
- Rotate access keys periodically
- Import targets before major security assessments
- Use workspaces to organize imported targets by environment
Troubleshooting
No targets found
No targets found
- Verify IAM permissions are correct
- Check that instances are in running state
- Verify you selected the correct regions
Authentication failed
Authentication failed
- Check Access Key ID and Secret are correct
- Verify the IAM user is active
- Check for copy/paste issues with credentials
Some regions failed
Some regions failed
- Verify IAM permissions apply to all regions
- Check for region-specific restrictions