configuring-vpc-endpoints-for-private-aws-service-access
A skill that walks the agent through VPC endpoint setup with AWS PrivateLink, so AWS services stay reachable without an internet gateway or public IPs.
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a claude-codeWhat configuring-vpc-endpoints-for-private-aws-service-access does
The skill hands the agent domain knowledge for VPC endpoints: gateway endpoints for S3 and DynamoDB, interface endpoints for EC2, SSM, Secrets Manager and other services on AWS PrivateLink. Ask it to set up private connectivity and it follows the procedure in references/configure-vpc-endpoints-for-private-aws-service-access.md instead of improvising a config.
Inside are the setup procedure and a troubleshooting section. If an endpoint is unreachable, it checks security group rules, subnet configuration and whether the service exists in the region. DNS problems mean verifying that DNS hostnames and DNS resolution are enabled on the VPC and that the DHCP options set points at the right name servers. Connection timeouts usually come down to port 443 or to route tables for gateway endpoints.
Endpoint policies get their own note. Default policies allow all access, but a custom one can block the calls you need, and that is the first thing to check when traffic stalls. The skill installs into Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode.
What it helps with
- set up private access to S3 and DynamoDB without a NAT device
- create an interface endpoint for SSM or Secrets Manager
- debug an endpoint that never becomes available
- fix DNS resolution inside a VPC
- check route tables for a gateway endpoint
Example prompts for the agent
- set up VPC endpoints for private access to S3 and DynamoDB
- why does DNS not resolve for my interface endpoint
- check the endpoint policy, traffic to Secrets Manager is failing
How to install configuring-vpc-endpoints-for-private-aws-service-access
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a claude-code2Manually: put the files in place
~/.claude/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/configuring-vpc-endpoints-for-private-aws-service-access/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a codex2Manually: put the files in place
.agents/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a cursor2Manually: put the files in place
.cursor/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aws/agent-toolkit-for-aws configuring-vpc-endpoints-for-private-aws-service-access2Manually: put the files in place
.github/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.md1Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a gemini-cli2Platform CLI
gemini skills install https://github.com/aws/agent-toolkit-for-aws --path skills/specialized-skills/networking-and-content-delivery-skills/configuring-vpc-endpoints-for-private-aws-service-accessManually: put the files in place
.devin/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about configuring-vpc-endpoints-for-private-aws-service-access
How do I install this skill in Claude?
Run npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access -a claude-code. The skill file then lives at ~/.claude/skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.md.
What does this skill do?
It guides the agent through creating and configuring VPC endpoints: gateway endpoints for S3 and DynamoDB, interface endpoints via AWS PrivateLink for other services. It also covers security groups, route tables and DNS.
Why is my endpoint still not working?
The skill says to check security group rules, subnet configuration and service availability in the region. For DNS, confirm that DNS hostnames and DNS resolution are enabled on the VPC and that the DHCP options set has the correct name servers.
Source text
SKILL.md · Apache-2.0
--- name: configuring-vpc-endpoints-for-private-aws-service-access description: Configures VPC endpoints (interface and gateway) for private AWS service access using AWS PrivateLink. Use when setting up secure private connectivity to S3, DynamoDB, and other AWS services without internet gateway, NAT device, or public IP addresses. Covers endpoint creation, security groups, route tables, and DNS configuration. version: 1 --- # Configuring VPC Endpoints for Private AWS Service Access ## Overview Domain expertise for configuring VPC endpoints to enable private access to AWS services without routing traffic through the internet. Covers both gateway endpoints (S3, DynamoDB) and interface endpoints (EC2, SSM, Secrets Manager, etc.) powered by AWS PrivateLink. ## Configure VPC endpoints To create and configure VPC endpoints for private AWS service access, follow the procedure exactly. See [VPC endpoints configuration procedure](references/configure-vpc-endpoints-for-private-aws-service-access.md). ## Troubleshooting ### Endpoint not available Check security group rules, subnet configurations, and service availability in the region. ### DNS resolution issues Verify DNS hostnames and DNS resolution are enabled on the VPC and that the DHCP options set has correct domain name servers. ### Connection timeouts Verify security group rules allow HTTPS traffic (port 443) and route tables are properly configured for gateway endpoints. ### Policy restrictions Review endpoint policies — default policies allow all access, but custom policies may be restrictive.
© aws · Apache-2.0 · aws/agent-toolkit-for-aws