Custom Layer 4 Load Balancer

What are my best options for deploying a load balancer on AWS with the following requirments:

Add auto scaling that will start my own EC2 instances.
Deploy 3rd party SW on the load balancer.
Have a readable shared memory (can be S3).

Found the tutorial "Create an External Load Balancer" about Kubernetes but not sure about it.

EDIT:

deploy 3rd party [software] on the load balancer" -- to do what: Want to start new instances with parameters and for routing rules to the instances that were created with the auto scaling.

how is "readable shared memory" used, and for what purpose? shared memory between the load balancer and the instances. I can do it with sockets.

Why is the balancer layer 4 as opposed to a different layer? Need TCP parametrs, layer 7 info can also be useful

Where is TLS handled? I havn't thought about this.

Historically, F5's Application Delivery Controller has been the enterprise-grade industry solution for doing this. With this solution you can:

• Use iRules LX to communicate with other software to auto-scale on an as-needed basis

• Load balance at Layer 4 (to achieve better throughput/acceleration) or Layer 7

• Share memory between Virtual Servers (there may be a better way using iRules LX instead of just iRules)

• Bridge or offload/terminate TLS on the Load Balancer

• Have vendor support and consulting if needed

• Do all of this in Amazon's cloud (or anyone else's; you can also run it in-house)

• Scale to millions more connections than Kubernetes, nginx, or any other load balancer solution that doesn't use a microkernel is capable of.

StackExchange DevOps Q#3006, answer score: 2