#AmazonElasticLoadBalancing
🆕 AWS Transform migrates F5 BIG-IP to Elastic Load Balancing with ALB/NLB, cutting time and avoiding post-migration projects. Available in all regions. See AWS Transform docs for details.

#AWS #AmazonElasticLoadBalancing
AWS Transform now provides F5 BIG-IP load balancer migration
AWS Transform now migrates F5 BIG-IP load balancer configurations to Elastic Load Balancing as part of network migration. Applications cut over with Application Load Balancers (ALB) and Network Load Balancers (NLB) already in place allowing you to adopt cloud-native load balancing during migration rather than after it. Moving to ALB and NLB has typically been a separate post-migration project because of time and cost. Teams rebuilt each F5 BIG-IP virtual server by hand, a slow and error-prone process that could break when traffic moved. AWS Transform compresses that timeline and enables the F5 to Elastic Load Balancing transition during migration, allowing you to run your cloud migration with network, load balancing, and compute moving as a coordinated unit. You can migrate F5 BIG-IP load balancers in every AWS Transform for migrations target Region. To get started, see the AWS Transform documentation, or visit the AWS Transform product page.
aws.amazon.com
November 18, 2026 at 3:10 PM
AWS Transform now provides F5 BIG-IP load balancer migration

AWS Transform now migrates F5 BIG-IP load balancer configurations to Elastic Load Balancing as part of network migration. Applications cut over with Application Load Balancers (ALB) and Network Load Ba...

#AWS #AmazonElasticLoadBalancing
AWS Transform now provides F5 BIG-IP load balancer migration
AWS Transform now migrates F5 BIG-IP load balancer configurations to Elastic Load Balancing as part of network migration. Applications cut over with Application Load Balancers (ALB) and Network Load Balancers (NLB) already in place allowing you to adopt cloud-native load balancing during migration rather than after it. Moving to ALB and NLB has typically been a separate post-migration project because of time and cost. Teams rebuilt each F5 BIG-IP virtual server by hand, a slow and error-prone process that could break when traffic moved. AWS Transform compresses that timeline and enables the F5 to Elastic Load Balancing transition during migration, allowing you to run your cloud migration with network, load balancing, and compute moving as a coordinated unit. You can migrate F5 BIG-IP load balancers in every https://docs.aws.amazon.com/transform/latest/userguide/transform-vmware-connect-target-account.html#transform-vmware-cta-supported-regions. To get started, see the https://docs.aws.amazon.com/transform/latest/userguide/transform-app-vmware.html, or visit the https://aws.amazon.com/transform/.
aws.amazon.com
November 18, 2026 at 3:05 PM
🆕 AWS Network Load Balancer is now in Phoenix Local Zone (us-west-2-phx-2a), lowering latency for local traffic and aiding latency-sensitive apps like gaming and streaming. Local routing boosts Phoenix user performance. For details, check AWS docume…

#AWS #AmazonElasticLoadBalancing #AwsLocalZones
AWS Network Load Balancer is now available in the AWS Phoenix Local Zone
AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a). AWS Local Zones is a type of AWS infrastructure deployment that places AWS compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists today. With this launch, you can create an AWS Network Load Balancer directly in the Phoenix Local Zone. Previously, if your targets ran in the Phoenix Local Zone, you had to place the load balancer in an Availability Zone in the parent Region, so connections and their traffic had to travel to the parent Region and back. This added latency and routed traffic outside the zone where your application runs. Now, connection routing stays local to your targets, delivering lower and more consistent latency to end users in the Phoenix metro area and keeping traffic within the Local Zone. This is especially valuable for latency-sensitive workloads such as real-time gaming, media streaming, and live financial applications serving users in the region. To learn more about Network Load Balancer, visit the documentation. For more information on AWS Local Zones, visit the AWS Local Zones website. The Locations webpage lists the available and announced Local Zones. You can enable AWS Local Zones from the Local Zones tab in the AWS Global View console, or the ModifyAvailabilityZoneGroup API.
aws.amazon.com
November 6, 2026 at 1:40 AM
AWS Network Load Balancer is now available in the AWS Phoenix Local Zone

AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a). AWS Local Zones is a type of AWS infrastructure deployment that places AWS compute, s...

