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

Configure VPC gateway and interface endpoints for private AWS service access.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill configuring-vpc-endpoints-for-private-aws-service-access
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/mreferre/aws-agent-toolkit-skills/tree/main/.kiro/skills/configuring-vpc-endpoints-for-private-aws-service-access
Command: npx skills add https://github.com/mreferre/aws-agent-toolkit-skills --skill configuring-vpc-endpoints-for-private-aws-service-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of needing secure, private connectivity to AWS services without sending traffic through an internet gateway, NAT device, or public IPs.

Core Features & Use Cases

  • PrivateLink-powered connectivity: Sets up both interface and gateway VPC endpoints so resources in your VPC can reach AWS services over private networking.
  • Correct networking and security wiring: Configures subnet associations, security group inbound rules for HTTPS (443), and route table associations for gateway endpoints.
  • Reliable operation and diagnostics: Includes troubleshooting guidance for common failures like endpoint not available, DNS resolution issues, timeouts, and overly restrictive policies.

Use case example: You want EC2 instances in private subnets to access S3 and DynamoDB reliably while also reaching EC2/SSM/Secrets Manager APIs without exposing the instances to the public internet.

Quick Start

Ask the AI to configure VPC endpoints for your VPC using your VPC ID, interface endpoint subnets, and desired service names, then verify that the created endpoints reach the expected services over DNS.

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 configure VPC endpoints for private AWS service access?

To configure VPC endpoints for private AWS service access, set up gateway endpoints for S3 and DynamoDB and interface endpoints for EC2, SSM, and Secrets Manager. You need to provision security group HTTPS rules, associate route tables, and enable DNS resolution.

What is the difference between gateway and interface VPC endpoints?

Gateway VPC endpoints are used for S3 and DynamoDB and require route table association, while interface VPC endpoints support services like EC2 and SSM by using security group inbound rules for HTTPS traffic and private DNS resolution.

Can EC2 instances in private subnets reach AWS services without a NAT or internet gateway?

Yes, EC2 instances in private subnets can reach AWS services without a NAT or internet gateway by using VPC endpoints powered by AWS PrivateLink to route traffic privately within the AWS network.

Why is my VPC endpoint timing out or failing DNS resolution?

VPC endpoint timeouts or DNS resolution failures often occur due to disabled private DNS settings, missing HTTPS security group rules on interface endpoints, or overly restrictive endpoint policies blocking traffic.

Do I need to validate my VPC subnets before provisioning interface endpoints?

Yes, you must validate your VPC and existing endpoints using AWS CLI checks before provisioning interface endpoints to ensure proper subnet associations and avoid overlapping endpoint configurations.

What is the best way to test VPC endpoint connectivity after deployment?

The best way to test VPC endpoint connectivity is by running AWS CLI validation commands to check endpoint availability and performing DNS testing to verify private access to the target AWS services.