Terminal
Terminal/Skill
Sets up VPC endpoints with PrivateLink so resources reach S3, DynamoDB, and other AWS services without an internet gateway or public IPs.
By Amazon Web Services
Works with
npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-accessDomain 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.
To create and configure VPC endpoints for private AWS service access, follow the procedure exactly. See VPC endpoints configuration procedure.
Check security group rules, subnet configurations, and service availability in the region.
Verify DNS hostnames and DNS resolution are enabled on the VPC and that the DHCP options set has correct domain name servers.
Verify security group rules allow HTTPS traffic (port 443) and route tables are properly configured for gateway endpoints.
Review endpoint policies — default policies allow all access, but custom policies may be restrictive.