Amazon Route 53 Resolver · JSON Structure

Amazon Route53 Resolver Openapi Create Resolver Endpoint Request Structure

CreateResolverEndpointRequest schema from openapi

Type: object Properties: 7 Required: 4
DNSHybrid CloudNetworking

CreateResolverEndpointRequest is a JSON Structure definition published by Amazon Route 53 Resolver, describing 7 properties, of which 4 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

CreatorRequestId Name SecurityGroupIds Direction IpAddresses Tags ResolverEndpointType

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/amazon-route53-resolver/refs/heads/main/json-structure/amazon-route53-resolver-openapi-create-resolver-endpoint-request-structure.json",
  "description": "CreateResolverEndpointRequest schema from openapi",
  "type": "object",
  "properties": {
    "CreatorRequestId": {
      "allOf": [
        {
          "$ref": "#/components/schemas/CreatorRequestId"
        },
        {
          "description": "A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. <code>CreatorRequestId</code> can be any unique string, for example, a date/time stamp. "
        }
      ]
    },
    "Name": {
      "allOf": [
        {
          "$ref": "#/components/schemas/Name"
        },
        {
          "description": "A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console."
        }
      ]
    },
    "SecurityGroupIds": {
      "allOf": [
        {
          "$ref": "#/components/schemas/SecurityGroupIds"
        },
        {
          "description": "The ID of one or more security groups that you want to use to control access to this VPC. The security group that you specify must include one or more inbound rules (for inbound Resolver endpoints) or outbound rules (for outbound Resolver endpoints). Inbound and outbound rules must allow TCP and UDP access. For inbound access, open port 53. For outbound access, open the port that you're using for DNS queries on your network."
        }
      ]
    },
    "Direction": {
      "allOf": [
        {
          "$ref": "#/components/schemas/ResolverEndpointDirection"
        },
        {
          "description": "<p>Specify the applicable value:</p> <ul> <li> <p> <code>INBOUND</code>: Resolver forwards DNS queries to the DNS service for a VPC from your network</p> </li> <li> <p> <code>OUTBOUND</code>: Resolver forwards DNS queries from the DNS service for a VPC to your network</p> </li> </ul>"
        }
      ]
    },
    "IpAddresses": {
      "allOf": [
        {
          "$ref": "#/components/schemas/IpAddressesRequest"
        },
        {
          "description": "The subnets and IP addresses in your VPC that DNS queries originate from (for outbound endpoints) or that you forward DNS queries to (for inbound endpoints). The subnet ID uniquely identifies a VPC. "
        }
      ]
    },
    "Tags": {
      "allOf": [
        {
          "$ref": "#/components/schemas/TagList"
        },
        {
          "description": "A list of the tag keys and values that you want to associate with the endpoint."
        }
      ]
    },
    "ResolverEndpointType": {
      "allOf": [
        {
          "$ref": "#/components/schemas/ResolverEndpointType"
        },
        {
          "description": " For the endpoint type you can choose either IPv4, IPv6. or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses. "
        }
      ]
    }
  },
  "required": [
    "CreatorRequestId",
    "SecurityGroupIds",
    "Direction",
    "IpAddresses"
  ],
  "name": "CreateResolverEndpointRequest"
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure 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 Structure
curl "https://apis.io/api/v1/json-structures/amazon-route53-resolver-openapi-create-resolver-endpoint-request-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.