#AWS #AmazonElasticLoadBalancing #AwsLocalZones
AWS Network Load Balancer is now available in the AWS Phoenix Local Zone
AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a). AWS Local Zones is a type of AWS infrastructure deployment that places AWS compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists today. With this launch, you can create an AWS Network Load Balancer directly in the Phoenix Local Zone. Previously, if your targets ran in the Phoenix Local Zone, you had to place the load balancer in an Availability Zone in the parent Region, so connections and their traffic had to travel to the parent Region and back. This added latency and routed traffic outside the zone where your application runs. Now, connection routing stays local to your targets, delivering lower and more consistent latency to end users in the Phoenix metro area and keeping traffic within the Local Zone. This is especially valuable for latency-sensitive workloads such as real-time gaming, media streaming, and live financial applications serving users in the region. To learn more about Network Load Balancer, visit the https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html. For more information on AWS Local Zones, visit the https://aws.amazon.com/about-aws/global-infrastructure/localzones/. The https://aws.amazon.com/about-aws/global-infrastructure/localzones/locations/ lists the available and announced Local Zones. You can enable AWS Local Zones from the https://us-east-1.console.aws.amazon.com/awsglobalview/home#RegionsAndZones:tabId=lztab in the AWS Global View console, or the https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyAvailabilityZoneGroup.html API.
aws.amazon.com
November 6, 2026 at 2:05 AM
🆕 AWS Transfer Family now supports source IP for SFTP behind NLB with Proxy Protocol v2, enabling true client IP visibility for auditing. Available globally; enable via console, CLI, or API.

#AWS #AwsTransferFamily #AmazonElasticLoadBalancing
AWS Transfer Family now supports source IP preservation for SFTP servers behind a Network Load Balancer (NLB)
AWS Transfer Family now preserves the client's source IP address using Proxy Protocol v2 (PPv2) when you place a Network Load Balancer (NLB) in front of your SFTP server that uses a VPC-hosted endpoint. You can now retain visibility of the client's source IP for IP-based auditing, access controls, and compliance when you use your own NLB. Previously, an NLB replaced the client's source IP with its own private IP address, so your Transfer Family logs and events recorded the NLB's address instead of the client's source IP. Because the NLB's private IP was the address presented to your custom identity provider during authentication, you couldn't authorize users based on their true source IP. With this launch, you can enable source IP preservation on your SFTP server so that the client's source IP is preserved. The preserved source IP is recorded in your logs and events and presented to your custom identity provider during authentication. You can enable the feature on each Transfer Family server individually through the console, CLI, or API. Source IP preservation for SFTP servers is available in all AWS Regions where AWS Transfer Family is available. To get started, visit the AWS Transfer Family console or use the AWS CLI/SDK. To learn more, visit the Transfer Family User Guide.
aws.amazon.com
September 17, 2026 at 8:10 PM
AWS Transfer Family now supports source IP preservation for SFTP servers behind a Network Load Balancer (NLB)

AWS Transfer Family now preserves the client's source IP address using Proxy Protocol v2 (PPv2) when you place a Network Load Balance...

#AWS #AwsTransferFamily #AmazonElasticLoadBalancing
AWS Transfer Family now supports source IP preservation for SFTP servers behind a Network Load Balancer (NLB)
AWS Transfer Family now preserves the client's source IP address using Proxy Protocol v2 (PPv2) when you place a Network Load Balancer (NLB) in front of your SFTP server that uses a VPC-hosted endpoint. You can now retain visibility of the client's source IP for IP-based auditing, access controls, and compliance when you use your own NLB. Previously, an NLB replaced the client's source IP with its own private IP address, so your Transfer Family logs and events recorded the NLB's address instead of the client's source IP. Because the NLB's private IP was the address presented to your custom identity provider during authentication, you couldn't authorize users based on their true source IP. With this launch, you can enable source IP preservation on your SFTP server so that the client's source IP is preserved. The preserved source IP is recorded in your logs and events and presented to your custom identity provider during authentication. You can enable the feature on each Transfer Family server individually through the console, CLI, or API. Source IP preservation for SFTP servers is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. To get started, visit the AWS Transfer Family console or use the AWS CLI/SDK. To learn more, visit the Transfer%20Family%20User%20Guide.
aws.amazon.com
September 17, 2026 at 8:05 PM
🆕 AWS Gateway Load Balancer now supports TCP Reset for faster failure recovery, reducing interruptions from minutes to seconds by sending RST packets when targets fail or idle timeouts expire, available in all regions with no extra charge.

