AWS Elemental MediaStore

Name: AWS Elemental MediaStore API
Brand: AWS Elemental MediaStore
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject Storagehmac21 EndpointsREST

For Agents

Provision and govern low-latency MediaStore containers used as origins for live and on-demand media workflows.

Quickstart

Get started with AWS Elemental MediaStore in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a mediastore container"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS Elemental MediaStore API.

Create and delete MediaStore containers used as live and VOD media origins

Attach container policies that grant cross-account or signed access to media

Configure CORS policies so browser-based players can fetch segments and manifests

Set lifecycle policies that expire stale segments and recordings automatically

GET STARTED

Start building with AWS Elemental MediaStore API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Elemental MediaStore, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Elemental MediaStore, keeping it validated and agent-ready. MediaStore is a low-latency object store optimized for media workflows — live origin storage, ingest from encoders, and delivery to packagers. Containers are the top-level namespace; each container has a unique data endpoint and supports container policies, CORS policies, lifecycle policies, and metric policies. The service is designed for high-throughput sequential reads and writes typical of streaming workloads rather than archival use cases.

Use Cases

Patterns agents use AWS Elemental MediaStore API for, with concrete tasks.

★ Live Streaming Origin Storage

Live broadcasters use MediaStore containers as the origin for streaming segments emitted by encoders such as AWS Elemental MediaLive. Each container exposes a low-latency HTTP endpoint that downstream packagers and CDNs read from in near real time. CORS and container policies control which origins and roles can fetch segments, and lifecycle policies expire stale recordings to keep storage costs flat.

Call CreateContainer with ContainerName='live-event-2026-finals', then PutLifecyclePolicy with a rule that expires objects older than 86400 seconds

Browser Player CORS Configuration

Web video apps that fetch HLS or DASH manifests directly from the MediaStore origin need CORS rules permitting the player's domain. PutCorsPolicy attaches a JSON CORS configuration to the container, listing AllowedOrigins, AllowedMethods, AllowedHeaders, and MaxAgeSeconds. The configuration takes effect immediately, so operators can react to new player domains without redeploying anything.

Call PutCorsPolicy on container 'live-event-2026-finals' with an AllowedOrigins list of ['https://app.example.com'] and AllowedMethods ['GET','HEAD']

Multi-Account Origin Sharing

Larger organizations split production and distribution into separate AWS accounts. PutContainerPolicy attaches an IAM policy directly to a MediaStore container that grants a CDN account or partner role permission to GetObject from the container. This lets the producing team own the storage and the distributing team operate the delivery without sharing credentials.

Call PutContainerPolicy on container 'live-events' with a policy granting mediastore:GetObject to the partner account principal arn:aws:iam::123456789012:role/cdn-origin

AI Agent Storage Operations

Operations agents call MediaStore through Jentic to provision new containers for upcoming events, attach standard CORS and lifecycle policies, and verify state before broadcasts begin. Jentic isolates AWS keys and exposes the container, policy, CORS, and lifecycle operations as discoverable tools, so the agent can answer 'spin up an origin for tomorrow's launch' without learning the AWS SDK.

Search Jentic for 'create a mediastore container', load CreateContainer, and execute it with the event-specific name then chain PutCorsPolicy with the standard player CORS config

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for aws elemental mediastore, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=MediaStore_20170901.CreateContainer

Create a new MediaStore container

POST

/#X-Amz-Target=MediaStore_20170901.DescribeContainer

Describe a container's endpoint and status

POST

/#X-Amz-Target=MediaStore_20170901.PutContainerPolicy

Attach an IAM policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.PutCorsPolicy

Attach a CORS policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.PutLifecyclePolicy

Attach a lifecycle policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.PutMetricPolicy

Attach a CloudWatch metric policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.DeleteContainer

Delete a MediaStore container

POST

/#X-Amz-Target=MediaStore_20170901.CreateContainer

Create a new MediaStore container

POST

/#X-Amz-Target=MediaStore_20170901.DescribeContainer

Describe a container's endpoint and status

POST

/#X-Amz-Target=MediaStore_20170901.PutContainerPolicy

Attach an IAM policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.PutCorsPolicy

Attach a CORS policy to a container

POST

/#X-Amz-Target=MediaStore_20170901.PutLifecyclePolicy

Attach a lifecycle policy to a container

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS keys are stored encrypted in the Jentic vault. Each MediaStore call is signed with Signature Version 4 server-side, so the agent never holds raw keys, and IAM scoping limits which containers it can create or modify.

Intent-based discovery

Agents search by intent (e.g. 'create a mediastore container' or 'attach a cors policy') and Jentic returns the matching MediaStore operations with their input schemas, including the JSON shape expected by container, CORS, and lifecycle policy fields.

Time to first call

Direct integration: under a day for IAM and basic container provisioning, more for cross-account policy work. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Elemental MediaPackage VOD

MediaPackage VOD packages content that may be served from MediaStore

Use MediaPackage VOD downstream when the agent needs to package content stored in MediaStore into HLS, DASH, or CMAF outputs.

Alternative

Bunny.net

Bunny.net offers low-latency CDN-attached media storage outside AWS

Choose Bunny.net when the agent's stack is not AWS-native; choose MediaStore when integration with AWS Elemental services and IAM is the priority.

Complementary

Amazon CloudWatch

CloudWatch ingests metric policies set on MediaStore containers

Use CloudWatch when the agent needs to alert on per-container request rate, error counts, or 4xx/5xx ratios that MediaStore's metric policies emit.

FAQs

Specific to using AWS Elemental MediaStore API through Jentic.

Why is there no official OpenAPI spec for AWS Elemental MediaStore?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Elemental MediaStore via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MediaStore API use?

MediaStore control-plane operations use AWS Signature Version 4 (HMAC) with an access key ID and secret access key scoped via IAM. Object-level operations against the container's data endpoint are signed the same way. Through Jentic, those keys live in the encrypted vault and Jentic signs each request server-side.

Can I attach a CORS policy with the MediaStore API?

Yes. Call PutCorsPolicy with a CorsPolicy array specifying AllowedOrigins, AllowedMethods, AllowedHeaders, MaxAgeSeconds, and ExposeHeaders. GetCorsPolicy returns the current configuration, and DeleteCorsPolicy removes it. Changes take effect immediately for new requests.

What are the rate limits for the MediaStore API?

AWS does not document explicit per-second control-plane limits in this spec. Per-container request limits exist on the data endpoint and scale with usage; the service is sized for live streaming throughput. See the AWS service quotas console for region-specific values.

How do I create a container and attach a policy through Jentic?

Search Jentic for 'create a mediastore container' to surface CreateContainer. Load the schema with the Jentic SDK (pip install jentic), execute it with the desired ContainerName, then chain PutContainerPolicy with the JSON policy granting the consuming role mediastore:GetObject.

Is AWS Elemental MediaStore free?

No. MediaStore charges per GB stored per month and per HTTP request, with separate rates for PUT, GET, and DELETE operations. There is no free tier — see the AWS MediaStore pricing page for current rates by region.