Amazon EC2 Auto Scaling · JSON Structure

Ec2 Auto Scaling Instance Metadata Options Structure

The metadata options for the instances. For more information, see Configuring the Instance Metadata Options in the Amazon EC2 Auto Scaling User Guide.

Type: object Properties: 3
Amazon Web ServicesAuto-ScalingComputeEC2High AvailabilityScaling

InstanceMetadataOptions is a JSON Structure definition published by Amazon EC2 Auto Scaling, describing 3 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

HttpTokens HttpPutResponseHopLimit HttpEndpoint

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-ec2-auto-scaling/refs/heads/main/json-structure/ec2-auto-scaling-instance-metadata-options-structure.json",
  "name": "InstanceMetadataOptions",
  "description": "The metadata options for the instances. For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-config.html#launch-configurations-imds\">Configuring the Instance Metadata Options</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.",
  "type": "object",
  "properties": {
    "HttpTokens": {
      "allOf": [
        {
          "$ref": "#/components/schemas/InstanceMetadataHttpTokensState"
        },
        {
          "description": "<p>The state of token usage for your instance metadata requests. If the parameter is not specified in the request, the default state is <code>optional</code>.</p> <p>If the state is <code>optional</code>, you can choose to retrieve instance metadata with or without a signed token header on your request. If you retrieve the IAM role credentials without a token, the version 1.0 role credentials are returned. If you retrieve the IAM role credentials using a valid signed token, the version 2.0 role credentials are returned.</p> <p>If the state is <code>required</code>, you must send a signed token header with any instance metadata retrieval requests. In this state, retrieving the IAM role credentials always returns the version 2.0 credentials; the version 1.0 credentials are not available.</p>"
        }
      ]
    },
    "HttpPutResponseHopLimit": {
      "allOf": [
        {
          "$ref": "#/components/schemas/InstanceMetadataHttpPutResponseHopLimit"
        },
        {
          "description": "<p>The desired HTTP PUT response hop limit for instance metadata requests. The larger the number, the further instance metadata requests can travel.</p> <p>Default: 1</p>"
        }
      ]
    },
    "HttpEndpoint": {
      "allOf": [
        {
          "$ref": "#/components/schemas/InstanceMetadataEndpointState"
        },
        {
          "description": "<p>This parameter enables or disables the HTTP metadata endpoint on your instances. If the parameter is not specified, the default state is <code>enabled</code>.</p> <note> <p>If you specify a value of <code>disabled</code>, you will not be able to access your instance metadata. </p> </note>"
        }
      ]
    }
  }
}

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/ec2-auto-scaling-instance-metadata-options-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.