# Automatically removing Private IP's in Route53 private hosted Zone

**URL:** <https://discuss.elastic.co/t/automatically-removing-private-ips-in-route53-private-hosted-zone/64771>\
**Category:** Elasticsearch\
**Created:** [November 2, 2016, 9:05pm UTC](https://discuss.elastic.co/t/automatically-removing-private-ips-in-route53-private-hosted-zone/64771 "2016-11-02T21:05:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![santsaha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/santsaha/32/6010_2.png) [@santsaha](https://discuss.elastic.co/u/santsaha)\
**Post date:** [November 2, 2016, 9:05pm UTC](https://discuss.elastic.co/t/automatically-removing-private-ips-in-route53-private-hosted-zone/64771/1 "2016-11-02T21:05:54Z")

</div>

I have a self-deployed elasticsearch cluster on AWS, where the instances are autoscaled and behind a private VPC and do not have public ip assigned to them. I have a custom domain and recordset in Route 53 as [elasticsearch.pers-z.infra.abc-appanalytics.com](http://elasticsearch.pers-z.infra.abc-appanalytics.com) : A 10.0.7.142 10.0.8.43 10.0.9.74

Now suppose one of the instances fail, how do i remove that entry from the recordset. When i say fail, it could be elasticsearch not responding on port 9200 Or the instance itself shuts down.

What are the options for me in this context ?

PS: Route53 Health Checks do not support private-ips

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:07pm UTC](https://discuss.elastic.co/t/automatically-removing-private-ips-in-route53-private-hosted-zone/64771/2 "2017-07-05T22:07:11Z")

</div>

Closed on July 5, 2017, 10:07pm UTC