Monat: September 2025

Amazon EC2 Auto Scaling expands AWS PrivateLink support to FIPS endpoints

Starting today, Amazon EC2 Auto Scaling (ASG) supports Federal Information Processing Standard (FIPS) 140-3 validated VPC endpoints. With this launch, you can use AWS PrivateLink with ASG for regulated workloads that require secure connections using FIPS 140-3 validated cryptographic modules. FIPS-compliant endpoints help organizations contracting with the U.S. federal government meet FIPS security requirements for encrypting sensitive data in supported regions. To create a VPC endpoint that connects to an ASG endpoint, see Setting up a VPC endpoint for Amazon EC2 Auto Scaling. This capability is available in the following regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), and Canada West (Calgary). For more information about FIPS 140-3 at AWS, visit FIPS 140-3 Compliance. To learn more about Amazon EC2 Auto Scaling, visit the ASG product page.
Quelle: aws.amazon.com

Amazon ECS announces IPv6-only support

Amazon Elastic Container Service (Amazon ECS) now supports running tasks in IPv6-only subnets. With this launch, Amazon ECS tasks and services can run using only IPv6 addresses, without requiring IPv4. This enables customers to deploy containerized applications in IPv6-only environments, scale without being limited by IPv4 address availability, and meet IPv6 compliance requirements through native IPv6 support in Amazon ECS. Previously, Amazon ECS tasks always required an IPv4 address, even when launched in dual-stack subnets. This requirement could create scaling and management challenges for customers operating large fleets of containerized applications, where IPv4 address space became a bottleneck. With IPv6-only support, Amazon ECS tasks launched in IPv6-only subnets use only IPv6 addresses. This removes IPv4 as a dependency and helps organizations that must meet IPv6 adoption or regulatory mandates. The feature works across all Amazon ECS launch types and can be used with awsvpc, bridge, and host networking modes. To get started, create IPv6-only subnets in your VPC and launch Amazon ECS services or tasks in those subnets. Amazon ECS automatically detects the configuration and provisions the appropriate networking. To learn more about IPv6-only task networking and supported AWS Regions, see the Amazon ECS task networking documentation for AWS Fargate launch type and EC2 launch type. You can also read our blog post for a detailed walkthrough and migration strategies.
Quelle: aws.amazon.com

Amazon EC2 Auto Scaling now supports Internet Protocol Version 6 (IPv6)

Amazon EC2 Auto Scaling (ASG) now supports Internet Protocol Version 6 (IPv6), enabling dual-stack configuration (IPv4 and IPv6) connectivity for your Auto Scaling groups. IPv6 enables an expanded address space, enabling you to scale your application on AWS beyond the typical constraints of the number of IPv4 addresses in your VPC. With IPv6, you can assign easy to manage contiguous IP ranges to micro-services and can get virtually unlimited scale for your applications. Moreover, with support for both IPv4 and IPv6, you can gradually transition applications from IPv4 to IPv6, enabling safer migration. IPv6 support is available in all commercial AWS regions (except New Zealand) and GovCloud regions where ASG is available. To learn more about configuring your network to use IPv6 endpoints, see the documentation.
Quelle: aws.amazon.com