Specific details on how to make ambari-server HA

[#1]

Background

I'm currently investigating how to make Ambari Server run in multiple regions within AWS. I realize that Ambari does not provide this feature out of the box, and so was thinking that I could use something like the following:

1. Setup 2 EC2 instances as Ambari Servers (in 2 different regions in AWS)
2. Assign a VIP (Virtual IP) and designate 1 of the above servers as the initial owner
3. Use keepalived to failover VIP between 2 EC2 instances that both have Ambari Server
4. Use DynamoDB to externalize the PostgresSQL DB
5. script/command that keepalived would trigger to start up the secondary Ambari Server and stop the primary

My questions

• Does this seem feasible?
• What about the hostname/IP info assigned to the 2 Ambari Servers?
• What about any filesystem details associated to Ambari Server, does this need to be shared across nodes too?

References

• Chapter 5. Moving the Ambari Server
• How to setup High Availability for Ambari server?

[#2]

• Does this seem feasible?
  • No since I would default to what the community provides in terms of HA solutions. Tons of gotchas
• What about the hostname/IP info assigned to the 2 Ambari Servers?
  • What is the question here?
• What about any filesystem details associated to Ambari Server, does this need to be shared across nodes too?
  • I am not sure how AMS collector would be shared accross the servers