#AWS #AmazonElasticLoadBalancing
AWS Gateway Load Balancer now supports TCP Reset for faster failure recovery
AWS Gateway Load Balancer (GWLB) now supports sending TCP Reset (RST) packets when a target becomes unhealthy, is deregistered, or when a flow's idle timeout expires. This feature helps reduce traffic interruptions from minutes to seconds by enabling TCP endpoints to quickly detect failed connections and establish new TCP flows through healthy targets. Previously, when a GWLB target failed, existing TCP connections would continue to be forwarded to the unhealthy target (aka fail-open behavior). Client and server applications could experience interruptions lasting several minutes due to TCP retry and exponential back-off mechanisms built in the TCP stacks of clients or servers. When this capability is enabled, GWLB sends TCP Resets in response to the incoming traffic, indicating to the sender that a TCP connection is no longer viable. This allows TCP endpoints to recover in quickly. TCP Reset is not enabled by default to ensure backward compatibility. You can enable it per target group using the AWS Management Console, AWS CLI, or API. Three triggers are supported independently for generating TCP Reset: target becomes unhealthy, target deregistration (after connection draining), and TCP idle timeout expiry. This feature is available for all new and existing Gateway Load Balancers in all AWS Regions where GWLB is available. There is no additional charge for using this feature. To learn more, visit this AWS blog, and GWLB User Guide here and here.
aws.amazon.com
September 3, 2026 at 9:10 PM
AWS Gateway Load Balancer now supports TCP Reset for faster failure recovery

AWS Gateway Load Balancer (GWLB) now supports sending TCP Reset (RST) packets when a target becomes unhealthy, is deregistered, or when a flow's idle timeout expires. This feature helps...

#AWS #AmazonElasticLoadBalancing
AWS Gateway Load Balancer now supports TCP Reset for faster failure recovery
AWS Gateway Load Balancer (GWLB) now supports sending TCP Reset (RST) packets when a target becomes unhealthy, is deregistered, or when a flow's idle timeout expires. This feature helps reduce traffic interruptions from minutes to seconds by enabling TCP endpoints to quickly detect failed connections and establish new TCP flows through healthy targets. Previously, when a GWLB target failed, existing TCP connections would continue to be forwarded to the unhealthy target (aka fail-open behavior). Client and server applications could experience interruptions lasting several minutes due to TCP retry and exponential back-off mechanisms built in the TCP stacks of clients or servers. When this capability is enabled, GWLB sends TCP Resets in response to the incoming traffic, indicating to the sender that a TCP connection is no longer viable. This allows TCP endpoints to recover in quickly. TCP Reset is not enabled by default to ensure backward compatibility. You can enable it per target group using the AWS Management Console, AWS CLI, or API. Three triggers are supported independently for generating TCP Reset: target becomes unhealthy, target deregistration (after connection draining), and TCP idle timeout expiry. This feature is available for all new and existing Gateway Load Balancers in all AWS Regions where GWLB is available. There is no additional charge for using this feature. To learn more, visit this https://aws.amazon.com/blogs/networking-and-content-delivery/reduce-traffic-interruptions-with-gateway-load-balancer-tcp-reset/, and GWLB User Guide https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/edit-target-group-attributes.html#send-tcp-reset-target-failover and https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/gateway-listeners.html#listener-attributes. 
aws.amazon.com
September 3, 2026 at 9:05 PM
AWS Network Load Balancer now supports Listener Rules for custom traffic routing

Network Load Balancer (NLB) now supports listener rules allowing you to route connections to different target groups based on the source IP address type. With listener rules, a sing...

#AWS #AmazonElasticLoadBalancing
AWS Network Load Balancer now supports Listener Rules for custom traffic routing
Network Load Balancer (NLB) now supports listener rules allowing you to route connections to different target groups based on the source IP address type. With listener rules, a single dual-stack NLB sends IPv6 client traffic to IPv6 targets and IPv4 client traffic to IPv4 targets, preserving the original client IP address end to end for both address families. Previously, serving both IPv4 and IPv6 clients from one NLB meant accepting a tradeoff: either run two separate load balancers (one per IP version) and split clients with DNS, or send all traffic to one target group and lose the original client IP through protocol translation. Listener rules remove that tradeoff by enabling conditional routing at Layer 3, directing each connection to a same-family target group with no translation and no additional infrastructure. You can add listener rules to existing dual-stack NLBs without recreating them. Rules are supported on TCP, UDP, TCP_UDP, and TLS listeners and work alongside existing NLB features including connection draining, target group stickiness, cross-zone load balancing, weighted target groups, and client IP preservation. Listener rules for Network Load Balancer are available in all AWS commercial Regions and the AWS GovCloud (US) Regions at no additional charge. Standard NLB pricing for load balancer hours and LCUs applies. To get started, see https://aws.amazon.com/blogs/networking-and-content-delivery/consolidate-dual-stack-architectures-with-listener-rules-for-network-load-balancer/, and the https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html.
aws.amazon.com
July 22, 2026 at 8:05 PM
AWS Application and Network Load Balancers now support RFC 9151 compliant security policies

AWS Application Load Balancer (ALB) and Network Load Balancer (NLB) now support new TLS-based security policies that comply with RFC 9151 TLS server requirements for Comm...

