Posts

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...

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

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...

[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...

[MS] Why do we need ud2 when int 6 is right there? - devamazonaws.blogspot.com

Some time ago, I mentioned that the ud2 instruction was created to be an architecturally undefined instruction . But why not just use an int 6 instruction? It's a two-byte instruction, just like ud2 , and interrupt vector 6 is the invalid opcode vector, so a program could just invoke it manually and get whatever behavior the operating system assigns to an attempt to execute an invalid opcode. Well, not exactly. Architecturally, the invalid opcode is a fault , which means that the address of the faulting instruction is reported to the exception handler. On the other hand, the int 6 is a trap , which means that the address of the instruction after the int 6 is reported to the handler. This distinction between faults and traps reflects how they are used. A fault represents an error that the kernel could attempt to repair and retry. For example, a page fault could be repaired by paging the memory in. An access violation could be repaired by changing the page protections. A tra...

AWS Elemental MediaConnect Router now supports high bitrate mode - devamazonaws.blogspot.com

AWS Elemental MediaConnect Router now supports high bitrate modes with two new tiers: 250 Mbps and 500 Mbps. This allows professional broadcasters that need higher bitrates to transport high-value content without compromising quality or reliability. This enhancement enables industry-standard workflows such as VSF TR-07 compliant transport stream distribution for broadcast contribution, content distribution, and remote production. High bitrate mode supports up to two redundant sources for reliability and includes data plane optimizations that reduce jitter for improved performance. To learn more, visit the AWS Elemental MediaConnect product page and the MediaConnect pricing page . Post Updated on October 19, 2026 at 09:00AM

Amazon GuardDuty adds optional threat detection rules for Runtime Monitoring - devamazonaws.blogspot.com

Amazon GuardDuty now supports optional detection rules for Runtime Monitoring. You can enable more than 50 Runtime Monitoring rules that help detect process, file, and network activity that might be routine in one environment but a sign of compromise in another, such as modifying sudoers files or disabling audit logging. The new rules provide detections for Amazon EC2 instances, Amazon EKS, and Amazon ECS on both EC2 and AWS Fargate, and span 13 finding types mapped to MITRE ATT&CK® tactics including persistence, privilege escalation, execution, defense evasion, discovery, exfiltration, and command and control. This release introduces four new finding types: CommandAndControl:Runtime/SuspiciousCommand, CredentialAccess:Runtime/SensitiveFileRead, Discovery:Runtime/SensitiveFileRead, and Exfiltration:Runtime/SuspiciousCommand. To get started, visit the GuardDuty console. You can enable rules in dry-run mode to evaluate detection efficacy before enabling live detection. Custom Dete...