What are the supported TLS versions for Classic Load Balancer?

NLBs are suitable for TCP-based applications, while Application Load Balancers (ALBs) are better suited for HTTP/HTTPS-based applications.

Use the AWS Management Console's migration wizard to create a new NLB with a configuration equivalent to your existing CLB. The wizard will handle the migration process for you.

Test the new NLB with your application to ensure it's functioning as expected.

Once you've verified the new NLB is working correctly, you can decommission the old CLB

https://repost.aws/knowledge-center/migrate-classic-load-balancer https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.html

To be sure, your traffic is not exclusively HTTP or HTTPS, but you also need some non-HTTP traffic to run through the same load balancer? As the other reply correctly advises, ALB exclusively supports HTTP and HTTPS, but you really should run HTTP(S) traffic through an ALB and not a CLB or NLB that lack many of the features you need for properly securing the HTTP(S) part of your application.

If you need non-HTTP TCP traffic with or without TLS, the best option would be to use an NLB for that traffic and a separate ALB for HTTP(S). You could configure proper listener rules, path-based routing, request logging, and WAFv2 protections on the ALB, all of which is not possible on an NLB, and the NLB would only process the non-HTTP(S) traffic to which those features don't apply anyway.