10/22/2024, 12:00:00 AM ~ 10/23/2024, 12:00:00 AM (UTC)

Recent Announcements

AWS Mainframe Modernization introduces new integrations for managed runtimes

We are excited to announce that the AWS Mainframe Modernization service now offers new integrations that provide greater flexibility of managed runtime environments running modernized mainframe applications. The new capabilities include new integrations with LDAP, LRS print and output management, AWS Health events, and support for Amazon EC2 M7i instances.\n For applications modernized using AWS Mainframe Modernization Replatform with Micro Focus and running on managed runtime environments, customers now have additional integration options. They can configure the managed runtimes to integrate with LRS VPSX Enterprise for centralized, scalable print and output management. Furthermore, application-level security can now be enhanced with LDAP/AD authorization support, enabling granular security controls when accessing application resources. With managed runtime environments now supporting the latest EC2 M7i instance types, customers benefit from improved performance and cost efficiency as they migrate mainframe applications to the cloud. Additionally, they integrate with AWS Health, enabling operational event monitoring and enhanced visibility into modernized mainframe workloads running on AWS. The new capabilities are available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.

Announcing the new Resiliency widget on myApplications

Today, we are excited to announce the launch of the new Resiliency widget on myApplications, providing enhanced visibility and proactive control over the resilience posture for each application in myApplications.\n Using the new Resiliency widget, you can start a resilience assessment directly from the myApplications dashboard. AWS Resilience Hub will automatically create an application based on the constructs defined in myApplications, eliminating the need for manual replication. It will then assess the application against a predefined policy and publish the results. The Resiliency widget provides the most recent, actionable insights into the application’s resilience, potential vulnerabilities, and recommended actions for improvement. You can access the full capabilities of AWS Resilience Hub with a single click to view more details. You can access the Resiliency widget on myApplications by signing into the AWS Management Console. To learn more about AWS Resilience Hub, visit the product page or technical documentation. To learn more about myApplications, visit the feature documentation.

Amazon EKS now supports Amazon Application Recovery Controller (ARC)

Amazon Elastic Kubernetes Service (Amazon EKS) now supports Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift. ARC helps you manage and coordinate recovery for your applications across AWS Regions and Availability Zones (AZs). With EKS support for ARC zonal shift and zonal autoshift, you can better maintain Kubernetes application availability by automating the process of shifting in-cluster network traffic away from an impaired AZ.\n Customers increasingly deploy highly available applications in Amazon EKS across multiple AZs to eliminate a single point of failure. If you’re running multi-AZ applications in EKS, you can now quickly shift application traffic away from an impaired AZ in your cluster. With zonal shift, you can temporarily mitigate issues and incidents by triggering a shift and redirecting in-cluster network traffic to a healthy AZ. For a fully automated experience, you can authorize AWS to manage this shift on your behalf using zonal autoshift. With zonal autoshift, you can configure practice runs to test that your cluster environment functions as expected with one less AZ. To get started, you can enable zonal shift using the Amazon EKS Console, the AWS CLI, CloudFormation or eksctl. Once enabled, you can manage zonal shifts or zonal autoshifts using the ARC Console, the AWS CLI, or the Zonal Shift and Zonal Autoshift APIs. EKS support for ARC zonal shift and zonal autoshift is available in all commercial AWS Regions, excluding the AWS GovCloud (US) Regions. To get started, visit our documentation.

Amazon Redshift launches query profiler for enhanced query monitoring and diagnostics

Amazon Redshift introduces query profiler for enhanced query visibility and troubleshooting. The query profiler is a feature in the AWS console that provides a visual and graphical representation of query execution plans and statistics, letting you easily monitor, analyze, and troubleshoot query performance without the need for manual analysis of system tables and logs.\n Enhanced query profiling in Amazon Redshift expands the current capabilities in the AWS console that let you monitor both running and completed queries. With the new query profiler, you can now further introspect your queries and review execution plans to discover query performance bottlenecks. The query profiler uses data from system views like SYS_QUERY_DETAIL to include performance metrics that help you optimize queries, including execution time, total input/output rows, and bytes read/written for each step of the query. The query profiler capability is now generally available for both Amazon Redshift Serverless and Amazon Redshift provisioned data warehouses in all AWS commercial and the AWS GovCloud (US) Regions where Amazon Redshift is available. To get started and learn more about using the query profiler, visit the Amazon Redshift database developer guide.