#AWS #AmazonElasticLoadBalancing
AWS Application and Network Load Balancers now support RFC 9151 compliant security policies
AWS Application Load Balancer (ALB) and Network Load Balancer (NLB) now support new TLS-based security policies that comply with RFC 9151 TLS server requirements for Commercial National Security Algorithm (CNSA) 1.0 suite requirements. These policies implement the cryptographic requirements defined by the US National Security Agency (NSA) for secure communications using TLS 1.2 and TLS 1.3 protocols. Customers who are required to meet CNSA 1.0 TLS security requirements can now use ALB and NLB with RFC 9151 compliant security policies. Broader interoperability policies are also supported, allowing you to implement CNSA by default while maintaining compatibility with non-CNSA clients during their transition to RFC 9151 compliance, minimizing service disruption. This feature is available for ALB and NLB in all AWS Commercial Regions, the AWS GovCloud (US) Regions, and the China region at no additional cost. To use this capability, update your existing ALB HTTPS listeners or NLB TLS listeners to a RFC 9151 compliant security policy, or select a compliant policy when creating new listeners through the AWS Management Console, CLI, API, or SDK. To learn more, visit the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/describe-ssl-policies.html and https://docs.aws.amazon.com/elasticloadbalancing/latest/network/describe-ssl-policies.html documentation. Get started with https://aws.amazon.com/elasticloadbalancing/.
aws.amazon.com
August 4, 2026 at 8:05 PM
Amazon CloudWatch Logs now supports Application Load Balancer logs

Amazon CloudWatch Logs now supports Application Load Balancer (ALB) logs as vended logs, improving observability and simplifying debugging for network traffic patterns. You ...

#AWS #AmazonElasticLoadBalancing #AmazonCloudwatchLogs
Amazon CloudWatch Logs now supports Application Load Balancer logs
Amazon CloudWatch Logs now supports Application Load Balancer (ALB) logs as vended logs, improving observability and simplifying debugging for network traffic patterns. You can now analyze ALB access, connection and health check logs directly in CloudWatch to gain insights into client connections, traffic distribution, connection status and target health, helping you identify and troubleshoot network issues faster. Additionally, you can set up https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/telemetry-config-rules.html to automatically configure logging of both existing and newly created ALB resources, for your organization, specific accounts, or specific resources, ensuring consistent monitoring coverage without manual setup. With this CloudWatch Logs integration, you can track detailed access patterns using CloudWatch Logs Insights queries, create metric filters for monitoring and alarming, and review traffic patterns in real time using Live Tail. ALB logs can be configured through the integrations tab of your application load balancer in AWS Management Console, AWS CLI, or SDKs. You can also configure delivery of ALB logs to Amazon Data Firehose or Amazon S3 with support for Apache Parquet format. ALB logs delivery to CloudWatch is available in all AWS Commercial and GovCloud regions where Application Load Balancer and CloudWatch are available. ALB logs are charged as vended logs when delivered to CloudWatch Logs and Data Firehose, while delivery to Amazon S3 is free (Parquet conversion is charged at $0.035/GB - N. Virginia). To learn more about configuring ALB logs in CloudWatch Logs, https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-logs.html. For pricing information, see https://aws.amazon.com/cloudwatch/pricing/
aws.amazon.com
July 24, 2026 at 2:05 AM
AWS Application Load Balancer now supports Health Check Logs

AWS Application Load Balancers (ALB) now supports Health Check Logs that allows you to send detailed target health check log data directly to your designated Amazon S3 bucket. This optional feature c...

#AWS #AmazonElasticLoadBalancing
AWS Application Load Balancer now supports Health Check Logs
AWS Application Load Balancers (ALB) now supports Health Check Logs that allows you to send detailed target health check log data directly to your designated Amazon S3 bucket. This optional feature captures comprehensive target health check status, timestamp, target identification data, and failure reasons. Health Check Logs provide complete visibility into target health status with precise failure diagnostics, enabling faster troubleshooting without contacting AWS Support. You can analyze target’s health patterns over time, determine exactly why instances were marked unhealthy, and significantly reduce mean time to resolution for target health investigations. Logs are automatically delivered to your S3 bucket every 5 minutes with no additional charges beyond standard S3 storage costs. This feature is available in all AWS Commercial Regions, AWS GovCloud (US) Regions and AWS China Regions where Application Load Balancer is offered. You can enable Health Check Logs through the AWS Management Console, AWS CLI, or programmatically using the AWS SDK. Learn more about Health Check Logs for ALBs in the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-monitoring.html.
aws.amazon.com
November 21, 2025 at 9:05 PM
AWS Application Load Balancer launches Target Optimizer

