Navigate
ScaleArc Customer Support
  • Login to Ignite Global Support
or
Contact Us
  • Get in touch

    Send us an email

  • Submit Feedback

    Feedback and suggestions submitted by customers like you

  • Knowledgebase Read help articles
  • Feedback Custom suggestions
  • Downloads Browse our downloads
  • Contact Us We are here to help
  • Portal
  • Knowledgebase
  • ScaleArc Registered User
  • AWS ELB with Active/Active and Active/Standby ScaleArc
Subscribe Download PDF

AWS ELB with Active/Active and Active/Standby ScaleArc

Mark Lee
2015-08-17
0 Comments
in ScaleArc Registered User

AWS ELB with Active/Active and Active/Standby ScaleArc

Release Document Status DB Platform Categories
3.11 or higher INFO All Cluster Settings

 

QUESTION

How does ScaleArc work with AWS ELB?

 

ANSWER

"Elastic Load Balancing automatically distributes incoming application traffic across multiple Amazon EC2 instance in the cloud.  It enables you to achieve greater levels of fault tolerance in your applications, seamlessly providing the required amount of load balancing capacity needed to distribute application traffic." 

In configuring Active/Active or Active/Passive ScaleArc on AWS, it requires an ELB to be configured to load balance the traffic between the two ScaleArc systems.  

To configure the ELB: 

1.  Create the AWS ELB - EC2 > Load Balancers > Create Load Balancer

2.  Name the load balancer, choose the VPC if necessary, add the TCP listing port (3306,1443,1521, etc.), select the Availability zone subnets to be load balanced (these should be the same zones as the ScaleArc instances). Add to the appropriate Security Group. Suppose if we have MSSQL Cluster running on 1443 Port then 3306 TCP port would be replaced by 1443.

3.  Configure the ELB health check.  This health check is executed on the instance that are being load balanced.  It will check the protocol and port is open and available to determine what the status of the instance is.  Be careful, you can only have 1 health check per ELB.  If you have multiple ScaleArc clusters, Sepearte ELB would be recommended for each Cluster.  Ping Port configured should be the InBound IP Address of the Cluster corresponding to which ELB listens.

4.  Add your instances to be load balanced to the ELB. 


As you can see, right now ScaleArcTest-3 is InSerivce and now serving traffic to Cluster mentioned below. In case ScaleArcTest-3 goes down and ELB unable to communicate with ScaleArcTest-2 as per health check intervals, ScaleArcTest-1 will take its place and further traffic will be served by ScaleArcTest-2.

Configuring ScaleArc Active/Passive HA: 

1.  SSH to each of the ScaleArc nodes.  

2.  Setup HA: How-to-configure-ha-in-scalearc-v-3-11-0-2-or-later-in-cloud-environment-aws-azure

 


 


If you are experiencing issues with ScaleArc or with any of it's features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at support@scalearc.com.

Copyright ©2014 ScaleArc, Inc. All rights reserved. Contact Support |  Contact ScaleArc |  Feedback

2901 Tasman Drive Santa Clara, CA 95054 | Email:  support@scalearc.com

 

 

Permalink: https://support.scalearc.com/kb/articles/2230
  • Tags
  • aws
  • ELB

Rate the quality of this page

This page was helpful :) :( This page was not helpful

3 of 10 people found this page helpful


Quick Jump
  • ScaleArc Customer Support
  • Knowledgebase
  • Downloads
  • Feedback
  • Contact Us
Top
Helpdesk software provided by DeskPRO