Using an AWS Application load Balancer between an on-prem Autosys Scheduler and Cloud based agent
search cancel

Using an AWS Application load Balancer between an on-prem Autosys Scheduler and Cloud based agent

book

Article ID: 369228

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Currently, the Autosys Agent is running in an AWS EKS/EC2 instance that is using a Network Load Balancer to communicate with the Autosys Infrastructure on-premise. 

Network Load Balancers are pretty expensive.
Could the communication between the Autosys Infrastructure on-prem communicate via an Application Load Balancer to the Autosys Agent in AWS EKS/EC2?

Do you have an example on how that would be done?

Environment

AWS
Cloud
Autosys 12.x

Cause

Product Limitation

Resolution

There currently is no documentation on using an Application Load balancer.
As such this is not supported.


Based on the below documentation, there are two reasons this is not supported.
https://aws.amazon.com/compare/the-difference-between-the-difference-between-application-network-and-gateway-load-balancing/

1) ALB only supports the below protocols.
Supports HTTP, HTTPS, and gRPC protocols.

Note:
the agent and scheduler communication is TCP

2) ALB is not designed for high performance and low latency which is required by the Autosys application only the NLB is:
An NLB is best for high-performance, low-latency, and scalable network-level balancing.
Applications that distribute traffic on the transport layer use NLBs, especially considering its reliability.
Gaming systems, media streaming services, and major IoT systems use NLBs.