8/27/2025, 12:00:00 AM ~ 8/28/2025, 12:00:00 AM (UTC)
Recent Announcements
AWS Client VPN extends OS support to Windows Arm64 v5.3.0
AWS Client VPN now supports Windows Arm64 client with version 5.3.0. You can now run the AWS supplied VPN client on the latest Windows Arm64 OS versions. AWS Client VPN desktop clients are available free of charge, and can be downloaded here.\n AWS Client VPN is a managed service that securely connects your remote workforce to AWS or on-premises networks. It supports desktop clients for MacOS, Windows x64, Windows Arm64 and Ubuntu-Linux. With this release, Client VPN now supports the Windows Arm64 5.3.0. It already supports Mac OS version 13.0, 14.0 and 15.0, Windows 10 (x64) and Windows 11 (Arm64 and x64), and Ubuntu Linux 22.04 and 24.04 LTS versions. This client version is available in all regions where AWS Client VPN is generally available with no additional cost. To learn more about Client VPN:
Visit the AWS Client VPN product page
Read the AWS Client VPN documentation
Read the AWS Client VPN user guide
AWS Transfer Family introduces Terraform support for deploying SFTP connectors
AWS Transfer Family Terraform module now supports deployment of SFTP connectors to transfer files between Amazon S3 and remote SFTP servers. This adds to the existing support for deploying SFTP server endpoints using Terraform, enabling you to automate and streamline centralized provisioning of file transfer resources using Infrastructure as Code (IaC).\n SFTP connectors provide a fully managed and low-code capability to copy files between Amazon S3 and remote SFTP servers. You can now use Terraform to programmatically provision your SFTP connectors, associated dependencies and customizations in a single deployment. The module also provides end-to-end examples to automate file transfer workflows based on a schedule or event triggers. Using Terraform for deployment eliminates the need for time-consuming and error-prone manual configurations, and provides you a fast, repeatable and secure deployment option that can scale. Customers can get started by downloading the Terraform module source code on GitHub. To learn more about Transfer Family, visit the product page and user guide. To see all the regions where Transfer Family is available, visit the AWS Region table.
SageMaker HyperPod now supports customer managed KMS keys for EBS volumes
Amazon SageMaker HyperPod now supports customer managed AWS KMS keys (CMK) for encrypting EBS volumes, enabling enterprise customers to deploy machine learning clusters that meet their specific organizational security and compliance requirements. Customers training foundation models need full control over their encryption keys while maintaining high-performance computing capabilities, but previously could only rely on SageMaker HyperPod owned keys for cluster storage encryption.\n This capability allows customers to encrypt both root and secondary EBS volumes using their own KMS keys, delivering enhanced security controls, regulatory compliance capabilities, and integration with existing key management workflows. The feature uses a grants-based approach for secure cross-account access and supports independent key selection for root and secondary volumes. You can specify customer managed KMS keys when creating or updating clusters using the CreateCluster and UpdateCluster APIs for clusters in continuous provisioning mode. Customer managed KMS key support is available in all AWS Regions where SageMaker HyperPod is available. To learn more about customer managed key encryption for SageMaker HyperPod, see the user guide.
Amazon EC2 C7i instances are now available in Asia Pacific (Osaka) Region
Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C7i instances powered by custom 4th Gen Intel Xeon Scalable processors (code-named Sapphire Rapids) are available in the Asia Pacific (Osaka) Region. C7i instances are supported by custom Intel processors, available only on AWS, and offer up to 15% better performance over comparable x86-based Intel processors utilized by other cloud providers.\n C7i instances deliver up to 15% better price-performance versus C6i instances and are a great choice for all compute-intensive workloads, such as batch processing, distributed analytics, ad-serving, and video encoding. C7i instances offer larger instance sizes, up to 48xlarge, and two bare metal sizes (metal-24xl, metal-48xl). These bare-metal sizes support built-in Intel accelerators: Data Streaming Accelerator, In-Memory Analytics Accelerator, and QuickAssist Technology that are used to facilitate efficient offload and acceleration of data operations and optimize performance for workloads. C7i instances support new Intel Advanced Matrix Extensions (AMX) that accelerate matrix multiplication operations for applications such as CPU-based ML. Customers can attach up to 128 EBS volumes to a C7i instance vs. up to 28 EBS volumes to a C6i instance. This allows processing of larger amounts of data, scale workloads, and improved performance over C6i instances. To learn more, visit Amazon EC2 C7i Instances. To get started, see the AWS Management Console.
Amazon SageMaker HyperPod now supports Amazon EBS CSI driver for persistent storage
Amazon SageMaker HyperPod now supports the Amazon Elastic Block Store (EBS) Container Storage Interface (CSI) driver, enabling customers to dynamically provision and manage persistent storage for machine learning workloads on SageMaker HyperPod EKS clusters. This capability allows customers to create, attach, and manage EBS volumes through Kubernetes persistent volume claims, providing storage that persists across pod restarts and node replacements. Customers deploying training and inference workloads need flexible storage allocation while maintaining high performance, but previously required manual EBS volume management outside Kubernetes workflows.\n EBS CSI driver support enables customers to dynamically provision volumes based on model requirements, resize volumes without service disruption, and create snapshots for backup and recovery. For training workloads, this provides persistent storage for datasets, model checkpoints, and shared artifacts. For inference workloads, customers can provision model storage, create caching volumes, and maintain event logging. The integration supports both static and dynamic provisioning through Kubernetes storage classes, optimizing storage costs and performance. To get started, install the Amazon EBS CSI driver as an EKS add-on on your HyperPod EKS cluster, then provision EBS volumes using standard Kubernetes persistent volume claims and storage classes. The EBS CSI driver manages the complete lifecycle of EBS volumes, including creation, attachment, mounting, and cleanup. Volume encryption with customer-managed KMS keys is supported, and volumes can be resized and snapshotted through standard Kubernetes operations. This feature is available in all AWS Regions where SageMaker HyperPod EKS clusters are supported. To learn more about EBS CSI driver support, see the Amazon SageMaker HyperPod User Guide.
Custom Metrics now available in Amazon CloudWatch Application Signals
Amazon CloudWatch Application Signals now supports Custom Metrics, empowering developers and operators to pinpoint the root cause of application issues faster and with greater precision. CloudWatch Application Signals already helps you monitor the health of your applications through standard metrics like fault rates, errors, and latency. Now, you can add your own custom metrics that provide deeper context about your application’s behavior and correlate them with standard metrics in a unified view.\n With Custom Metrics in Application Signals, you can define and visualize application-specific metrics that provide critical context for your services, correlate custom metrics with standard metrics in the new ‘Related Metrics’ tab, identify patterns and dependencies between metrics to narrow down issue root causes, and analyze specific data points through interactive visualization and correlation analysis. You have the flexibility of using either OpenTelemetry Metrics, where you create and export metrics directly from your application code using the OpenTelemetry Metrics SDK or Span Metrics, where you can add custom span attributes using the OpenTelemetry Traces SDK and create metrics from them using Metrics Filters. In the Application Signals console you can select and graph multiple metrics together to visualize correlations, filter metrics by name, type, and other attributes, select data points to view correlated spans, top contributors, and related logs and navigate directly from Service Operations or Dependencies to Related Metrics through correlation analysis.
Custom Metrics support is available in all regions Application Signals is available in. For more information about custom metrics, refer to the documentation. For pricing details, see Amazon CloudWatch pricing.
New P5 instance with one NVIDIA H100 GPU is now available in SageMaker Training and Processing Jobs
Today, SageMaker Training and Processing Jobs announces the new Amazon EC2 P5 instance size with one NVIDIA H100 GPU. It allows businesses to right-size their machine learning (ML) and high-performance computing (HPC) resources with cost-effectiveness. The new P5 instance type gives customers the flexibility to begin with smaller configurations and expand incrementally with fine-grained control, delivering enhanced cost management for their infrastructure investments.\n P5.4xlarge instances are now available through SageMaker Flexible Training Plans in the following AWS Regions: US East (North Virginia, Ohio), US West (Oregon), Europe (London), Asia Pacific (Mumbai, Sydney, Tokyo), and South America (Sao Paulo). Additionally, the instance type can be purchased through SageMaker On-Demand and Spot in the Europe (London), Asia Pacific (Mumbai, Jakarta, Tokyo), and South America (Sao Paulo) AWS Regions.
To learn more about P5.4xlarge instances, visit Amazon EC2 P5 instances.
AWS App Runner expands support for IPv6 compatibility
AWS App Runner now supports IPv6-based inbound and outbound traffic on both public and private App Runner service endpoints. This helps customers meet IPv6 compliance requirements, and removes the need for handling address translation between IPv4 and IPv6.\n App Runner is a fully-managed service that makes it easier for developers to quickly deploy containerized web applications and APIs to the cloud, at scale, and without managing infrastructure. Previously, IPv6 was only supported on incoming traffic through public endpoints. You can configure IPv6 by selecting the dual-stack option in your networking configuration on new or existing services. AWS App Runner support for IPv6 is available in all AWS Regions where AWS App Runner is available. For more information about how to manage dual-stack support for your App Runner service, see Networking with App Runner in the AWS App Runner Developer Guide.
AWS Management Console now supports assigning a color to an AWS account for easier identification
Today, AWS announces the general availability of account color settings in AWS Management Console across all Public Regions. AWS customers now have an easy way to identify their accounts at a glance. Using the account color setting, account admins can assign a color to their AWS account (such as red for production accounts or yellow for testing accounts) that appears in the Console’s navigation bar for all authorized users in that account, enabling quick visual identification of different accounts.\n AWS customers manage multiple accounts to separate their workloads, such as maintaining distinct accounts for development and production environments or for different business units. Previously, users had to rely on account numbers to identify accounts. With this new feature, users with admin privileges can assign colors to AWS accounts, enabling all authorized users to quickly identify the account they want to operate on through the colored navigation bar. When signing in to the AWS Console, users see a default grey color in the navigation bar. Users with admin privileges can change this color through the ‘Account’ option in the navigation bar’s account menu, on the top right of the page. Once the color is set, all users with proper permissions can see it. To view the account color, users need to be assigned permissions using the AWS managed policy AWSManagementConsoleBasicUserAccess or the custom permission uxc:getaccountcolor.
To learn more about account colors, click here. To get started with setting account color, click here.
AWS Blogs
AWS Japan Blog (Japanese)
- Important Kiro pricing notice
- Achieving High Availability and Fast Disaster Recovery for Amazon RDS for Db2 Using Cross-Region Standby Replicas
- IDEMY’s SaaS on AWS case: The data storage platform “Lab Bank” for material development for research and development departments in the materials industry has been multi-tenanted on AWS. Utilize managed services to build a secure environment with a small number of people and in a short period of time.
- AWS-generated AI case by WinSystem Co., Ltd.: Development productivity improved tenfold by utilizing Cline with Amazon Bedrock
- Transform your machine learning career with AWS Jam
AWS Cloud Operations Blog
AWS Big Data Blog
- Modernize Amazon Redshift authentication by migrating user management to AWS IAM Identity Center
- Implement fine-grained access control using Amazon OpenSearch Service and JSON Web Tokens
- How Ancestry optimizes a 100-billion-row Iceberg table