ACUVA

Your Accurate Search for New Technology

Amazon Route 53 Profiles now available in three additional AWS Regions

By

Starting today, Route 53 Profiles is available in Asia Pacific (Thailand), Mexico (Central), and Asia Pacific (Malaysia) Regions.

Route 53 Profiles allows you to define a standard DNS configuration (Profile), that may include Route 53 private hosted zone (PHZ) associations, Route 53 Resolver rules, and Route 53 Resolver DNS Firewall rule groups, and apply this configuration to multiple VPCs in your account. Route 53 Profiles can also be used to enforce DNS settings for your VPCs, with configurations for DNSSEC validations, Resolver reverse DNS lookups, and the DNS Firewall failure mode. You can share Profiles with AWS accounts in your organization using AWS Resource Access Manager (RAM). Route 53 Profiles simplifies the association of Route 53 resources and VPC-level settings for DNS across VPCs and AWS accounts in a Region with a single configuration, minimizing the complexity of having to manage each resource association and setting per VPC.

Route 53 Profiles is available in the AWS Regions mentioned here . To get started with this feature, visit the Route 53 documentation . To learn more about pricing, you can visit the Route 53 pricing page .
 

Amazon ECS increases container exit reason message to 1024 characters

By

Amazon Elastic Container Service (Amazon ECS) has extended the length of the container exit reason message from 255 to 1024 characters. The enhancement helps you debug more effectively by providing more complete error messages when containers fail.

Amazon ECS customers use container exit reason messages to troubleshoot their running or stopped tasks. Error messages can be accessed through the “reason” field in the DescribeTasks API response, which is a short, human-readable string that provides details about a running or stopped container. Previously, error messages beyond 255 characters were truncated. With the increased limit to 1024 characters, customers can now surface and view richer error details, making troubleshooting faster.

Customers can access longer container exit reason messages through the AWS Management Console and the DescribeTasks API. This improvement is available in all AWS regions for tasks deployed on Fargate Platform 1.4.0 or container instances with ECS Agent v1.92.0 or later. To learn more, refer to the documentation and release notes .
 

CloudWatch Database Insights adds support for Aurora Limitless PostgreSQL

By

CloudWatch Database Insights announces support for Amazon Aurora PostgreSQL Limitless databases. Database Insights is a database observability solution that provides a curated experience designed for DevOps engineers, application developers, and database administrators (DBAs) to expedite database troubleshooting and gain a holistic view into their database fleet health.

Database Insights consolidates logs and metrics from your applications, your databases, and the operating systems on which they run into a unified view in the console. Using its pre-built dashboards, recommended alarms, and automated telemetry collection, you can monitor the health of your database fleets and use a guided troubleshooting experience to drill down to individual instances for root-cause analysis. You can now enable Database Insights on Aurora Limitless databases and start monitoring how database load is spread across your Limitless shard groups.

You can get started with Database Insights for Aurora Limitless by enabling it on your Limitless databases using the Aurora service console, AWS APIs, and SDKs.

Database Insights for Aurora Limitless is available in all regions where Aurora Limitless is available and applies a new ACU-based pricing – see pricing page for details. For further information, visit the Database Insights documentation .

Scroll Up