2/13/2025, 12:00:00 AM ~ 2/14/2025, 12:00:00 AM (UTC)

Recent Announcements

AWS Deadline Cloud now supports Adobe After Effects in Service-Managed Fleets

AWS Deadline Cloud now includes support for Adobe After Effects in its Service-Managed Fleets. AWS Deadline Cloud is a fully managed service that simplifies render management for teams creating computer-generated graphics and visual effects, created in industry-standard graphics tools such as Adobe After Effects, for films, television and broadcasting, web content, and design.\n With this new feature, you can submit After Effects projects to Deadline Cloud without having to manage your own render farm infrastructure. The integration offers built-in support for custom fonts and an adjustable number of image sequence frames rendered per task, allowing you to submit jobs that are tailored to your workflow directly within After Effects. AWS Deadline Cloud automatically handles the provisioning and elastic scaling of compute resources required for rendering your After Effects projects. Service-Managed Fleets can be configured in minutes so you can begin rendering immediately. Deadline Cloud After Effects support is available in all AWS Regions where Deadline Cloud is offered. For more information, please visit the Deadline Cloud product page and our AWS Deadline Cloud documentation.

AWS Network Load Balancer now supports removing availability zones

Today, we are launching the ability to remove Availability Zones (AZ) of an existing Network Load Balancer (NLB). Prior to this launch, customers could add AZs to an existing NLB, but could not remove AZs. With this capability, customers can now change their application stack locations and move them between availability zones quickly.\n Changing business needs such as mergers & acquisitions, divestitures, data residency compliance requirements, and capacity considerations in a given region are some of the use cases that necessitate removing AZs of existing NLBs. Using this capability, customers can remove one or more availability zones from their NLB by simply updating the list of enabled subnets using ELB API, CLI or Console. Similar to any delete operation, removing a zone can be a potentially disruptive operation. When you remove a zone, the NLB zonal Elastic Network Interface (ENI) is deleted. All active connections to backend targets in that zone (including clients connecting through other zones) are terminated, the zonal IPs (and EIPs) are released and zonal DNS names deleted, and any backend target in the removed zone becomes “unused”. Refer to product documentation and AWS blog post for prescriptive guidance on how to use this capability in a safe manner. This capability is available in all AWS commercial and the AWS GovCloud (US) Regions.

Amazon RDS for PostgreSQL supports minor versions 17.3, 16.7, 15.11, 14.16, 13.19

Amazon Relational Database Service (RDS) for PostgreSQL now supports the latest minor versions 17.3, 16.7, 15.11, 14.16, and 13.19. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of PostgreSQL, and to benefit from the bug fixes added by the PostgreSQL community. This release also includes updates for PostgreSQL extensions such as pg_active 2.1.4, pg_cron 1.6.5, pg_partman 5.2.4, and others.\n You can use automatic minor version upgrades to automatically upgrade your databases to more recent minor versions during scheduled maintenance windows. You can also use Amazon RDS Blue/Green deployments for RDS for PostgreSQL using physical replication for your minor version upgrades. Learn more about upgrading your database instances, including automatic minor version upgrades and Blue/Green Deployments in the Amazon RDS User Guide. Amazon RDS for PostgreSQL makes it simple to set up, operate, and scale PostgreSQL deployments in the cloud. See Amazon RDS for PostgreSQL Pricing for pricing details and regional availability. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.

Amazon Q generative SQL is now available in additional regions

Amazon Q generative SQL is now available in Amazon Redshift Query Editor for US East (Ohio) and Asia Pacific (Seoul) regions. This feature enhances SQL query authoring in the web-based Query Editor for Amazon Redshift, enabling you to write SQL queries using natural language and receive intelligent SQL code recommendations. Amazon Q generative SQL makes Amazon Redshift database querying more accessible and efficient for users, regardless of their SQL expertise.\n Using generative AI, Amazon Q generative SQL analyzes user intent, SQL query patterns, and schema metadata to identify common query patterns within Amazon Redshift. The conversational interface allows users to submit SQL queries in natural language while maintaining their existing data permissions. For example, when asking “Find total revenue by region,” the system automatically suggests appropriate SQL code by joining relevant Amazon Redshift tables, reducing development time and potential errors. Users can accept suggested queries directly or iterate with follow-up questions to refine their results. To learn more about pricing, visit the Amazon Q Developer pricing page. See the documentation to get started.

Amazon RDS for MySQL announces Extended Support minor 5.7.44-RDS.20250103