Amazon Application Recovery Controller zonal shift and zonal autoshift extends support for two new multi-AZ resources

Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift have expanded their capabilities and now support Amazon Elastic Kubernetes Service (Amazon EKS) and Network Load Balancers (NLB) with cross-zone configuration enabled. ARC zonal shift helps customers quickly recover an unhealthy application in an Availability Zone (AZ), and reduce the duration and severity of impact to the application due to events such as power outages and hardware or software failures. ARC zonal autoshift safely and automatically shifts an application’s traffic away from an AZ when AWS identifies a potential failure affecting that AZ.\n All NLB customers can now shift traffic away from an AZ in the event of a failure. Zonal shift works with NLB by blocking all traffic to targets in an impaired AZ and removing the zonal IP from DNS responses while it is active. You can enable NLBs for zonal shift using the NLB console or API. Amazon EKS customers can now shift traffic away from an AZ in the event of a failure. Zonal shift works with Amazon EKS by shifting in-cluster traffic to healthy AZs and ensuring Pods aren’t scheduled in the impaired AZ. You can enable EKS clusters for zonal shift using the EKS console or API. You can start a zonal shift or enable Zonal autoshift in the ARC console for EKS and NLB resources. There is no additional charge for using zonal shift or zonal autoshift. See the AWS Regional Services List for the most up-to-date availability information.

Anthropic’s upgraded Claude 3.5 Sonnet model and computer use now in Amazon Bedrock

Anthropic’s upgraded Claude 3.5 Sonnet model is now available in Amazon Bedrock. According to Anthropic, the model delivers across-the-board improvements over its predecessor, with significant gains in coding—an area where it already led the field.\n The upgraded Claude 3.5 Sonnet model shows wide-ranging improvements on industry benchmarks. On coding the model improves performance on SWE-bench Verified from 33% to 49%, scoring higher than all publicly available models, according to Anthropic. It also improves performance on TAU-bench, an agentic tool use task, from 62.6% to 69.2% in the retail domain, and from 36.0% to 46.0% in the airline domain. The new Claude 3.5 Sonnet offers these advancements at the same price of its predecessor. Additionally, Claude 3.5 Sonnet now offers computer use capabilities in Amazon Bedrock in a public beta, allowing Claude to perceive and interact with computer interfaces. Developers can direct Claude to use computers the way people do—by looking at a screen, moving a cursor, clicking buttons, and typing text. Given this technology is early, developers are encouraged to explore lower-risk tasks. The upgraded Claude 3.5 Sonnet model is now available in Amazon Bedrock in the US West (Oregon) Region. Computer use is now available in public beta. To learn more, read the AWS News launch blog, Claude in Amazon Bedrock product page, and documentation. To get started with Claude, visit the Amazon Bedrock console.

Amazon Aurora launches Global Database writer endpoint

Amazon Aurora now supports a Global Database writer endpoint. This highly available and fully managed endpoint simplifies routing for your applications and eliminates the need to make application code changes to establish connectivity after initiating a cross-region Global Database Switchover or Failover operation.\n With Global Database, a single Aurora cluster can span multiple AWS Regions, providing disaster recovery from Region-wide outages and enabling fast local reads for globally distributed applications. The new Global Database writer endpoint automatically updates to point to the current writer instance in your global cluster. This eliminates the need to modify your application code or configuration after you initiate a cross-region failover or switchover to change the location of the primary cluster in your Global Database. The endpoint is created automatically for your global clusters and can be found on the AWS Management Console, or using the RDS CLI or API. The feature is available in all AWS Regions where Aurora Global Database is available. See our documentation to learn more. Amazon Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. To get started with Amazon Aurora, take a look at our getting started page.

Enhanced Monitoring for applications hosted on Amazon ECS via Application Signals

Today, AWS announces enhanced monitoring for applications hosted in Amazon ECS with Amazon CloudWatch Application Signals, an application performance monitoring (APM) feature in CloudWatch, that makes it easy to automatically instrument and track application performance against their most important business or service level objectives (SLOs). With no manual effort or custom code required, Application Signals’ support for ECS already offered service operators a pre-built, standardized dashboard showcasing essential application performance metrics—volume, availability, latency, faults, and errors—for each application. In this launch, it further enhances this visibility by adding infrastructure metrics correlation for ECS, alongside existing traces and logs correlation, enabling a more complete view of application health.\n By correlating telemetry across application metrics, traces, logs, real-user monitoring, synthetic monitoring and infrastructure metrics, Application Signals enables customers to speed up troubleshooting and reduce application disruptions. For example, an application developer managing a payment processing application can begin their investigation with Application Signals to detect any spikes in payment processing latency. From there, they can delve into infrastructure metrics through ECS Container Insights, enabling them to determine if the issue is linked to specific ECS tasks, such as high CPU usage or memory shortage. Application Signals enhancements for ECS is available in 28 commercial AWS Regions, except, CA West (Calgary) Region, AWS GovCloud (US) Regions and China Regions. For pricing, see Amazon CloudWatch pricing. To learn more, see documentation to enable Amazon CloudWatch Application Signals on your applications hosted in Amazon ECS. To try Application Signals on a sample application hosted on ECS follow these instructions.

Amazon EKS endpoints now support connectivity over Internet Protocol version 6 (IPv6)

Amazon EKS introduces dual stack support for the EKS management API endpoint and the Kubernetes API server endpoint in IPv6 EKS clusters, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when the EKS management API endpoint is privately accessed from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink. Dual stack endpoints are made available on a new AWS DNS domain name. The existing EKS management API endpoints are maintained for backwards compatibility reasons.\n The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on EKS endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6. This launch only affects EKS managed endpoints and does not change the behavior of pod networking. To understand how EKS supports IPv6 connectivity in pods, refer to this blog. There is no additional charge when you connect to EKS endpoints using Internet Protocol Version 6 (IPv6) clients. To learn more, see EKS user guide.

