Exploring new subnet management capabilities of Network Load Balancer
Networking & Content Delivery Blog
AWS has enhanced Network Load Balancer (NLB) subnet management capabilities, allowing organizations greater flexibility in configuring load balancers across Availability Zones.
- NLBs can now remove and modify subnet configurations after deployment
- Previously, NLBs were restricted to only adding subnets in new Availability Zones
- The new SetSubnets API enables relocating load balancers within Amazon VPC
- Subnet removal can impact active connections and requires careful planning
- Recommended best practices include: • Identifying active IP addresses • Adjusting load balancer settings • Preparing the Availability Zone for removal • Using zonal shift for smoother transitions
This enhancement provides more control over network architecture and brings NLB subnet management in line with Application Load Balancer capabilities.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Feb 13
2025
2025
AWS Network Load Balancer now supports removing availability zones
Oct 11
2024
2024
Cross-zone enabled Network Load Balancer now supports zonal shift and zonal autoshift
Nov 19
2025
2025
Network Load Balancers now support Weighted Target Groups
Nov 19
2025
2025
AWS Network Load Balancer simplifies deployments with support for Weighted Target Groups
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.