AWS announces Deployment Agent SOPs in AWS MCP Server (preview)

AWS announces the launch of deployment Standard Operating Procedures (SOPs) available in the AWS MCP Server. SOPs are structured, natural language instructions that guide AI agents through complex, multi-step tasks to ensure consistent, reliable, and efficient behavior. With these automated procedures, customers can deploy web applications to their AWS account using natural language prompts from any MCP-compatible IDE or CLI, including Kiro, Kiro CLI, Cursor, and Claude Code. Deployment works by generating AWS CDK infrastructure, deploying CloudFormation stacks, and creating CI/CD pipelines with recommended AWS security best practices. Previously, developers struggled to take their vibe-coded applications to production with DevOps best practices in place. Now, developers can move quickly from prototype to production in as little as one prompt. When you ask your AI assistant configured with AWS MCP Server to deploy your web application, your AI agent will follow the multi-step plan defined in Agent SOPs to analyze the project structure, generate CDK infrastructure, and deploy a preview environment hosted on Amazon S3 and Amazon CloudFront. Once you are ready, it can configure AWS CodePipeline for automated production deployments from source repositories, setting up CI/CD automatically for your application. The Agent SOPs support web applications built with popular frameworks including React, Vue.js, Angular, and Next.js. Deployment documentation is automatically created in the repository, enabling agents to handle future deployments, query logs for troubleshooting and resume work across sessions. The Agent SOPs are available in preview as part of the AWS MCP Server at no additional cost in the US East (N. Virginia) Region. You pay only for AWS resources you create and applicable data transfer costs. To get started, see the AWS MCP Server documentation.
Quelle: aws.amazon.com

Amazon Cognito introduces inbound federation Lambda triggers

Amazon Cognito introduces inbound federation Lambda triggers that enable you to transform and customize federated user attributes during the authentication process. You can now modify responses from external SAML and OIDC providers before they are stored in your user pool, providing complete programmatic control over the federation flow without requiring changes to your identity provider configuration..
Inbound federation Lambda trigger addresses current limitations in federated authentication workflows, particularly issues caused by attribute size limits and the need for selective attribute storage from external identity providers. For example, large group attributes from external SAML or OIDC identity providers that exceed Cognito’s 2,048 character limit per attribute can block the authentication flow. This capability allows you to add, override, or suppress attribute values, such as modifying large group attributes, before creating new federated users or updating existing federated user profiles in Cognito.
The new inbound federation Lambda trigger is available through hosted UI (classic) and managed login in all AWS Regions where Amazon Cognito is available. To get started, configure the trigger using the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), Cloud Development Kit (CDK), or AWS CloudFormation by adding the new parameter to your User Pool LambdaConfig. To learn more, see the Amazon Cognito Developer Guide for implementation examples and best practices.
Quelle: aws.amazon.com

Announcing increased 1 MB payload size support in Amazon EventBridge

Amazon EventBridge increases event payload size from 256 KB to 1 MB, enabling developers to ingest richer, complex payloads for their event-driven workloads without the need to split, compress, or externalize data. Amazon EventBridge is a serverless event router that enables you to create scalable event-driven applications by routing events between your applications, third-party SaaS applications, and AWS services. These applications often need to process rich contextual data, including large-language model prompts, telemetry signals, and complex JSON structures for machine learning outputs. The new 1MB payload support in EventBridge Event Buses enables developers to streamline their architectures by including comprehensive data in a single event, reducing the need for complex data chunking or external storage solutions. This feature is available in all commercial AWS Regions where Amazon EventBridge is offered, except Asia Pacific (New Zealand), Asia Pacific (Thailand), Asia Pacific (Malaysia), Asia Pacific (Taipei), and Mexico (Central). For a full list, see the AWS Regional Services List. To learn more, visit the EventBridge documentation.
Quelle: aws.amazon.com

Amazon DynamoDB global tables with multi-Region strong consistency now supports application resiliency testing with AWS Fault Injection Service

Amazon DynamoDB global tables with multi-Region strong consistency (MRSC) now supports application resiliency testing with AWS Fault Injection Service (FIS), a fully managed service for running controlled fault injection experiments to improve application performance, observability, and resilience. With this launch, you can create real-world failure scenarios to MRSC global tables, such as during regional failures, enabling you to observe how your applications respond to these disruptions and validate your resilience mechanisms. MRSC global tables replicate your DynamoDB tables automatically across your choice of AWS Regions to achieve fast, strongly consistent read and write performance, providing you 99.999% availability, increased application resiliency, and improved business continuity. FIS is a fully managed service for running controlled fault injection experiments to improve an application’s performance, observability, and resilience. You can use the new FIS action to observe how your application responds to a pause in regional replication and tune monitoring and recovery processes to improve resiliency and application availability. MRSC global tables support for FIS is available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo), Asia Pacific (Osaka), Asia Pacific (Seoul), Europe (Ireland), Europe (London), Europe (Frankfurt), and Europe (Paris). To get started, visit the DynamoDB FIS actions documentation.
Quelle: aws.amazon.com

Amazon MSK Replicator is now available in Asia Pacific (New Zealand)