Application Load Balancer (ALB) now offers Target Optimizer, a new feature that allows you to enforce a maximum number of concurrent requests on a target.

With Target Optimizer, you can fine-tune you...

#AWS #AmazonElasticLoadBalancing
AWS Application Load Balancer launches Target Optimizer
Application Load Balancer (ALB) now offers Target Optimizer, a new feature that allows you to enforce a maximum number of concurrent requests on a target. With Target Optimizer, you can fine-tune your application stack so that targets receive only the number of requests they can process, achieving higher request success rate, more target utilization, and lower latency. This is particularly useful for compute-intensive workloads. For example, if you have applications that perform complex data processing or inference, you can configure each target to receive as few as one request at a time, ensuring the number of concurrent requests is in line with the target's processing capabilities. You can enable this feature by creating a new target group with a target control port. Once enabled, the feature works with the help of an agent provided by AWS that you run on your targets that tracks request concurrency. For deployments that include multiple target groups per ALB, you have the flexibility to configure this capability for each target group individually. You can enable Target Optimizer through the AWS Management Console, AWS CLI, AWS SDKs, and AWS APIs. ALB Target Optimizer is available in all AWS Commercial Regions, AWS GovCloud (US) Regions, and AWS China Regions. Traffic to target groups that enable Target Optimizer generates more LCU usage than regular target groups. For more information, see the https://aws.amazon.com/elasticloadbalancing/pricing/?nc=sn&loc=3, https://aws.amazon.com/blogs/networking-and-content-delivery/drive-application-performance-with-application-load-balancer-target-optimizer/, and ALB https://docs.aws.amazon.com/elasticloadbalancing/latest/application/target-group-register-targets.html#register-targets-target-optimizer.
aws.amazon.com
November 21, 2025 at 12:05 AM
AWS Network Load Balancer simplifies deployments with support for Weighted Target Groups

Network Load Balancer now supports weighted target groups, allowing you to distribute traffic across multiple target groups with configurable weights for a...

#AWS #AwsGovcloudUs #AmazonElasticLoadBalancing
AWS Network Load Balancer simplifies deployments with support for Weighted Target Groups
Network Load Balancer now supports weighted target groups, allowing you to distribute traffic across multiple target groups with configurable weights for advanced deployment strategies. Weighted target groups enables key use cases like Blue-Green and Canary Deployments, Application Migration, and A/B Testing by allowing you to register multiple target groups with configurable weights ranging from 0 to 999, providing precise control over traffic distribution. Blue-Green and Canary Deployments allow you to gradually shift traffic between application versions, minimizing downtime during upgrades and patches; Application Migration enables seamless transitions from legacy stacks to new stacks without disrupting production traffic; and A/B Testing facilitates splitting incoming traffic across experimental environments. All target group types are supported, including instance, IP address, and Application Load Balancer (ALB) targets. Weighted Target Groups routing is available for all existing and new Network Load Balancers across AWS commercial and AWS GovCloud (US) regions at no additional charge. Standard Network Load Balancer Capacity Unit (LCU) pricing applies. To learn more, please refer to https://aws.amazon.com/blogs/networking-and-content-delivery/network-load-balancers-now-support-weighted-target-groups/, and the https://docs.aws.amazon.com/elasticloadbalancing/latest/network/listener-update-rules.html. 
aws.amazon.com
November 19, 2025 at 11:05 PM
AWS Network Load Balancer now supports QUIC protocol in passthrough mode

AWS Network Load Balancer (NLB) now supports QUIC protocol in passthrough mode, enabling low-latency forwarding of QUIC traffic while preserving session stickiness through ...

#AWS #AmazonElasticLoadBalancing #AwsGovcloudUs
AWS Network Load Balancer now supports QUIC protocol in passthrough mode
AWS Network Load Balancer (NLB) now supports QUIC protocol in passthrough mode, enabling low-latency forwarding of QUIC traffic while preserving session stickiness through QUIC Connection ID. This enhancement helps customers maintain consistent connections for mobile applications, even when client IP addresses change during network roaming. With QUIC support, customers can reduce application latency by up to 30% through fewer packet round trips and ensure seamless user experiences across varying network conditions. This is especially useful for mobile applications that require users to move between cellular towers or switch from WiFi to cellular networks, without losing connection state. You can enable QUIC support on your existing or new Network Load Balancers through the AWS Management Console, CLI, or APIs. Once enabled, NLB forwards QUIC traffic to targets by using the QUIC Connection ID to maintain session stickiness even when a client roams. QUIC support is available at no additional charge in all AWS commercial and AWS GovCloud (US) regions. QUIC traffic is metered within existing UDP Load Balancer Capacity Unit (LCU) entitlements. To learn more, visit this https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-quic-protocol-support-for-network-load-balancer-accelerating-mobile-first-applications/ and https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-listener.html#add-listener. 
aws.amazon.com
November 13, 2025 at 11:05 PM
Amazon EBS now supports Volume Clones for instant volume copies

