vLLM-Omni links real-time image generation and asynchronous video generation on SageMaker
AWS shows an end-to-end path from FLUX.2-klein still images to asynchronous Wan2.1-VACE video generation.
Key takeaways
AWS published a September 28 workflow for image and video generation with vLLM-Omni on Amazon SageMaker AI. Two endpoints are deployed from the same Deep Learning Container: FLUX.2-klein-4B runs as a real-time image endpoint, while Wan2.1-VACE-1.3B runs asynchronously for video. The generated still image and a motion prompt are submitted to the video endpoint, and the resulting MP4 is stored in Amazon S3, with an optional Streamlit interface for demonstration. The shared container simplifies framework packaging, but production teams still need separate capacity, queue, timeout, moderation, content-rights, retention, and idle-cost controls for the real-time and asynchronous stages, plus traceability from every final video back to its prompts and source asset.
Direct answer
AWS published a September 28 workflow for image and video generation with vLLM-Omni on Amazon SageMaker AI. Two endpoints are deployed from the same Deep Learning Container: FLUX.2-klein-4B runs as a real-time image endpoint, while Wan2.1-VACE-1.3B runs asynchronously for video. The generated still image and a motion prompt are submitted to the video endpoint, and the resulting MP4 is stored in Amazon S3, with an optional Streamlit interface for demonstration. The shared container simplifies framework packaging, but production teams still need separate capacity, queue, timeout, moderation, content-rights, retention, and idle-cost controls for the real-time and asynchronous stages, plus traceability from every final video back to its prompts and source asset.
Verified facts
AWS published a SageMaker AI image-and-video workflow using vLLM-Omni on September 28, 2026.
The same container deploys a real-time FLUX.2-klein-4B image endpoint and an asynchronous Wan2.1-VACE-1.3B video endpoint.
A still image and motion prompt are submitted to the video endpoint, with the completed MP4 retrieved from Amazon S3.
What changed
- One container supports both model types
- Images use a real-time endpoint
- Video uses an asynchronous endpoint
- Completed media is delivered through S3
Impact for AI users
Treat image and video generation as separate services: validate the first for interactive latency and concurrency, and the second for queue time, completion rate, and cost per accepted video. Store prompts, model versions, source images, rights evidence, and moderation results for every job. Add authorization checks for people, brands, and uploaded assets, idle-endpoint shutdown rules, and idempotent retries that do not overwrite accepted outputs.
Operating checklist
- Separate image and video metrics
- Record prompts, models, and rights
- Add moderation and safe retries
- Control idle endpoint cost
AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance
FAQ
Does one container mean only one endpoint is needed?
No. The example still deploys separate real-time image and asynchronous video endpoints.
Where is the completed video stored?
The workflow writes the completed MP4 to Amazon S3 for retrieval by the client.
Summary
A shared container unifies packaging, but real-time images and asynchronous video still need distinct capacity, moderation, and cost controls.
This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.
What this means for everyday users
Treat image and video generation as separate services: validate the first for interactive latency and concurrency, and the second for queue time, completion rate, and cost per accepted video. Store prompts, model versions, source images, rights evidence, and moderation results for every job. Add authorization checks for people, brands, and uploaded assets, idle-endpoint shutdown rules, and idempotent retries that do not overwrite accepted outputs.
Tools you may use
Related tutorials
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
SageMaker Studio Simplifies New-Customer Access: Credits, Setup, and Cost Boundaries
AWS announced a simplified path into Amazon SageMaker Studio for new customers on October 19, 2026. Eligible users can sign up with Amazon, Apple, GitHub, Google, or email in two or three steps, and most do not need to enter a credit card first. Studio is created in about 20 seconds. New customers receive $100 in Free Tier credits and may earn another $100; the free period ends after six months or when credits are exhausted, and resource usage then stops automatically. This article provides a bounded first-experiment checklist covering account eligibility, GPU quota visibility, endpoint shutdown, credit monitoring, and the decision point before a paid upgrade.
Smartsheet MCP Is Generally Available for Amazon Quick and Kiro Workflows
AWS has published a guide to the generally available Smartsheet MCP Server, which exposes more than forty tools for reading, writing, and managing sheets, rows, columns, and automations. Business users can connect through Amazon Quick, while developers can configure the server in Kiro. This article compares the two paths, lists the documented account, authentication, and regional requirements, and proposes a safe first task: identify blocked work and produce a review checklist without writing changes. Only after results, user permissions, and organization controls are verified should a team enable a narrowly scoped write action. Natural-language requests do not grant extra access, and a connected agent should not be treated as an unrestricted project administrator.
When Should an AI Agent Act Autonomously? A Scope, Know, Bound, Observe Checklist
An AI agent should receive more autonomy only when its actions can be verified, not because one demonstration looked successful. AWS describes a Trust in Depth framework organized around four lifecycle questions: Scope, Know, Bound, and Observe. This durable guide turns those questions into an operational checklist for a small team. Using an internal task-status update as the example, it identifies evidence required before launch, controls during execution, records after execution, and conditions that should stop the agent and request human review. Precise rules can sometimes be tested or formally checked, while tone, sensitive context, and high-impact decisions still require judgment. The objective is bounded, reviewable autonomy rather than either constant approval or unrestricted action.
Reflection Beam Arrives on AWS: How to Choose an Agentic Coding Deployment
AWS introduced Reflection AI's Beam on October 16, 2026 as an open-weight model for agentic coding and long-horizon work. Beam is designed to resolve software issues, modify code, call tools, interpret intermediate results, and continue multi-step workflows. AWS describes a sparse mixture-of-experts architecture with 501 billion total parameters, 23 billion active parameters, and an effective one-million-token context length reported by Reflection. Weights are released under Apache 2.0 in BF16, FP8, and NVFP4 variants. This guide separates the managed SageMaker JumpStart path from the more controllable HyperPod route and explains the operational evidence teams should collect before trusting either in real projects.
Nine-Stage AI Agent Evaluation Checklist: From First Commit to Production Drift
AWS published a nine-stage production AI-agent evaluation framework built around Amazon Bedrock AgentCore on October 16, 2026. It follows an agent from defining quality and comparing experiments through merge checks, deployment gates, canary scoring, adversarial testing, drift detection, live pulse monitoring, and feedback-driven improvement. The framework evaluates five dimensions—safety, quality, performance, cost, and operational control—at tool, individual-agent, and multi-agent levels. This durable guide converts the public framework into a vendor-neutral checklist for ordinary teams, with minimum evidence, ownership, and stop conditions designed to catch soft failures where latency and uptime remain normal while answer quality quietly declines over time.
A Banking Agent Writes Then Reverses: AWS Describes a Demo, Not Production Trading
An October 5 AWS post describes Texas Capital Bank’s Trust-Earned Autonomy pattern, in which reviewer agreement can inform an agent’s permissions and a prior write can be reversed if trust declines. AWS explicitly says the agent pattern is still a demonstration running on demo-scale Apache Fineract with synthetic data, not a production workload or real production transaction flow. The bank’s separate document-extraction capability is described as operating in production. This article focuses on revocable authority, auditability, and system boundaries, and avoids presenting the demonstration as an already deployed autonomous banking agent. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.