Gain deeper insights into Amazon Q Business with new analytics and conversation insights

Amazon Q Business now offers an analytics dashboard and integration with Amazon CloudWatch Logs, providing comprehensive insights into the usage of your Amazon Q Business application environments and Amazon Q Apps. The new analytics dashboard in the Amazon Q Business console offers insights through interactive charts and visualizations, enabling administrators to monitor key metrics such as usage trends, user conversations, query trends, and user feedback. Additionally, user chat conversation and feedback information is now available in Amazon CloudWatch Logs, Amazon S3 and Amazon Data Firehouse, allowing you to ingest and analyze this data to build custom dashboards if needed.\n These new features empower administrators to monitor, analyze, and optimize Amazon Q Business for their users. The analytics dashboard provides at-a-glance visibility into performance metrics, while the Amazon CloudWatch Logs integration enables in-depth analysis of conversation data and user feedback. Whether you need to track usage patterns, identify areas for improvement, or gain deeper insights into user interactions, these capabilities offer valuable tools for enhancing your Amazon Q Business experience. The new analytics dashboard and Amazon CloudWatch Logs integration for Amazon Q Business are now available in all AWS Regions where Amazon Q Business is available. To learn more, visit the Amazon Q Business documentation, or activate your analytics dashboard to start leveraging these powerful insights.

AWS DMS now supports homogenous migrations via CLI, SDK and API

AWS Database Migration Service (DMS) announces the general availability of CLI, SDK and API support for homogenous data migrations. This launch enables programmatic migration or replication of your self-managed MySQL, PostgreSQL, MariaDB, or MongoDB databases from on-premises or Amazon EC2 sources, to equivalent targets on Amazon Relational Database Service (RDS), Amazon Aurora, or Amazon DocumentDB. Homogenous data migrations provide easy and performant like-to-like migrations with minimal downtime and zero data loss.\n Using the AWS API, AWS CLI or AWS SDK you can initiate fully automated homogeneous migrations or replications including all data types, secondary objects, and partitions. This feature is serverless, so there is no need to manage replication instances. Homogenous data migrations are generally available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), Canada West (Calgary), South America (São Paulo), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Osaka), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Jakarta), Asia Pacific (Melbourne), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Hyderabad, Europe (Frankfurt), Europe (Zurich), Europe (Stockholm), Europe (Ireland), Europe (London), Europe (Paris), Europe (Milan), Europe (Spain), Middle East (UAE), Middle East (Bahrain), Israel (Tel Aviv), and Africa (Cape Town). See AWS DMS homogeneous data migrations to learn more.

AWS Lambda console now features a new code editor based on Code-OSS (VS Code - Open Source)

Today, AWS Lambda announces the launch of a new code editing experience in the Lambda console based on Code-OSS (VS Code – Open Source). This integration brings new interface and productivity features directly into the Lambda console, giving customers a more intuitive coding environment when building serverless applications.\n The new Code-OSS (VS Code – Open Source) based code editor on console offers a similar layout to the desktop version of the editor and includes features such as the command palette and quick search. Developers can apply preferred themes and personalize their settings, mirroring their local development environment setup. Additionally, this new editor allows customers to enable an Amazon Q Developer extension for real-time code suggestions and insights to help boost productivity. Developers can also view their function code and test results simultaneously, streamlining the development and debugging workflow. The new code editor is available in all AWS Regions where Lambda is available. To learn more about the new editing experience based on Code-OSS (VS Code – Open Source), visit the compute blog.

Amazon OpenSearch Serverless now available in the AWS GovCloud (US-East) Region

We are excited to announce that Amazon OpenSearch Serverless is expanding its availability to the AWS GovCloud (US-East) Region. OpenSearch Serverless is a serverless deployment option for Amazon OpenSearch Service that makes it simple to run search and analytics workloads without the complexities of infrastructure management. OpenSearch Serverless’ compute capacity used for data ingestion, search, and query is measured in OpenSearch Compute Units (OCUs).\n The support for OpenSearch Serverless is now available in 17 regions globally: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe West (Paris), Europe West (London), Asia Pacific South (Mumbai), South America (Sao Paulo), Canada Central (Montreal), Asia Pacific (Seoul). Europe (Zurich), AWS GovCloud (US-West), and AWS GovCloud (US-East). 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.

AWS Blogs

AWS Japan Blog (Japanese)

AWS News Blog

AWS Cloud Operations Blog

AWS Big Data Blog

AWS Compute Blog

AWS Database Blog

AWS DevOps & Developer Productivity Blog

AWS HPC Blog

AWS Machine Learning Blog

AWS Security Blog

Open Source Project

AWS CLI

AWS CDK

Amplify for iOS

Amplify for Flutter

Amplify UI

Bottlerocket OS