
This script helps identify any resources provisioned in EC2-Classic across all regions in an account as well as each region's enablement status for EC2-Classic. That being said, to double check, I would recommend using the EC2 Classic Resource finder script- to find any EC2 Classic Resources in your account. As you have already mentioned that your ELB is in VPC, there is no need to migrate and it will not be affected. If they are in EC2-Classic you need to manually migrate it to VPC. By default, if the load balancer cannot get a response from AWS WAF. First thing is to identify if the Classic Load Balancers are in EC2-Classic or in a VPC. In contrast, think about the NLB as a way to route traffic to a fleet of virtual. That Elastic load balancer is not retiring however EC2-Classic Networking is Retiring and you are required to migrate all the affected resources as mentioned in the articleĬlassic Load Balancers can be in EC2-Classic or in a VPC.
