2/13/2026, 12:00:00 AM ~ 2/16/2026, 12:00:00 AM (UTC)
Recent Announcements
AWS Batch now provides Job Queue and Share Utilization Visibility
AWS Batch now provides Queue and Share Utilization Visibility, giving you insights into how your workloads are distributed across compute resources. This feature introduces queue utilization data in job queue snapshots, revealing compute capacity used by your first-in-first-out (FIFO) and fair share job queues, along with capacity consumption by individual fair share allocations. Additionally, the ListServiceJobs API now includes a scheduledAt timestamp for AWS Batch service jobs, allowing you to track when jobs are scheduled for execution.\n Queue and Share Utilization Visibility helps you understand which fair-share allocations consume the most capacity and pinpoint the specific jobs driving resource consumption. You can monitor overall queue utilization and drill down into active shares to optimize resource distribution, or filter jobs by share identifier to analyze consumption patterns and scheduling behavior across your workloads. You can access this feature using the GetJobQueueSnapshot, ListJobs, and ListServiceJobs APIs, or through the AWS Batch Management Console by navigating to your job queue details page and selecting the new Share Utilization tab. This feature is available today in all AWS Regions where AWS Batch is available. To learn more, visit the Job Queue Snapshot, List Jobs, and List Service Jobs pages of the AWS Batch API Reference Guide.
Amazon Connect now supports in-app notifications in the workspace header, visible from any page, so your team can stay informed without interrupting their workflow— whether configuring, analyzing data, or servicing customers. A notification icon appears in the header of every workspace page, with a badge indicating unread messages. Click the icon to view messages, access relevant resources through embedded links, and manage read/unread status—all without navigating away from your current task. For example, if all supervisors need to complete a certain training by end of week, a notification can be published to non-compliant users to remind them.\n The new notification APIs enable you to programmatically send targeted messages to specific audiences within your organization, ensuring teams stay aware of urgent updates, policy changes, and action items requiring immediate attention. Amazon Connect will also leverage this capability to deliver system updates and important announcements. In-app notifications are available in all AWS regions where Amazon Connect is available and offer public API and AWS CloudFormation support. To learn more about in-app notifications, see the Amazon Connect Administrator Guide. To learn more about Amazon Connect, please visit the Amazon Connect website.
Amazon Connect now provides real time AI-powered overviews and recommended next actions for Tasks
Amazon Connect now provides AI-powered Task overviews with suggested next actions so agents can understand work items faster and resolve them more quickly. For example, when an agent receives a Task to process a refund request submitted through an online form, Amazon Connect summarizes earlier activities such as verifying order details, checking return eligibility, and confirming the payment method, and then presents recommended next steps to complete the refund.\n To enable this feature, add the Connect assistant flow block to your flows before a Task contact is assigned to your agent. You can guide the recommendations of your generative AI-powered Tasks assistant by adding knowledge bases. This new feature is available in all AWS regions where Amazon Connect real time agent assistance is available. To learn more and get started, refer to the help documentation, pricing page, or visit the Amazon Connect website.
Amazon RDS now supports backup configuration when restoring snapshots
Amazon Relational Database Service (RDS) and Amazon Aurora now offer greater flexibility for restore operations to view and modify backup retention period and preferred backup window prior to and upon restoring database snapshots. The backup retention period lets you specify how many days backups are retained, while the preferred backup window allows you to set your desired backup schedule.\n Previously, restored database instances and clusters inherited backup parameter values from snapshot metadata and could only be modified after restore was complete. This launch introduces two enhancements - you can now view the backup retention period and preferred backup window settings as part of automated backups and snapshots, providing visibility into backup configurations before initiating restore operation. Additionally, you can now specify or modify the backup retention period and preferred backup window when restoring database instances and clusters, eliminating the need to modify the instance or cluster after restoration. These enhancements are available for all Amazon RDS database engines (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, and DB2) and Amazon Aurora (MySQL-Compatible and PostgreSQL-Compatible editions) in all AWS commercial regions and AWS GovCloud (US) regions where RDS and Aurora are supported and respective database engines are available. You can use these features through the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs at no additional cost. For more information, see Amazon RDS and Amazon Aurora User Guide.
Amazon Aurora DSQL adds support for identity columns and sequence objects
Amazon Aurora DSQL now supports identity columns and sequence objects enabling developers to generate auto-incrementing, integer-based IDs directly in the database using familiar SQL patterns.\n This launch simplifies migrations of existing PostgreSQL applications and supports development of new workloads that rely on database-managed integer identifiers. Developers can create compact, human-readable IDs, such as order numbers, account IDs, or operational references without custom ID generation logic in application code or middleware.