Today, Amazon Web Services (AWS) announces the general availability of Volume Clones for Amazon Elastic Block Store (Amazon EBS), our high-performance block storage service. This ne...

#AWS #AmazonElasticLoadBalancing #AwsGovcloudUs
Amazon EBS now supports Volume Clones for instant volume copies
Today, Amazon Web Services (AWS) announces the general availability of Volume Clones for Amazon Elastic Block Store (Amazon EBS), our high-performance block storage service. This new capability allows you to instantly create and access point-in-time copies of EBS volumes within the same Availability Zone (AZ), accelerating software development workflows and enhancing operational agility. Customers use Amazon EBS volumes as durable block storage attached to Amazon EC2 instances. With Amazon EBS Volume Clones, you can instantly create copies of volumes and access the copied volumes with single-digit millisecond latency. Amazon EBS Volume Clones enables rapid creation of test and development environments from production volumes, eliminating manual copy workflows. Additionally, Volume Clones integrates with the Amazon EBS Container Storage Interface (CSI) driver, simplifying storage management for containerized applications. Amazon EBS Volume Clones is available in all AWS Commercial Regions and AWS GovCloud (US) Regions. You can access Volume Clones through the AWS Console, AWS Command Line Interface (CLI), AWS SDKs, and AWS CloudFormation. This capability supports all EBS volume types and works for volume copies within the same account and AZ. For detailed pricing information, please visit the https://aws.amazon.com/ebs/pricing/. To explore how Volume Clones can accelerate your software development processes and improve operational efficiency, visit the https://docs.aws.amazon.com/ebs/latest/userguide/ebs-copying-volume.html.
aws.amazon.com
October 15, 2025 at 12:05 AM
Load Balancer Capacity Unit Reservation for Gateway Load Balancers

Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its...

#AWS #AmazonElasticLoadBalancing
Load Balancer Capacity Unit Reservation for Gateway Load Balancers
Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern. Gateway Load Balancer helps you deploy, scale, and manage third-party virtual appliances. With this feature, you can reserve a guaranteed capacity for anticipated traffic surge. The LCU reservation is ideal for scenarios such as onboarding and migrating new workload to your GWLB gated services without the need to wait for organic scaling, or maintaining a minimum bandwidth capacity for your firewall applications to meet specific SLA or compliance requirements. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API. The feature is available for GWLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) AWS Regions. This feature is not supported on Gateway Load Balancer Endpoint (GWLBe). To learn more, please refer to the https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/capacity-unit-reservation.html.
aws.amazon.com
April 10, 2025 at 11:05 PM
Application Load Balancer announces integration with Amazon VPC IPAM

AWS Application Load Balancer (ALB) now allows customers to provide a pool of public IPv4 addresses for IP address assignment to load balancer nodes. Customers can configure a public IP Addre...

#AWS #AmazonElasticLoadBalancing
Application Load Balancer announces integration with Amazon VPC IPAM
AWS Application Load Balancer (ALB) now allows customers to provide a pool of public IPv4 addresses for IP address assignment to load balancer nodes. Customers can configure a public IP Address Manager (IPAM) pool that can consist of either Bring Your Own IP addresses (BYOIPs) that is customer owned or a contiguous IPv4 address block provided by Amazon. With this feature, customers can optimize public IPv4 cost by using BYOIP in public IPAM pools. Customers can also simplify their enterprise allowlisting and operations, by using Amazon-provided contiguous IPv4 blocks in public IPAM pools. The ALB's IP addresses are sourced from the IPAM pool and automatically switch to AWS managed IP addresses when the public IPAM pool is depleted. This intelligent switching maximizes service availability during scaling events. The feature is available in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ and https://aws.amazon.com/govcloud-us/Regions where Amazon VPC IP Address Manager (IPAM) is available. To learn more, please refer to the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html#ip-pools.  
aws.amazon.com
March 7, 2025 at 10:05 PM
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...

#AWS #AwsGovcloudUs #AmazonElasticLoadBalancing
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. 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 https://docs.aws.amazon.com/elasticloadbalancing/latest/network/availability-zones.html and https://aws.amazon.com/blogs/networking-and-content-delivery/exploring-new-subnet-management-capabilities-of-network-load-balancer/ for prescriptive guidance on how to use this capability in a safe manner. This capability is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ and the AWS GovCloud (US) Regions.
aws.amazon.com
February 13, 2025 at 10:05 PM
Cross-zone enabled Application Load Balancer now supports zonal shift and zonal autoshift

