Create

Sign in to ReadmeX

Sign in to join communities, post, vote and chat.

New here?

Amazon Web Services

AI overview

Sign in and the AI will write an overview from our coverage.

Headlines · 8

  1. AWS outlines Agentic Value Model for justifying agentic automation

    An AWS Machine Learning Blog post proposes an “Agentic Value Model” for building the business case for agentic automation, arguing that the RPA-era ROI formula (hours saved × loaded rate − build cost) misses exception handling, decision quality, and change resilience and maintenance economics. It lays out four value pools and stresses that every benefit needs a defined realization mechanism and an accountable owner. The post cites early deployments of Amazon Quick Automate: Kitsa reports 91% cost savings, 96% faster data acquisition and 96% coverage; dLocal says it automates up to 75% of merchant-compliance reviews in controlled evaluations; and Genpact reports cutting supply-chain disruption analysis from 2–3 days to minutes.

    AWS Machine Learning Blog · 🔥 9
  2. AWS playbook: six-week program turns non-engineers into AI agent builders

    In an AWS Machine Learning Blog post, Amazon Web Services describes a six-week program that pairs non-engineering business staff with mentors and production-grade tools—Kiro, Amazon Bedrock, Strands Agents SDK and AWS Lambda agents—for about four hours a week, ending in a working prototype. A team of four customer-facing employees with no engineering background built WealthWise, a multi-agent financial advisory prototype with five agents (portfolio analysis, risk assessment, financial planning and more), a dual-server Node.js and Python Flask architecture, four DynamoDB tables and, the team says, sub-5-second responses for complex reasoning; it took first place in the demo judging. AWS reports that self-rated “strong or expert” understanding of agentic AI rose from 27% to 82% among participants, and readiness to identify AI opportunities from 41% to 85%.

    AWS Machine Learning Blog · 🔥 9
  3. Cornerstone cuts database diagnosis time 78% with Bedrock-based Orion AI

    Cornerstone OnDemand's Enterprise DataOps team built Orion AI, a multi-agent system on Amazon Bedrock and AWS's open-source Strands Agents framework, using a hub-and-spoke topology in which a meta-orchestrator routes work to 13 domain-specific agents, including three SQL Server diagnostics agents. According to the AWS blog post, database diagnosis time fell from about 45 minutes to 10 minutes per incident (a 78% reduction), manual lifecycle steps dropped roughly 70%, SRE-to-data-team reporting lag went from 15 minutes to real time, and redundant alerts fell by a median of 65%. A three-person team delivered the system in six months on Amazon ECS, with Amazon Bedrock AgentCore providing cross-session memory.

    AWS Machine Learning Blog · 🔥 9
  4. Building a context-aware AI assistant with OpenClaw on AWS AgentCore

    An AWS Machine Learning Blog tutorial shows how to run the open-source agentic system OpenClaw on Amazon Bedrock AgentCore runtime and give it continuity with AgentCore memory, using a gardening assistant called Sprout as the example; the whole system ships in a single CloudFormation template that deploys with one command. On each message the agent retrieves long-term memory records from a per-user namespace, ranks explicit preferences ahead of inferred facts, and injects them into the system prompt, degrading gracefully to a memory-free answer if retrieval times out within a 3-second budget or errors. Tasks are routed to different models — Claude Haiku 4.5 for text and Claude Sonnet 4.5 for image diagnosis — with Telegram as the front door. The author estimates roughly $1–2 per month for light personal use versus about $35 per month for an always-on EC2 instance.

    AWS Machine Learning Blog · 🔥 5
  5. Best practices for Amazon SageMaker HyperPod administration and governance

    An AWS Machine Learning Blog post explains how to administer Amazon SageMaker HyperPod clusters through Amazon SageMaker Unified Studio while preserving underlying governance controls. It lays out four layers of control — organization, project, cluster, and workload — and covers designing identity, capacity, and observability policies across them, plus a "connection contract" record for each approved project-to-cluster connection.

    AWS Machine Learning Blog · 🔥 5
  6. SageMaker Studio can now manage HyperPod Spaces without the CLI

    AWS says users can now create, configure, start, stop and open Amazon SageMaker Spaces on Amazon SageMaker HyperPod EKS clusters directly from the SageMaker Studio UI, instead of relying on the HyperPod CLI or kubectl. A new IDE and Notebooks tab on the cluster detail page offers a guided form and a searchable Spaces table, with browser access to JupyterLab or Code Editor and remote VS Code access over SSH-over-SSM. AWS says Karpenter over-provisioning can cut Space startup from 5–7 minutes to roughly 30–40 seconds.

    AWS Machine Learning Blog · 🔥 5
  7. AWS ships MCP server to promote Amazon Quick resources across accounts

    An AWS blog post details the Amazon Quick Resource Migrator, a sample Model Context Protocol server hosted on Amazon Bedrock AgentCore runtime that promotes Amazon Quick agents, action connectors, knowledge bases, flows and spaces from a development AWS account to production. It reads and recreates resources through the Amazon Quick (Quick Sight) API, replays source permissions in the target account, offers a read-only preview, is idempotent across re-runs, and writes versioned S3 backups with a restore tool. S3 documents behind knowledge bases are not copied, and connector credentials are created as placeholders and must be re-authenticated in the target account; full source is in an aws-samples repository.

    AWS Machine Learning Blog · 🔥 0
  8. AWS shows layered evaluation for multi-agent systems with AgentCore Evaluations

    An AWS blog post explains how to assess multi-agent systems with Amazon Bedrock AgentCore Evaluations, combining built-in evaluators (helpfulness, task success, instruction following, tool selection) with custom evaluators for domain rules such as constraint satisfaction, route feasibility and SQL correctness. The walkthrough uses a fictional retailer, AnyCompany Retail, building a supply-chain decisioning system with the Strands Agents SDK: one orchestrator agent plus optimization, distribution, routing and analytics sub-agents running on AgentCore runtime with memory and observability. A separate explainability layer of six cross-cutting evaluators checks decision rationale, evidence attribution, constraint reasoning, trade-off explanation, tool-use explainability and assumption disclosure; AgentCore Evaluations runs in on-demand mode for benchmarks and CI/CD gates, and online mode to sample production traces into CloudWatch dashboards and alarms.

    AWS Machine Learning Blog · 🔥 0

Experience and discussion from the community

Share my Amazon Web Services experienceAsk about Amazon Web Services

Nobody has shared their experience with Amazon Web Services yet.