TLDRocket
Sign in

AWS

163 summarised stories about AWS, each linking back to the original source. Browse all topics →

+ Follow this topic

Friday, 14 August 2026

Building agentic workflows with SageMaker AI and Bedrock AgentCore

Amazon Web Services 2 months ago 25 ● 2 sources

Bedrock AgentCore was used to run a multi-agent workflow that routes requests between Amazon Bedrock models and an OpenAI-compatible Qwen 3.5 9B endpoint hosted on Amazon SageMaker AI. The Qwen 3.5 9B model was deployed on an ml.g6e.2xlarge instance running vLLM 0.22.1-gpu-py312-cu130. Token-level observability changed by adding a custom OpenTelemetry gen_ai.chat span and enabling vLLM streaming usage reporting (include_usage) so SageMaker token counts become visible in traces.

Your container images are unsigned. In the AI era, that’s a ticking time bomb.

The New Stack 2 months ago 45

Amazon ECR Managed Signing was introduced to address how unsigned container images leave organizations unable to cryptographically prove image origin or prevent tampering in AI-era delivery pipelines. It uses AWS Signer with a default signature validity of 135 months and signs a Notary payload that binds the image manifest digest to an identity. With registry-backed signing plus Kubernetes enforcement (e.g., Kyverno/Gatekeeper/Ratify), unsigned or untrusted images are blocked from running and compromised signer identities can be revoked to stop trust fleetwide.

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.