AWS App Mesh · JSON Structure

App Mesh Http Route Match Structure

An object that represents the requirements for a route to match HTTP requests for a virtual router.

Type: object Properties: 7

DeprecatedEnvoyMicroservicesNetworkingService Mesh

HttpRouteMatch is a JSON Structure definition published by AWS App Mesh, describing 7 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

headers method path port prefix queryParameters scheme

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

JSON Structure

{
  "type": "object",
  "properties": {
    "headers": {
      "allOf": [
        {
          "$ref": "#/components/schemas/HttpRouteHeaders"
        },
        {
          "description": "The client request headers to match on."
        }
      ]
    },
    "method": {
      "allOf": [
        {
          "$ref": "#/components/schemas/HttpMethod"
        },
        {
          "description": "The client request method to match on. Specify only one."
        }
      ]
    },
    "path": {
      "allOf": [
        {
          "$ref": "#/components/schemas/HttpPathMatch"
        },
        {
          "description": "The client request path to match on."
        }
      ]
    },
    "port": {
      "allOf": [
        {
          "$ref": "#/components/schemas/ListenerPort"
        },
        {
          "description": "The port number to match on."
        }
      ]
    },
    "prefix": {
      "allOf": [
        {
          "$ref": "#/components/schemas/String"
        },
        {
          "description": "Specifies the path to match requests with. This parameter must always start with <code>/</code>, which by itself matches all requests to the virtual service name. You can also match for path-based routing of requests. For example, if your virtual service name is <code>my-service.local</code> and you want the route to match requests to <code>my-service.local/metrics</code>, your prefix should be <code>/metrics</code>."
        }
      ]
    },
    "queryParameters": {
      "allOf": [
        {
          "$ref": "#/components/schemas/HttpQueryParameters"
        },
        {
          "description": "The client request query parameters to match on."
        }
      ]
    },
    "scheme": {
      "allOf": [
        {
          "$ref": "#/components/schemas/HttpScheme"
        },
        {
          "description": "The client request scheme to match on. Specify only one. Applicable only for HTTP2 routes."
        }
      ]
    }
  },
  "description": "An object that represents the requirements for a route to match HTTP requests for a virtual router.",
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/aws-app-mesh/refs/heads/main/json-structure/app-mesh-http-route-match-structure.json",
  "name": "HttpRouteMatch"
}

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/app-mesh-http-route-match-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 email required.

GitHub Google LinkedIn

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