Amazon Relational Database Service (RDS) for MySQL announces Amazon RDS Extended Support minor version 5.7.44-RDS.20250103. We recommend that you upgrade to this version to fix known security vulnerabilities and bugs in prior versions of MySQL. Learn more about the bug fixes and patches in this version in the Amazon RDS User Guide.\n Amazon RDS Extended Support provides you more time, up to three years, to upgrade to a new major version to help you meet your business requirements. During Extended Support, Amazon RDS will provide critical security and bug fixes for your RDS for MySQL databases after the community ends support for a major version. You can run your MySQL databases on Amazon RDS with Extended Support for up to three years beyond a major version’s end of standard support date. Learn more about Extended Support in the Amazon RDS User Guide and the Pricing FAQs. Amazon RDS for MySQL makes it simple to set up, operate, and scale MySQL deployments in the cloud. See Amazon RDS for MySQL Pricing for pricing details and regional availability. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.

Amazon OpenSearch Serverless expands support for time-series workloads up to 100TB

We are excited to announce that Amazon OpenSearch Serverless now supports workloads up to 100TB of data for time-series collections. OpenSearch Serverless is a serverless deployment option for Amazon OpenSearch Service that makes it simple for you to run search and analytics workloads without having to think about infrastructure management. With the support for larger datasets, OpenSearch Serverless now enables more data-intensive use cases such as log analytics, security analytics, real-time application monitoring, and more.\n OpenSearch Serverless’ compute capacity used for indexing and search are measured in OpenSearch Compute Units (OCUs). To accommodate for larger datasets, OpenSearch Serverless now allows customers to independently scale indexing and search operations to use up to 1700 OCUs. You configure the maximum OCU limits on search and indexing independently to manage costs. You can also monitor real-time OCU usage with CloudWatch metrics to gain a better perspective on your workload’s resource consumption. Please refer to the AWS Regional Services List for more information about Amazon OpenSearch Service availability. To learn more about OpenSearch Serverless, see the documentation.

Introducing Amazon EC2 C6in instances in Chicago and New York City Local Zones

Amazon Elastic Compute Cloud (Amazon EC2) C6in instances are now available in the Chicago and New York City Local Zones. C6in instances are powered by 3rd Generation Intel Xeon Scalable processors with an all-core turbo frequency of up to 3.5 GHz. They are x86-based Amazon EC2 compute-optimized instances offering up to 200 Gbps of network bandwidth. The instances are built on AWS Nitro System, which is a dedicated and lightweight hypervisor that delivers the compute and memory resources of the host hardware to your instances for better overall performance and security. You can take advantage of the higher network bandwidth to scale the performance for a broad range of workloads running in AWS Local Zones.\n Local Zones are an AWS infrastructure deployment that place compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists. You can use Local Zones to run applications that require single-digit millisecond latency for use cases such as real-time gaming, hybrid migrations, media and entertainment content creation, live video streaming, engineering simulations, financial services payment processing, capital market operations, and AR/VR. To get started, you can enable Chicago Local Zone us-east-1-chi-2a and New York City Local Zone us-east-1-nyc-2a , in the Amazon EC2 Console or the ModifyAvailabilityZoneGroup API, and deploy C6in instances. To learn more, visit AWS Local Zones overview page and see Amazon EC2 Instance types.

Amazon ECS now enables you to update services from short to long ARNs

You can now update your existing Amazon Elastic Container Service (Amazon ECS) services that use a short Amazon Resource Name (ARN) to use a long ARN without needing to re-create the service. This enables you to tag your long-running Amazon ECS services, letting you better allocate cost, improve visibility, and define fine-grained resource-level permissions for these services.\n Since 2018, customers have been able to tag Amazon ECS services that use the long ARN format (which includes the cluster name in the ARN) but if they wanted to tag services that were created with the old short ARN format, they had to delete and re-create the service. Now, ECS enables you to tag services that were created with the old short ARN format without needing to re-create the service. To enable this, you need to complete 2 steps: 1/opt-in your account to the long Amazon Resource Names (ARN) format for tasks and services and 2/tag the service you want to migrate to the long ARN format using the TagResource API action. Once you complete these steps, ECS updates the ARN of the service to the long ARN format and tags the service. Updating the service to use the long ARN format allows you to define resource-based access policies in IAM and granularly monitor the cost of your services in the Cost & Usage Report and Cost Explorer. You can update your services with short ARNs to long ARNs in all AWS regions using the AWS Console, CLI, and API. To learn more, please read our documentation.

AWS Blogs

AWS Japan Blog (Japanese)

AWS News Blog

AWS Big Data Blog

AWS Database Blog

AWS for Industries

The Internet of Things on AWS – Official Blog

AWS Machine Learning Blog

AWS for M&E Blog

Networking & Content Delivery

Open Source Project

AWS CLI

Amazon EKS Anywhere