Home > Storage > ObjectScale and ECS > Product Documentation > ECS with F5 Deployment Reference Guide > Scope
This whitepaper is meant to be a reference guide for deploying F5 with ECS. An external load balancer (traffic manager) is highly recommended with ECS for applications that do not proactively monitor ECS node availability or natively manage traffic load to ECS nodes. Directing application traffic to ECS nodes using local DNS queries, as opposed to a traffic manager, can lead to failed connection attempts to unavailable nodes and unevenly distributed application load on ECS.
The ECS HDFS client, CAS SDK and ECS S3 API extensions are outside of the scope of this paper. The ECS HDFS client, which is required for Hadoop connectivity to ECS, handles load balancing natively.
Similarly, the Centera Software Development Kit for CAS access to ECS has a built-in load balancer. The ECS S3 API also has extensions leveraged by certain ECS S3 client SDKs which allow for balancing load to ECS at the application level.
Dell EMC takes no responsibility for customer load balancing configurations. All customer networks are unique, with their own requirements. It’s extremely important for customers to configure their load balancers according to their own circumstance. We only provide this paper as a guide. F5 or a qualified network administrator should be consulted before making any changes to your current load balancer configuration.