I really donβt understand why your client will not use Elastic IP or Elastic Load Balancer here?
With Elastic IP, you can save a consistent name in your public DNS record, and then manually or programmatically update the EC2 instance associated with this EIP when necessary using the elb API scripts.
By balancing the elastic load, you can easily connect only one active node to the ELB, and then programmatically remove / add nodes and update Route53 accordingly.
You can use the internal machine API to get the values ββ(Instance ID, etc.) for these calls in boostrap script.
source share