AWS Application Load Balancer (ALB) now supports Amazon Application Recovery Controller’s zonal shift and zonal autoshift features on load balancers that are enabled ac...

#AWS #AmazonElasticLoadBalancing
Cross-zone enabled Application Load Balancer now supports zonal shift and zonal autoshift
AWS Application Load Balancer (ALB) now supports Amazon Application Recovery Controller’s zonal shift and zonal autoshift features on load balancers that are enabled across zones. Zonal shift allows you to quickly shift traffic away from an impaired Availability Zone (AZ) and recover from events such as bad application deployment and gray failures. Zonal autoshift safely and automatically shifts your traffic away from an AZ when AWS identifies potential impact to it. Enabling cross-zone on ALBs is a popular configuration for customers that require an even distribution of traffic across application targets in multiple AZs. With this launch, customers can shift traffic away from an AZ in the event of a failure just like they are able to for cross-zone disabled load balancers. When zonal shift or autoshift is triggered, the ALB will block all traffic to targets in the AZ that is impacted and remove the zonal IP from DNS. You can configure this feature in two steps: First, enable configuration to allow zonal shift to act on your load balancer(s) using the ALB console or API. Second, trigger zonal shift or enable zonal autoshift for the chosen ALBs via Amazon Application Recovery Controller console or API. Zonal shift and zonal autoshift support on ALB is available in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, including the https://aws.amazon.com/govcloud-us/. To learn more, please refer to the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-integrations.html#zonal-shift.
aws.amazon.com
November 22, 2024 at 7:05 PM
AWS Application Load Balancer introduces header modification for enhanced traffic control and security

Application Load Balancer (ALB) now supports HTTP request and response header modification giving you greater controls to manage your applicat...

#AWS #AwsGovcloudUs #AmazonElasticLoadBalancing
AWS Application Load Balancer introduces header modification for enhanced traffic control and security
Application Load Balancer (ALB) now supports HTTP request and response header modification giving you greater controls to manage your application’s traffic and security posture without having to alter your application code. This feature introduces three key capabilities: renaming specific load balancer generated headers, inserting specific response headers, and disabling server response header. With header rename, you can now rename all ALB generated Transport Layer Security (TLS) headers that the load balancer adds to requests, which includes the six mTLS headers and two TLS headers (version and cipher). This capability enables seamless integration with existing applications that expect headers in a specific format, thereby minimizing changes to your backends while using TLS features on the ALB. With header insertion, you can insert custom headers related to Cross-Origin Resource Sharing (CORS) and critical security headers like HTTP Strict-Transport-Security (HSTS). Finally, the capability to disable the ALB generated “Server” header in responses reduces exposure of server-specific information, adding an extra layer of protection to your application. These response header modification features give you the ability to centrally enforce your organizations security posture at the load balancer instead of enforcement at individual applications, which can be prone to errors. You can configure Header Modification feature using AWS APIs, AWS CLI, or the AWS Management Console. This feature is available for ALBs in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, https://aws.amazon.com/govcloud-us/ and https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/#AWS_China_Regions*. To learn more, refer to the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html#alb-http-headers.  
aws.amazon.com
November 21, 2024 at 11:05 PM
Load Balancer Capacity Unit Reservation for Application and Network Load Balancers

Application Load Balancer (ALB) and Network Load Balancer (NLB) now support Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a min...

#AWS #AmazonElasticLoadBalancing #AwsGovcloudUs
Load Balancer Capacity Unit Reservation for Application and Network Load Balancers
Application Load Balancer (ALB) and Network Load Balancer (NLB) now support Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern. With this feature, you can prepare for anticipated traffic surges by reserving a guaranteed minimum capacity in advance, providing customers increased scale and availability during high-demand events. LCU Reservation is ideal for scenarios such as event ticket sales, new product launches, or release of popular content. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API. The feature is available for ALB in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, including the https://aws.amazon.com/govcloud-us/ and NLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm). To learn more, please refer to the https://docs.aws.amazon.com/elasticloadbalancing/latest/application/capacity-unit-reservation.html and https://docs.aws.amazon.com/elasticloadbalancing/latest/network/capacity-unit-reservation.html.
aws.amazon.com
November 21, 2024 at 1:06 AM
🆕 AWS ALB and NLB now support RFC 9151 compliant security policies for CNSA 1.0, ensuring secure TLS 1.2/1.3 communications per US NSA requirements, available in all regions at no extra cost. Update existing listeners or create new ones with compliant policies.

