Amazon Cloud WAN · Schema

CreateSiteToSiteVpnAttachmentRequest

Amazon Web ServicesCloud WANNetworkingWide Area NetworkSD-WAN

Properties

Name Type Description
CoreNetworkId string The ID of a core network where you're creating a site-to-site VPN attachment.
VpnConnectionArn string The ARN identifying the VPN attachment.
RoutingPolicyLabel string The routing policy label to apply to the Site-to-Site VPN attachment for traffic routing decisions.
NatGatewaySupport string Specifies whether to enable NAT gateway support on the Site-to-Site VPN attachment. To enable NAT gateway support, you must also specify at least one NAT rule. If you don't specify a value, NAT gatewa
NatSystemRouteSupport boolean Specifies whether the core network installs system routes for the NAT CIDR blocks of the attachment's NAT rules. System routes have a route type of SYSTEM. NAT is applied to traffic whether or not thi
NatGatewayRules array The NAT rules for the Site-to-Site VPN attachment, up to 50 rules.
Tags array The 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-site-to-site-vpn-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-site-to-site-vpn-attachment-request-schema.json",
  "title": "CreateSiteToSiteVpnAttachmentRequest",
  "x-generated": "2026-11-11",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/amazon-cloud-wan-operations-api-openapi.yml#/components/schemas/CreateSiteToSiteVpnAttachmentRequest",
  "type": "object",
  "properties": {
    "CoreNetworkId": {
      "type": "string",
      "description": "The ID of a core network where you're creating a site-to-site VPN attachment."
    },
    "VpnConnectionArn": {
      "type": "string",
      "description": "The ARN identifying the VPN attachment."
    },
    "RoutingPolicyLabel": {
      "type": "string",
      "description": "The routing policy label to apply to the Site-to-Site VPN attachment for traffic routing decisions."
    },
    "NatGatewaySupport": {
      "type": "string",
      "enum": [
        "ENABLE",
        "DISABLE"
      ],
      "description": "Specifies whether to enable NAT gateway support on the Site-to-Site VPN 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."
    },
    "NatSystemRouteSupport": {
      "type": "boolean",
      "description": "Specifies whether the core network installs system routes for the NAT CIDR blocks of the attachment's NAT rules. System routes have a route type of SYSTEM. NAT is applied to traffic whether or not this option is enabled. The default is true for VPN connections that use BGP and false for VPN connections that use static routing. If the VPN connection uses static routing, you must specify false or omit this parameter."
    },
    "NatGatewayRules": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/NatRuleRequest"
      },
      "description": "The NAT rules for the Site-to-Site VPN attachment, up to 50 rules."
    },
    "Tags": {
      "type": "array",
      "items": {
        "$ref": "#/$defs/Tag"
      },
      "description": "The tags associated with the request."
    },
    "ClientToken": {
      "type": "string",
      "description": "The client token associated with the request."
    }
  },
  "required": [
    "CoreNetworkId",
    "VpnConnectionArn"
  ],
  "$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."
        }
      }
    }
  }
}

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-site-to-site-vpn-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.