Integration

AWS CloudFront integration

Amazon CloudFront CDN API for managing content delivery distributions, cache behaviors, and invalidations. Create and configure distributions, manage origins, invalidate cached content, and monitor CDN performance.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in AWS CloudFront.Built from the 32 AWS CloudFront tools below, on the connection you add once.

Common AWS CloudFront use cases

  • automate function management
  • automate cache policy management
  • automate distribution management
  • automate origin access control management
  • automate invalidation management
  • automate resource management
  • list tag programmatically
  • Discover all edge data stores
  • get function programmatically
  • tag resource programmatically

What you can do with AWS CloudFront

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Function, 6 operations

  • create_functionCreate functionPOSTCreate a CloudFront Function (lightweight JavaScript function) for viewer request/response manipulation at edge locations
  • delete_functionDelete functionDELETEDelete a CloudFront Function. It must not be associated with any distribution
  • get_functionGet functionGETGet the code and metadata of a CloudFront Function
  • list_functionsList functionsGETList all CloudFront Functions in the account
  • publish_functionPublish functionPOSTPublish a CloudFront Function from DEVELOPMENT to LIVE stage, making it available for association with distributions
  • update_functionUpdate functionPUTUpdate the code or configuration of a CloudFront Function

Cache policy, 5 operations

  • create_cache_policyCreate cache policyPOSTCreate a cache policy defining what CloudFront includes in the cache key and TTL settings
  • delete_cache_policyDelete cache policyDELETEDelete a custom cache policy. It must not be attached to any cache behavior
  • get_cache_policyGet cache policyGETGet the configuration of a specific cache policy
  • list_cache_policiesList cache policiesGETList all cache policies (managed and custom) available in the account
  • update_cache_policyUpdate cache policyPUTUpdate an existing cache policy configuration

Distribution, 5 operations

  • create_distributionCreate distributionPOSTCreate a new CloudFront distribution with specified origins, cache behaviors, and settings
  • delete_distributionDelete distributionDELETEDelete a CloudFront distribution. The distribution must be disabled and deployed before deletion. Requires current ETag via If-Match header
  • get_distributionGet distributionGETGet detailed information about a specific CloudFront distribution including configuration, status, and ETag
  • list_distributionsList distributionsGETList all CloudFront distributions in the account. Returns paginated list with distribution IDs, domain names, status, and aliases
  • update_distributionUpdate distributionPUTUpdate the configuration of an existing CloudFront distribution. Requires current ETag via If-Match header

Origin access control, 5 operations

  • create_origin_access_controlCreate origin access controlPOSTCreate a new origin access control (OAC) for securing S3 or other origins
  • delete_origin_access_controlDelete origin access controlDELETEDelete an origin access control. It must not be associated with any distribution
  • get_origin_access_controlGet origin access controlGETGet details of a specific origin access control
  • list_origin_access_controlsList origin access controlsGETList all origin access controls (OAC) in the account used to authenticate CloudFront requests to origins
  • update_origin_access_controlUpdate origin access controlPUTUpdate an existing origin access control configuration

Invalidation, 3 operations

  • create_invalidationCreate invalidationPOSTCreate an invalidation to remove objects from CloudFront edge caches before their TTL expires
  • get_invalidationGet invalidationGETGet the status and details of an invalidation request
  • list_invalidationsList invalidationsGETList all invalidations for a distribution, paginated

Key value store, 2 operations

  • create_key_value_storeCreate key value storePOSTCreate a CloudFront KeyValueStore for storing key-value pairs accessible from CloudFront Functions.
  • list_key_value_storesList key value storesGETList all CloudFront KeyValueStores in the account.

Resource, 2 operations

  • tag_resourceTag resourcePOSTAdd tags to a CloudFront resource (distribution, streaming distribution, etc.) for organization and cost allocation
  • untag_resourceUntag resourcePOSTRemove tags from a CloudFront resource

Continuous deployment policy, 1 operation

  • create_continuous_deployment_policyCreate continuous deployment policyPOSTCreate a continuous deployment policy to safely route traffic to a staging distribution.

Distribution config, 1 operation

  • get_distribution_configGet distribution configGETGet the configuration of a distribution (without status info). Returns ETag needed for updates

Tag, 1 operation

  • list_tags_for_resourceList tags for resourceGETList all tags attached to a CloudFront resource

Vpc origin, 1 operation

  • create_vpc_originCreate vpc originPOSTCreate a VPC origin to deliver content from private VPC resources through CloudFront.

Use AWS CloudFront from Claude Code, Cursor or Codex

Connect AWS CloudFront in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AWS CloudFront operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect AWS CloudFront

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect AWS CloudFront once

    Add your AWS CloudFront connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

AWS CloudFront integration FAQ

What can you do with the AWS CloudFront integration?

LiveContext exposes 32 operations on AWS CloudFront, covering function, cache policy, distribution and origin access control. Common uses include automate function management, automate cache policy management and automate distribution management.

Popular integrations

Browse the whole catalog