Run AWS media workflows
with a governed agent
Lunen agents work in MediaConvert, MediaLive and the rest of AWS Elemental Media Services through the AWS Media Services MCP server, in a chat or on a schedule. They act as the member who connected them, follow the policy you set for each tool, and can use a model on Amazon Bedrock, billed to your AWS account.
Stop running media ops
one console tab at a time
The agent reads job history and channel state, and makes the changes you trust it with. You decide, tool by tool, what runs on its own and what waits for a person.
Without Lunen: Finding out why last night's transcodes failed means opening MediaConvert, filtering the job list, and decoding errors one job at a time.
With Lunen: Ask which jobs failed and why. The agent lists the night's MediaConvert jobs, reads each error, and answers in plain language.
Without Lunen: Getting a live channel ready is a console runbook: check the inputs, start the channel, confirm it is running. Someone has to be awake to do it.
With Lunen: A scheduled agent checks the MediaLive channel and its inputs before the event and starts it on time, on its own or once the producer on call approves.
Without Lunen: Re-encoding a batch for a new rendition means hand-editing job settings and hoping nothing else in the template changed.
With Lunen: Describe the outputs you need. The agent builds each MediaConvert job from your existing template and submits it, with every job's full settings in the run log.
Without Lunen: Giving an AI assistant AWS access usually means a local proxy on someone's laptop, their personal credentials, no policy on what it can run, and no shared record of what it did.
With Lunen: Each member connects through your IAM Identity Center with their own account and role. IAM decides what is possible, and CloudTrail and Lunen's audit log both record who acted.
Ask your media stack a question
Ask in plain language and get answers from live MediaConvert and MediaLive data, with the same identity, policies and audit log behind every call.
Media ops questions
Ask anything...
Claude Sonnet 4.6What you can do on AWS Media Services
Work an agent can take on once AWS Media Services is connected, whether you ask in a chat or put it on a schedule.
Failed job triage
Ask why jobs failed overnight. The agent pulls the MediaConvert job list, groups failures by error, and points to the input or setting behind each one.
Live event readiness
Before a broadcast window, the agent checks the MediaLive channel, its inputs and its destinations, and hands back a go or no-go with the reasons.
Batch transcodes
Give it a list of source files and a job template. It creates one MediaConvert job per file and reports back with every job ID.
Idle channel sweep
List every MediaLive channel that is running and how long it has been up, and stop the ones left on after an event.
Packaging and ad insertion checks
Read MediaPackage endpoints and MediaTailor playback configurations side by side, and flag any setting that differs from what you expect.
Channel schedule updates
Add or change actions on a MediaLive channel's schedule, like an input switch or an SCTE-35 splice, ahead of air.
Use Amazon Bedrock as your model provider
An administrator connects your organization's AWS account once. The Bedrock models it can use appear in every model picker in Lunen, and nothing runs on Bedrock until someone picks one.
The models your account can use
Lunen looks up the models your AWS account can reach, from Anthropic, Amazon, Mistral, DeepSeek, Qwen and others, and lists each one by name with Amazon Bedrock beside it.
Amazon Bedrock
- Claude Sonnet 4.6 · Amazon Bedrock
- Nova 2 Lite · Amazon Bedrock
- Mistral Large 3 · Amazon Bedrock
- DeepSeek V3.2 · Amazon Bedrock
- gpt-oss-120b · Amazon Bedrock
No AWS keys to hand over
You create an IAM role that trusts Lunen's role under an external ID minted for your organization. Lunen assumes it to reach Bedrock and never holds an access key.
Geographic or global routing
Geographic routing keeps inference inside your region's geography. Global routing can send it to any region, at a lower price.
Billed to your AWS account
Model calls run under your role, so Bedrock usage lands on your AWS bill next to the rest of your media spend.
Connected in three steps
- 1In Settings, then Access, choose Set up Amazon Bedrock and copy the trust and permission policies Lunen shows.
- 2Create an IAM role in your AWS account with those two policies.
- 3Paste the role ARN and region, pick routing, then Save and look up models.
Why run your AWS agents in Lunen
It acts as the person
Each member connects their own AWS account and role. An agent can do what that role can do and nothing more, and CloudTrail attributes every call to them.
You decide what runs on its own
Every media action is its own tool with its own policy. Allow the ones a trusted agent runs end to end, and set the rest to Approve so a reviewer sees the parameters first.
In a chat or on a schedule
Ask a question when you need an answer, or put the same work on a schedule so the overnight transcode check is done before the morning standup.
One record for every tool
AWS calls land in the same audit log as every other tool: who acted, which agent ran, what was approved, and which model answered.
Put an agent on your media pipeline
Lunen is in early access with a small group of design partners. Tell us how your team works on AWS and we'll set up a call.