Posts

Amazon SES now supports tenant-level suppression lists - devamazonaws.blogspot.com

Amazon Simple Email Service (Amazon SES) now supports tenant-level suppression lists, allowing email senders to isolate bounces and complaints per tenant. Previously, all tenants in an account shared a single suppression list, meaning one tenant's email issues caused emails for other tenants to be suppressed. With this feature, each tenant maintains a separate suppression list, ensuring that bounces and complaints affect only the tenant that generated them. This capability benefits any sender managing distinct email streams from a single SES account. Key use cases include SaaS providers sending on behalf of multiple customers, enterprises separating transactional and marketing mail across business units, agencies managing campaigns for different brands, or any application where a complaint from one sending program shouldn't suppress delivery for another.  You can configure suppression behavior using two settings: suppression scope (TENANT or ACCOUNT) and suppressed reasons ...

Amazon Connect’s AI assistant is now available in the UI builder - devamazonaws.blogspot.com

Amazon Connect Customer Assistant is now integrated within the UI builder, enabling contact center managers to create and modify views using natural language. Managers describe what they need, such as "Create a feedback form with rating and comment fields," and the assistant generates the corresponding UI components for review before publishing. This reduces the time and expertise needed to build Views for Step-by-Step Guides and Workspace pages by up to 70%. Managers can use conversational prompts to create views, configure layouts with conditional UIs, set component properties, and apply styling without manual work. The assistant recommends components, explains options, and troubleshoots issues to accelerate builds.  Post Updated on May 28, 2026 at 02:51PM

[MS] Scaling AI for silicon - devamazonaws.blogspot.com

Image
Modern AI systems have transformed software engineering, but their impact in silicon development has been limited. The primary constraint is that silicon engineering depends on assembling and reasoning over context that is distributed across many systems. Specifications, logs, regressions, waveforms, and prior debug history all contribute to understanding a problem, yet they are rarely accessible within a single workflow. Early applications of AI in this space focused on code generation and isolated tasks. These approaches proved useful for scripting and tooling, but had little effect on core design and verification work. The underlying issue is that most engineering effort is spent reconstructing context before meaningful reasoning can begin. When that context remains fragmented, AI systems operate on partial information and cannot participate in the full problem-solving process. This reflects a fundamental difference in how progress is made. Software workflows can rely on rapid i...

[MS] Microsoft Agent Framework at BUILD 2026 - devamazonaws.blogspot.com

Image
BUILD 2026 begins on Tuesday, June 2, and there will be tons of exciting announcements from the Microsoft Agent Framework team, Microsoft Foundry, and all things Microsoft AI. If you're traveling to San Francisco for BUILD, be sure to stop by the Microsoft Foundry booths to chat with folks from the Agent Framework team - there'll be stickers! If you can't make it to SF, you can still register online and check out the great sessions: Register for Microsoft Build Looking for sessions with Microsoft Agent Framework to watch online? Start with these breakout sessions. Times are shown in Pacific time; check the session page for the latest schedule. Session Date/time Speaker(s) Description Claw and agent harness in Microsoft Foundry (BRK243) Wed, June 3, 11:30 AM–12:15 PM PT Glenn Condron, Amanda Foster, Shawn Henry Go deep on multi-agent systems, Claw agent patterns, hosted agents architecture, triggers, state management, and file access. From prototype...

[MS] What's new in Microsoft Foundry | May 2026 - devamazonaws.blogspot.com

Image
TL;DR Trace-based evaluation for external and hosted agents: Grade real production traces from Foundry, GCP, AWS, or any framework — no hand-curated datasets required. Grok 4.3: xAI's latest model lands in Foundry for advanced agentic and domain-specific workloads. DeepSeek V4: DeepSeek's newest model family expands open-model choice in the catalog. Fireworks AI — May update: DeepSeek V4 Pro and Kimi 2.6 arrive via Fireworks for high-performance open-model inference. GPT-5 Reinforcement Fine-Tuning (Gated GA): RFT graduates to gated GA with enterprise-ready compliance and SLA coverage. MagenticBrain, Fara1.5-9B, MagenticLite: Microsoft Research ships three on-device agent projects for agentic reasoning, screen-based UI automation, and local browser/file-system workflows — with examples in Foundry Labs. SocialReasoning-Bench + STATE-Bench: Two open-source benchmarks for evaluating agent negotiation, coordination, and memory quality. Manage...

[MS] Sharing the result of a single Windows Runtime IAsyncOperation among multiple coroutines, part 3 - devamazonaws.blogspot.com

Last time, we wrote a coroutine function that cached the result of another coroutine , but it only cached successful calls. It didn't cache failures, so if the inner coroutine fails, the outer one will simply try again the next time it is called. But what if we want to call the inner coroutine only once and cache the failure, too? We now have three states: Never tried, tried with success (and cache the success result), and tried with failure (and cache the failure). We can represent that as a variant with three types, using std:: monostate to represent the "never tried" state.¹ struct Widget : WidgetT<Widget> { std::variant<std::monostate, winrt::Thing, std::exception_ptr> m_thing; wil::unique_event m_busy{ wil::EventOptions::Signaled }; // auto-reset, initially signaled IAsyncOperation<winrt::Thing> GetThingAsync() { auto lifetime = get_strong(); co_await winrt::resume_on_signal(m_busy.get()); auto not_busy ...

Amazon Redshift Serverless now offers 4-RPU Minimum Capacity in 7 additional AWS Regions - devamazonaws.blogspot.com

Amazon Redshift now allows you to get started with Amazon Redshift Serverless with a lower data warehouse base capacity configuration of 4 Redshift Processing Units (RPUs) in the Asia Pacific (Hong Kong), Asia Pacific (Seoul), Canada (Central), Europe (London), South America (Sao Paulo), AWS GovCloud (US-East), and AWS GovCloud (US-West) regions. Amazon Redshift Serverless measures data warehouse capacity in RPUs. 1 RPU provides you 16 GB of memory. You pay only for the duration of workloads you run in RPU-hours on a per-second basis. Previously, the minimum base capacity required to run Amazon Redshift Serverless was 8 RPUs. You can start using Amazon Redshift Serverless for as low as $1.50 per hour and pay only for the compute capacity your data warehouse consumes when it is active. For predictable workloads, Amazon Redshift Serverless capacity reservations with 1-year and 3-year terms provide additional price-performance benefits. Amazon Redshift Serverless enables users to run...