configuring-vpc-endpoints-for-private-aws-service-access

Configures VPC gateway and interface endpoints for private AWS service access via PrivateLink.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill configuring-vpc-endpoints-for-private-aws-service-access-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configuring-vpc-endpoints-for-private-aws-service-access
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/configuring-vpc-endpoints-for-private-aws-service-access
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill configuring-vpc-endpoints-for-private-aws-service-access-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Accessing AWS services like S3, DynamoDB, EC2, and Secrets Manager from a VPC normally routes traffic through the public internet, requiring internet gateways, NAT devices, or public IPs. This Skill guides the creation of VPC endpoints so traffic stays on the AWS private network. ## Core Features & Use Cases - Gateway Endpoint Creation: Sets up gateway endpoints for S3 and DynamoDB and associates them with route tables. - Interface Endpoint Creation: Provisions PrivateLink interface endpoints for services like EC2, SSM, and Secrets Manager with subnets, security groups, and DNS settings. - Validation and Troubleshooting: Verifies VPC and subnet existence, checks for duplicate endpoints, confirms endpoint availability, and diagnoses DNS, timeout, and policy issues. - Use Case: A team needs EC2 instances in a private subnet to reach S3 and Secrets Manager without internet exposure; the Skill walks through endpoint creation, security group rules, and connectivity testing with AWS CLI and SDK examples. ## Quick Start Ask the assistant to configure VPC endpoints for private access to S3 and Secrets Manager in your VPC, providing the VPC ID and subnet IDs.

Frequently Asked Questions about configuring-vpc-endpoints-for-private-aws-service-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a VPC endpoint for private S3 access?

Create a gateway VPC endpoint for S3 and associate it with your VPC route tables using the AWS CLI. The Skill validates the VPC, checks for existing endpoints, creates the gateway endpoint, and updates route tables so S3 traffic stays on the AWS network.

What is the difference between gateway and interface VPC endpoints?

Gateway endpoints support only S3 and DynamoDB and work by adding routes to route tables at no hourly cost. Interface endpoints use AWS PrivateLink with ENIs in subnets, support most other services like EC2 and Secrets Manager, and require security groups.

Which AWS services support gateway VPC endpoints?

Only Amazon S3 and DynamoDB support gateway endpoints. All other supported services, such as EC2, SSM, and Secrets Manager, require interface endpoints powered by AWS PrivateLink.

Why is my VPC interface endpoint DNS name not resolving?

DNS resolution fails when DNS hostnames or DNS resolution are disabled on the VPC, or the DHCP options set lacks correct domain name servers. Enable both DNS settings on the VPC and verify the DHCP options configuration.

Why do connections to my VPC endpoint time out?

Timeouts usually occur when security group rules do not allow HTTPS traffic on port 443 from the VPC CIDR, or route tables are not properly configured for gateway endpoints. Verify inbound security group rules and route table associations.