Amazon SNS now supports push notifications in four additional AWS Regions

Amazon Simple Notification Service (Amazon SNS) now supports sending push notifications in the Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), and AWS GovCloud (US-East) Regions.
Amazon SNS is a fully managed pub/sub service that provides message delivery to multiple endpoints, including AWS Lambda, Amazon SQS, Amazon Data Firehose, HTTP, SMS (via AWS End User Messaging), push notifications, and email. With this launch, customers in these four additional Regions can use Amazon SNS to send push notifications to the following supported push notification services: Amazon Device Messaging (ADM), Apple Push Notification Service (APNs), Baidu Cloud Push (Baidu), Firebase Cloud Messaging (FCM), and Windows Push Notification Services (WNS).
For the full list of Regions from which you can send push notifications, see Supported Regions and Countries in the Amazon SNS Developer Guide. For more information, see the Amazon SNS push notifications documentation.
Quelle: aws.amazon.com

Amazon Connect Customer supports merging and linking related cases in the agent workspace

Amazon Connect Customer now lets agents merge and link related cases in the agent workspace, so they can resolve customer issues faster and respond consistently. When a customer contacts a business about the same issue more than once, or on different channels, the history can end up split across several cases. Agents can merge those cases into one case with a single, consolidated history. For example, an agent can merge the chat and email cases a customer opened about a delayed shipment.
Agents can also link related cases, such as cases from different customers affected by the same issue, so they can coordinate one consistent response for every affected customer.
Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases webpage and documentation.
Quelle: aws.amazon.com

Amazon Aurora and RDS now support Graviton5-based R9g database instances

AWS Graviton5-based R9g database instances are now generally available for Amazon Aurora with PostgreSQL compatibility and MySQL compatibility, and for Amazon RDS for PostgreSQL, MySQL, and MariaDB.   Graviton5-based R9g instances provide up to a 30% performance improvement and up to a 22% price-performance improvement for on-demand pricing over Graviton4-based instances of equivalent sizes on Amazon Aurora, depending on database engine, version, and workload. Built on the AWS Nitro System, R9g instances are available in nine sizes, from large to 48xlarge. They deliver up to 192 vCPUs, an 8:1 ratio of memory to vCPU, up to 100 Gbps of networking bandwidth, and up to 72 Gbps of bandwidth to Amazon Elastic Block Store (Amazon EBS). 
You can get started using the R9g database instances through the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI). The instances are available in US East (N. Virginia, Ohio), US West (Oregon), and Europe (Frankfurt) regions. For the specific engine versions that support these instance classes, see the Aurora and RDS documentation. For pricing, see Amazon Aurora pricing and Amazon RDS pricing.
Quelle: aws.amazon.com

Amazon Cognito now supports OAuth 2.0 token exchange

Amazon Cognito now supports OAuth 2.0 token exchange (RFC 8693). Amazon Cognito helps you add sign-up, sign-in, and access control to your web applications, mobile applications, and AI agents. With token exchange, a service or AI agent acting on a user’s behalf can exchange the user’s token for a new token scoped to a specific downstream service. Previously, a service that called another service on a user’s behalf had to forward the user’s original token or build and maintain its own token minting logic.
With token exchange, you can issue a new token that has a narrower scope than the original token, is bound to a single audience, and comes without a refresh token. When you include an actor token, Cognito adds an act claim that identifies the intermediary, so downstream services can tell a request that an agent made on a user’s behalf from one the user made directly. For example, a Model Context Protocol (MCP) server can exchange a user’s token for a narrowly scoped token to call a backend API, with the act claim recording the MCP server as the actor.
You can exchange tokens through the token endpoint or with the new GetDerivedToken API. Token exchange is available on the Essentials and Plus feature plans in all AWS Regions where Amazon Cognito is available. To learn more, see exchanging tokens for downstream services in the Amazon Cognito Developer Guide.
Quelle: aws.amazon.com