How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

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

Name: configuring-vpc-endpoints-for-private-aws-service-access
Author: aws

Imported from aws/agent-toolkit-for-aws (skills/specialized-skills/networking-and-content-delivery-skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.md) via skills.sh. Install upstream with npx skills add aws/agent-toolkit-for-aws --skill configuring-vpc-endpoints-for-private-aws-service-access. Copyright stays with the author.

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.

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.

Install configuring-vpc-endpoints-for-private-aws-service-access and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "aws-agent-toolkit-for-aws-configuring-vpc-endpoints-for-5078dc", "kind": "skill", "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.", "publisher": "aws", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/aws/agent-toolkit-for-aws", "path": "skills/specialized-skills/networking-and-content-delivery-skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/aws/agent-toolkit-for-aws/configuring-vpc-endpoints-for-private-aws-service-access", "key": "aws/agent-toolkit-for-aws/skills/specialized-skills/networking-and-content-delivery-skills/configuring-vpc-endpoints-for-private-aws-service-access/SKILL.md" } }, "instructions": "# Configuring VPC Endpoints for Private AWS Service Access\n\n## Overview\n\nDomain expertise for configuring VPC endpoints to enable private access to AWS services\nwithout routing traffic through the internet. Covers both gateway endpoints (S3, DynamoDB)\nand interface endpoints (EC2, SSM, Secrets Manager, etc.) powered by AWS PrivateLink.\n\n## Configure VPC endpoints\n\nTo create and configure VPC endpoints for private AWS service access, follow the procedure exactly.\nSee [VPC endpoints configuration procedure](references/configure-vpc-endpoints-for-private-aws-service-access.md).\n\n## Troubleshootin", "cost": { "context_tokens": 288 } }

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

About

Configuring VPC Endpoints for Private AWS Service Access

Overview

Configure VPC endpoints

Troubleshooting

Endpoint not available

DNS resolution issues

Connection timeouts

Policy restrictions

Use it

Install configuring-vpc-endpoints-for-private-aws-service-access and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews