Amazon Cloud WAN · Schema

CreateVpcAttachmentRequest

Amazon Web ServicesCloud WANNetworkingWide Area NetworkSD-WAN

Properties

Name Type Description
CoreNetworkId string The ID of a core network for the VPC attachment.
VpcArn string The ARN of the VPC.
SubnetArns array The subnet ARN of the VPC attachment.
Options object
RoutingPolicyLabel string The routing policy label to apply to the VPC attachment for traffic routing decisions.
NatGatewaySupport string Specifies whether to enable NAT gateway support on the VPC attachment. To enable NAT gateway support, you must also specify at least one NAT rule. If you don't specify a value, NAT gateway support is
NatGatewayRules array The NAT rules for the VPC attachment, up to 50 rules.
Tags array The key-value tags associated with the request.
ClientToken string The client token associated with the request.
View JSON Schema on GitHub

JSON Schema

amazon-cloud-wan-create-vpc-attachment-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/amazon-cloud-wan/json-schema/amazon-cloud-wan-create-vpc-attachment-request-schema.json",
  "title": "CreateVpcAttachmentRequest",
  "x-generated": "2026-11-11",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/amazon-cloud-wan-vpc-attachments-api-openapi.yml#/components/schemas/CreateVpcAttachmentRequest",
  "type": "object",
  "properties": {
    "CoreNetworkId": {
      "type": "string",
      "description": "The ID of a core network for the VPC attachment."
    },
    "VpcArn": {
      "type": "string",
      "description": "The ARN of the VPC."
    },
    "SubnetArns": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The subnet ARN of the VPC attachment."
    },
    "Options": {
      "$ref": "#/$defs/VpcOptions"
    },
    "RoutingPolicyLabel": {
      "type": "string",
      "description": "The routing policy label to apply to the VPC attachment for traffic routing decisions."
    },
    "NatGatewaySupport": {
      "type": "string",
      "enum": [
        "ENABLE",
        "DISABLE"
      ],
      "description": "Specifies whether to enable NAT gateway support on the VPC attachment. To enable NAT gateway support, you must also specify at least one NAT rule. If you don't specify a value, NAT gateway support is disabled. Only the core network owner can configure NAT on an attachment."
    },
    "NatGatewayRules": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/NatRuleRequest"
      },
      "description": "The NAT rules for the VPC attachment, up to 50 rules."
    },
    "Tags": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/Tag"
      },
      "description": "The key-value tags associated with the request."
    },
    "ClientToken": {
      "type": "string",
      "description": "The client token associated with the request."
    }
  },
  "required": [
    "CoreNetworkId",
    "VpcArn",
    "SubnetArns"
  ],
  "$defs": {
    "NatRuleRequest": {
      "type": "object",
      "properties": {
        "RuleNumber": {
          "type": "integer",
          "description": "The rule number, from 1 to 32766. Each rule number must be unique for the attachment."
        },
        "MatchSourceCidr": {
          "type": "string",
          "description": "The IPv4 CIDR block to match against the source address of traffic from the attachment. The CIDR block can't overlap with the multicast range (224.0.0.0/4)."
        },
        "NatCidr": {
          "type": "string",
          "description": "The IPv4 CIDR block to translate matching source addresses to. The prefix length must be the same as the prefix length of MatchSourceCidr. The CIDR block must be within a private (RFC 1918) or shared address space (RFC 6598) range. The CIDR blocks of the NAT rules of an attachment can't overlap with each other."
        }
      },
      "required": [
        "RuleNumber",
        "MatchSourceCidr",
        "NatCidr"
      ]
    },
    "Tag": {
      "type": "object",
      "properties": {
        "Key": {
          "type": "string",
          "description": "The tag key. Constraints: Maximum length of 128 characters."
        },
        "Value": {
          "type": "string",
          "description": "The tag value. Constraints: Maximum length of 256 characters."
        }
      }
    },
    "VpcOptions": {
      "type": "object",
      "properties": {
        "Ipv6Support": {
          "type": "boolean",
          "description": "Indicates whether IPv6 is supported."
        },
        "ApplianceModeSupport": {
          "type": "boolean",
          "description": "Indicates whether appliance mode is supported. If enabled, traffic flow between a source and destination use the same Availability Zone for the VPC attachment for the lifetime of that flow. The default value is false."
        },
        "DnsSupport": {
          "type": "boolean",
          "description": "Indicates whether DNS is supported."
        },
        "SecurityGroupReferencingSupport": {
          "type": "boolean",
          "description": "Indicates whether security group referencing is enabled for this VPC attachment. The default is true. However, at the core network policy-level the default is set to false."
        }
      }
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/amazon-cloud-wan-create-vpc-attachment-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.