Posts

AgentCore Gateway now supports Bedrock InvokeModel APIs and model fallback - devamazonaws.blogspot.com

Amazon Bedrock AgentCore Gateway now supports the Amazon Bedrock InvokeModel and InvokeModelWithResponseStream APIs on its inference endpoint, along with model fallback routing for inference traffic. With InvokeModel support, you can point your existing Amazon Bedrock SDK integration at the gateway and reach any model provider through one governed endpoint, without rewriting client code for each provider. With model fallback, the gateway automatically routes a request to an alternative model or provider when the primary destination is throttled, out of capacity, or unreachable, so your agents stay available without each client implementing its own retry logic. For fallback routing, you define an ordered chain of alternative destinations in a gateway rule, along with the conditions that trigger a switch, such as throttling, server errors, or response timeouts. A built-in circuit breaker skips destinations that are currently failing, so requests reach a healthy destination faster and y...
Post a Comment
Read more

[MS] 🚀 React Native Windows v0.85 is here - devamazonaws.blogspot.com

We're excited to release React Native Windows 0.85.0, built on React Native 0.85.3. React Native Windows v0.85 completes the move to the New Architecture, updates the Windows build toolchain, and adds new component capabilities along with touch, text, accessibility, and rendering fixes. 🔥 What's New in RNW v0.85? New Architecture only The legacy architecture has been removed. Apps still on the old architecture must migrate to Fabric before upgrading to 0.85. New projects already target the New Architecture. 🔗 New vs. Old Architecture · React Native for Windows Updated toolchain React Native Windows 0.85 requires: Visual Studio 2026 .NET 10 Windows App SDK 1.8 ( Microsoft.WindowsAppSDK 1.8.260508005) Update your build environment before upgrading. Modal title bar and border control Modal now supports hideTitleBar and hideBorder , so Windows apps can present dialogs without the default native title bar or border when that fits the design. View outlin...
Post a Comment
Read more

AWS Network Firewall now supports Route 53 Resolved IP Validation - devamazonaws.blogspot.com

AWS Network Firewall now supports IP validation, extending domain-based filtering beyond HTTP/HTTPS to protocols such as SFTP and SSH. This new capability validates that a connection's destination IP address was resolved through your VPC's Amazon Route 53 VPC Resolver, closing security gaps where clients could bypass domain rules. This feature enables Network Firewall customers to implement domain filtering rules for any protocol, not just HTTP/HTTPS, providing more flexible security policies than IP-based rules alone. It simplifies protection against Server Name Identifier (SNI) spoofing by validating the IPs resolved by the Route 53 VPC Resolver against the SNI, ensuring traffic only reaches legitimately resolved destinations. Organizations can now enforce consistent domain-based security policies across all outbound traffic types, from web applications to file transfer protocols, without complex workarounds. Additionally, Route 53 Resolver DNS Firewall can be used with you...
Post a Comment
Read more

Amazon CloudWatch Alarms now supports tags in alarm actions payload - devamazonaws.blogspot.com

Today, Amazon CloudWatch announces support for including alarm tags in action payloads and Amazon EventBridge events, enabling customers to route and filter alarm notifications by tag without additional lookups. When enabled on an alarm, CloudWatch adds the alarm tags to the messages it sends to Amazon SNS, AWS Lambda, and Amazon EventBridge each time the alarm changes state. This option is designed for customers who route many alarms through a shared notification pipeline and need to identify the owning team, environment, or service directly from the message. With tags in actions payloads, customers can avoid the extra work of correlating tag metadata with alarm events after the fact. For example, a team that routes hundreds of alarms through a single SNS topic to a Lambda function previously had to call ListTagsForResource for each event to find the owning team before paging. With this feature, the tags arrive in the notification, so the function can route directly from the message...
Post a Comment
Read more

Amazon DynamoDB global tables now support disassociating replicas - devamazonaws.blogspot.com

Amazon DynamoDB global tables now support disassociating a replica without deleting its table or data. Global tables provide fully managed, multi-Region, multi-active replication. You can now stop replication to and from a replica and continue using the same table as a single-Region table. An account can leave a shared multi-account global table and continue using its table independently. You can also stop replication to a Region while keeping its table for local workloads, validation, or audit, without creating a replacement table or copying data. DynamoDB supports disassociating replicas in all AWS Regions for same-account and multi-account global tables that use multi-Region eventual consistency (MREC). To get started, use the AWS Management Console, AWS CLI, DynamoDB API, or AWS CloudFormation. For more information, see Disassociating replicas in the Amazon DynamoDB Developer Guide. Post Updated on October 21, 2026
Post a Comment
Read more

Amazon ElastiCache Serverless for Valkey now supports online migration with zero downtime - devamazonaws.blogspot.com

Amazon ElastiCache Serverless for Valkey now supports online migration from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. Zero downtime means zero Errors returned to the client during migration, measured the same way the ElastiCache SLA measures availability. Your application continues reading and writing through cutover, and you do not need third-party replication tools. Online migration runs in three steps. You prepare the migration, start the data sync, and complete the cutover. ElastiCache gives you a migration endpoint your application can point to when you prepare the migration, and data replicates continuously from your source once you start the sync. You choose when writes move to the serverless cache, with a manual cutover or an automatic one once your data is in sync. ElastiCache records each step as an event on the cache’s Events tab, with the reason for any failed step. Online migration connects to your source using encryption in transit (TLS) an...
Post a Comment
Read more

[MS] Can a local git remote replace GitHub in your agent eval? - devamazonaws.blogspot.com

When an agent eval involves pushing, pulling or keeping a git branch in sync, the fixture needs a remote repository. The easiest one to set up is a bare repository next to the fixture. It takes one git init --bare , works offline and resets with the rest of the workspace. A real GitHub repository in comparison, needs a token, an API call to create it and cleanup after every run. Run scenarios in parallel, and it gets even worse. Every run needs its own repository with a unique name that still looks like something a developer would create, and every failed teardown leaves one behind. Multiply that by hundreds of runs, and you're also putting load on GitHub's services for traffic that serves nobody. So we wanted to know whether a local remote is a good enough stand-in for the real thing. Mostly, it is. The agent rebased just as well and pushed just as safely against both. But when the agent had to decide on its own whether to push, the local remote changed the answer. It made t...
Post a Comment
Read more