You can now use Amazon MSK Replicator to replicate streaming data across Amazon Managed Streaming for Apache Kafka (Amazon MSK) clusters in Asia Pacific (New Zealand) Region. MSK Replicator is a feature of Amazon MSK that enables you to reliably replicate data across Amazon MSK clusters in different or the same AWS Region(s) in a few clicks. With MSK Replicator, you can easily build regionally resilient streaming applications for increased availability and business continuity. MSK Replicator provides automatic asynchronous replication across MSK clusters, eliminating the need to write custom code, manage infrastructure, or setup cross-region networking. MSK Replicator automatically scales the underlying resources so that you can replicate data on-demand without having to monitor or scale capacity. MSK Replicator also replicates the necessary Kafka metadata including topic configurations, Access Control Lists (ACLs), and consumer group offsets. If an unexpected event occurs in a region, you can failover to the other AWS Region and seamlessly resume processing. You can get started with MSK Replicator from the Amazon MSK console or the Amazon CLI. With this launch, MSK Replicator is now available in thirty six AWS Regions. To learn more, visit the MSK Replicator documentation, product page, and pricing page.
Quelle: aws.amazon.com

Amazon EC2 R7gd instances are now available in Europe (Paris) Region

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) R7gd instances with up to 3.8 TB of local NVMe-based SSD block-level storage are available in Europe (Paris) Region. R7gd are powered by AWS Graviton3 processors with DDR5 memory are built on the AWS Nitro System. They are ideal for memory-intensive workloads such as open-source databases, in-memory caches, and real-time big data analytics and are a great fit for applications that need access to high-speed, low latency local storage, including those that need temporary storage of data for scratch space, temporary files, and caches.  To learn more, see Amazon R7gd Instances. To get started, see the AWS Management Console.
Quelle: aws.amazon.com

Amazon EKS and Amazon EKS Distro now supports Kubernetes version 1.35

Kubernetes version 1.35 introduced several new features and bug fixes, and AWS is excited to announce that you can now use Amazon Elastic Kubernetes Service (EKS) and Amazon EKS Distro to run Kubernetes version 1.35. Starting today, you can create new EKS clusters using version 1.35 and upgrade existing clusters to version 1.35 using the EKS console, the eksctl command line interface, or through an infrastructure-as-code tool. Kubernetes version 1.35 introduces several key improvements, including In-Place Pod Resource Updates allowing CPU and memory adjustments without restarting Pods, and PreferSameNode Traffic Distribution prioritizing local endpoints before routing to remote nodes for reduced latency. The release brings Node Topology Labels via Downward API enabling Pods to access region and zone information without API server queries, alongside Image Volumes delivering data artifacts like AI models using OCI container images. To learn more about the changes in Kubernetes version 1.35, see our documentation and the Kubernetes project release notes. EKS now supports Kubernetes version 1.35 in all the AWS Regions where EKS is available, including the AWS GovCloud (US) Regions. You can learn more about the Kubernetes versions available on EKS and instructions to update your cluster to version 1.35 by visiting EKS documentation. You can use EKS cluster insights to check if there are any issues that can impact your Kubernetes cluster upgrades. EKS Distro builds of Kubernetes version 1.35 are available through ECR Public Gallery and GitHub. Learn more about the EKS version lifecycle policies in the documentation.
Quelle: aws.amazon.com

Amazon RDS for PostgreSQL, MySQL and MariaDB now support r6id and r6gd database instances in additional AWS Regions

AWS memory optimized R6id database instances are now generally available for Amazon RDS for PostgreSQL, MySQL, and MariaDB in the Tel Aviv region. R6gd instances are now supported for Amazon RDS for PostgreSQL, MySQL, and MariaDB in Asia Pacific (Osaka), and EU (Spain, Zurich) regions.  AWS Graviton2-based instances provide up to 40% performance improvement over R5-based instances of equivalent sizes on Amazon Aurora and Amazon RDS databases, depending on database engine, version, and workload. R6gd instances also deliver local NVMe-based block level storage for low latency local storage. Memory-optimized R6id instances offer 58% higher TB storage per vCPU and 15% better price performance when compared with R5d instances. You can easily launch R6gd or R6id database instances through the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI). For detailed information about specific engine versions that support these database instance types, please refer to the Aurora and RDS documentation. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page.
Quelle: aws.amazon.com

AWS Network Firewall now supports GenAI traffic visibility and enforcement with Web category-based filtering

AWS Network Firewall now provides visibility into generative AI (GenAI) application traffic and supports traffic filtering based on web categories. This new capability simplifies governance by enabling you to identify and control access to GenAI services, social media platforms, streaming sites, and other web categories directly within your firewall rules using pre-defined URL categories. This approach of inspecting traffic based on URL categories helps security and compliance teams enforce consistent policies across their AWS environments while providing visibility into usage of emerging technologies like GenAI. You can now easily block access to inappropriate or high-risk domains, restrict GenAI tool usage to approved services, and meet regulatory requirements—all while reducing operational overhead. When combined with AWS Network Firewall’s TLS inspection feature, you can inspect the full URL path using category-based rules for even more granular control. This feature is available in all AWS commercial regions where AWS Network Firewall is supported. To learn more about URL category filtering in AWS Network Firewall, visit AWS Network Firewall product page and service documentation. You can get started by updating your stateful rule groups in the AWS Management Console, AWS CLI, or AWS SDKs. 
Quelle: aws.amazon.com

AWS Deadline Cloud now supports editing job name and description

AWS Deadline Cloud now supports editing job names and descriptions after submission. This new feature makes it easier to organize and identify jobs after submission by updating names or adding useful tracking details in the description field. Job names and descriptions are critical metadata for organizing and understanding between users and projects, often tracking things like shot and sequence number across systems. Previously they could only be set at job creation during submission, being able to edit them after submission allows you to fix issues in naming as well as add key tracking information to the job description for other users. You can edit job names and descriptions using the AWS SDK, Deadline client, and Deadline Monitor. To learn more see the AWS Deadline Cloud documentation.
Quelle: aws.amazon.com