#AWS #AmazonElasticLoadBalancing
AWS Application and Network Load Balancers now support RFC 9151 compliant security policies
AWS Application Load Balancer (ALB) and Network Load Balancer (NLB) now support new TLS-based security policies that comply with RFC 9151 TLS server requirements for Commercial National Security Algorithm (CNSA) 1.0 suite requirements. These policies implement the cryptographic requirements defined by the US National Security Agency (NSA) for secure communications using TLS 1.2 and TLS 1.3 protocols. Customers who are required to meet CNSA 1.0 TLS security requirements can now use ALB and NLB with RFC 9151 compliant security policies. Broader interoperability policies are also supported, allowing you to implement CNSA by default while maintaining compatibility with non-CNSA clients during their transition to RFC 9151 compliance, minimizing service disruption. This feature is available for ALB and NLB in all AWS Commercial Regions, the AWS GovCloud (US) Regions, and the China region at no additional cost. To use this capability, update your existing ALB HTTPS listeners or NLB TLS listeners to a RFC 9151 compliant security policy, or select a compliant policy when creating new listeners through the AWS Management Console, CLI, API, or SDK. To learn more, visit the ALB User Guide and NLB User Guide documentation. Get started with Elastic Load Balancing.
aws.amazon.com
August 4, 2026 at 8:10 PM
🆕 Amazon CloudWatch Logs now supports Application Load Balancer logs for improved observability. Analyze and set up telemetry rules in CloudWatch, delivering logs to Firehose or S3. Available in all regions with ALB and CloudWatch. Pricing on…

#AWS #AmazonElasticLoadBalancing #AmazonCloudwatchLogs
Amazon CloudWatch Logs now supports Application Load Balancer logs
Amazon CloudWatch Logs now supports Application Load Balancer (ALB) logs as vended logs, improving observability and simplifying debugging for network traffic patterns. You can now analyze ALB access, connection and health check logs directly in CloudWatch to gain insights into client connections, traffic distribution, connection status and target health, helping you identify and troubleshoot network issues faster. Additionally, you can set up CloudWatch telemetry enablement rules to automatically configure logging of both existing and newly created ALB resources, for your organization, specific accounts, or specific resources, ensuring consistent monitoring coverage without manual setup. With this CloudWatch Logs integration, you can track detailed access patterns using CloudWatch Logs Insights queries, create metric filters for monitoring and alarming, and review traffic patterns in real time using Live Tail. ALB logs can be configured through the integrations tab of your application load balancer in AWS Management Console, AWS CLI, or SDKs. You can also configure delivery of ALB logs to Amazon Data Firehose or Amazon S3 with support for Apache Parquet format. ALB logs delivery to CloudWatch is available in all AWS Commercial and GovCloud regions where Application Load Balancer and CloudWatch are available. ALB logs are charged as vended logs when delivered to CloudWatch Logs and Data Firehose, while delivery to Amazon S3 is free (Parquet conversion is charged at $0.035/GB - N. Virginia). To learn more about configuring ALB logs in CloudWatch Logs, please visit our documentation. For pricing information, see CloudWatch pricing page.
aws.amazon.com
July 24, 2026 at 2:10 AM
🆕 AWS Network Load Balancer adds listener rules for custom traffic routing, allowing IPv4/IPv6 to route to same-family groups without translation, available in all commercial and GovCloud regions at no extra charge.

#AWS #AmazonElasticLoadBalancing
AWS Network Load Balancer now supports Listener Rules for custom traffic routing
Network Load Balancer (NLB) now supports listener rules allowing you to route connections to different target groups based on the source IP address type. With listener rules, a single dual-stack NLB sends IPv6 client traffic to IPv6 targets and IPv4 client traffic to IPv4 targets, preserving the original client IP address end to end for both address families. Previously, serving both IPv4 and IPv6 clients from one NLB meant accepting a tradeoff: either run two separate load balancers (one per IP version) and split clients with DNS, or send all traffic to one target group and lose the original client IP through protocol translation. Listener rules remove that tradeoff by enabling conditional routing at Layer 3, directing each connection to a same-family target group with no translation and no additional infrastructure. You can add listener rules to existing dual-stack NLBs without recreating them. Rules are supported on TCP, UDP, TCP_UDP, and TLS listeners and work alongside existing NLB features including connection draining, target group stickiness, cross-zone load balancing, weighted target groups, and client IP preservation. Listener rules for Network Load Balancer are available in all AWS commercial Regions and the AWS GovCloud (US) Regions at no additional charge. Standard NLB pricing for load balancer hours and LCUs applies. To get started, see this AWS blog, and the Network Load Balancer User Guide.
aws.amazon.com
July 22, 2026 at 8:10 PM