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.

creating-production-vpc-multi-az - Skill

Name: creating-production-vpc-multi-az
Author: aws

Imported from aws/agent-toolkit-for-aws (skills/specialized-skills/networking-and-content-delivery-skills/creating-production-vpc-multi-az/SKILL.md) via skills.sh. Install upstream with npx skills add aws/agent-toolkit-for-aws --skill creating-production-vpc-multi-az. Copyright stays with the author.

Creating a Production-Ready VPC Across Multiple Availability Zones

Overview

Domain expertise for creating production-ready VPC infrastructure distributed across multiple Availability Zones. Covers VPC creation with DNS support, public and private subnet layout with automatic CIDR calculation, internet gateway, NAT gateways for high-availability outbound access, route table configuration, and tiered security groups following AWS Well-Architected principles.

Create a production VPC

To create a fully configured multi-AZ VPC with public/private subnets, NAT gateways, route tables, and security groups, follow the procedure exactly. See Production VPC creation procedure.

Key parameters:

vpc_name (required): Name prefix for all resources
region (required): Target AWS region
allowed_web_cidrs (required): CIDR blocks allowed for web access — allow 0.0.0.0/0 only if explicitly requested
vpc_cidr (optional, default 10.0.0.0/16): VPC CIDR block
availability_zones (optional, default 3): Number of AZs (2–6)
environment (required): Environment tag
enable_ssh_access (optional, default false): Whether to create SSH security group

Troubleshooting

Insufficient Availability Zones

The target region must have at least 2 available AZs. Use aws ec2 describe-availability-zones to verify.

NAT Gateway creation delays

NAT Gateways can take several minutes to become available. The procedure waits for availability before configuring route tables.

Security group CIDR warnings

The procedure warns about 0.0.0.0/0 for web access CIDRs and recommends specific IP ranges for production workloads, but allows it if explicitly requested.

Install creating-production-vpc-multi-az 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-creating-production-vpc-multi-az", "kind": "skill", "name": "creating-production-vpc-multi-az", "description": "Creates a production-ready VPC with public and private subnets across multiple Availability Zones, including internet gateway, NAT gateways, route tables, and security groups following AWS Well-Architected principles. Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution.", "publisher": "aws", "version": "1.0.0", "capabilities": { "domains": [ "data_analysis", "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Creates a production-ready VPC with public and private subnets across multiple Availability Zones, including internet gateway, NAT gateways, route tables, and security groups following AWS Well-Architected principles. Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution." ], "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/creating-production-vpc-multi-az/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/aws/agent-toolkit-for-aws/creating-production-vpc-multi-az", "key": "aws/agent-toolkit-for-aws/skills/specialized-skills/networking-and-content-delivery-skills/creating-production-vpc-multi-az/SKILL.md" } }, "instructions": "# Creating a Production-Ready VPC Across Multiple Availability Zones\n\n## Overview\n\nDomain expertise for creating production-ready VPC infrastructure distributed across\nmultiple Availability Zones. Covers VPC creation with DNS support, public and private\nsubnet layout with automatic CIDR calculation, internet gateway, NAT gateways for\nhigh-availability outbound access, route table configuration, and tiered security\ngroups following AWS Well-Architected principles.\n\n## Create a production VPC\n\nTo create a fully configured multi-AZ VPC with public/private subnets, NAT gateways,\nroute tables, and ", "cost": { "context_tokens": 435 } }

creating-production-vpc-multi-az

About

Creating a Production-Ready VPC Across Multiple Availability Zones

Overview

Create a production VPC

Troubleshooting

Insufficient Availability Zones

NAT Gateway creation delays

Security group CIDR warnings

Install creating-production-vpc-multi-az 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

Use it

Manifest

Reviews