Amazon AppSync · Schema

GetApiCacheResponse

Amazon AppSyncGraphQLAPI ManagementServerlessAmazon Web Services

Properties

Name Type Description
apiCache object
View JSON Schema on GitHub

JSON Schema

amazon-appsync-get-api-cache-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/amazon-appsync/json-schema/amazon-appsync-get-api-cache-response-schema.json",
  "title": "GetApiCacheResponse",
  "x-generated": "2026-11-11",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/amazon-appsync-apicaches-api-openapi.yml#/components/schemas/GetApiCacheResponse",
  "type": "object",
  "properties": {
    "apiCache": {
      "$ref": "#/$defs/ApiCache"
    }
  },
  "$defs": {
    "ApiCache": {
      "type": "object",
      "properties": {
        "ttl": {
          "type": "integer",
          "description": "TTL in seconds for cache entries. Valid values are 1–3,600 seconds."
        },
        "apiCachingBehavior": {
          "type": "string",
          "enum": [
            "FULL_REQUEST_CACHING",
            "PER_RESOLVER_CACHING",
            "OPERATION_LEVEL_CACHING"
          ],
          "description": "Caching behavior. FULL_REQUEST_CACHING: All requests from the same user are cached. Individual resolvers are automatically cached. All API calls will try to return responses from the cache. PER_RESOLVER_CACHING: Individual resolvers that you specify are cached. OPERATION_LEVEL_CACHING: Full requests are cached together and returned without executing resolvers."
        },
        "transitEncryptionEnabled": {
          "type": "boolean",
          "description": "Transit encryption flag when connecting to cache. You cannot update this setting after creation."
        },
        "atRestEncryptionEnabled": {
          "type": "boolean",
          "description": "At-rest encryption flag for cache. You cannot update this setting after creation."
        },
        "type": {
          "type": "string",
          "enum": [
            "T2_SMALL",
            "T2_MEDIUM",
            "R4_LARGE",
            "R4_XLARGE",
            "R4_2XLARGE",
            "R4_4XLARGE",
            "R4_8XLARGE",
            "SMALL",
            "MEDIUM",
            "LARGE",
            "XLARGE",
            "LARGE_2X",
            "LARGE_4X",
            "LARGE_8X",
            "LARGE_12X"
          ],
          "description": "The cache instance type. Valid values are SMALL MEDIUM LARGE XLARGE LARGE_2X LARGE_4X LARGE_8X (not available in all regions) LARGE_12X Historically, instance types were identified by an EC2-style value. As of July 2020, this is deprecated, and the generic identifiers above should be used. The following legacy instance types are available, but their use is discouraged: T2_SMALL: A t2.small instance type. T2_MEDIUM: A t2.medium instance type. R4_LARGE: A r4.large instance type. R4_XLARGE: A r4.xlarge instance type. R4_2XLARGE: A r4.2xlarge instance type. R4_4XLARGE: A r4.4xlarge instance type. "
        },
        "status": {
          "type": "string",
          "enum": [
            "AVAILABLE",
            "CREATING",
            "DELETING",
            "MODIFYING",
            "FAILED"
          ],
          "description": "The cache instance status. AVAILABLE: The instance is available for use. CREATING: The instance is currently creating. DELETING: The instance is currently deleting. MODIFYING: The instance is currently modifying. FAILED: The instance has failed creation."
        },
        "healthMetricsConfig": {
          "type": "string",
          "enum": [
            "ENABLED",
            "DISABLED"
          ],
          "description": "Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include: NetworkBandwidthOutAllowanceExceeded: The network packets dropped because the throughput exceeded the aggregated bandwidth limit. This is useful for diagnosing bottlenecks in a cache configuration. EngineCPUUtilization: The CPU utilization (percentage) allocated to the Redis process. This is useful for diagnosing bottlenecks in a cache configuration. Metrics will be recorded by API ID. You can set the value to ENABLED or DISABLED."
        }
      }
    }
  }
}

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-appsync-get-api-cache-response"
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.