By using AWS re:Post, you agree to the Terms of Use
/Route53 - Manual Update of IP address for A record of EBS Environment/

Route53 - Manual Update of IP address for A record of EBS Environment



I have a hosted zone in Route53. Under this hosted zone, I have two records.

  1. A
  2. CNAME

For the above 2 records.

Record 1:

  • is just an example, we have to update this IP address very regularly, as we are using the IP address of the EBS environment

Record 2:

  • We link the EBS environment URL directly to it

My question is, because the IP address of the EBS environment changes regularly on AWS side, we have to manually update the the value for the A record shown above. Is there a recommended way to do that, so that we can access the website via both and ?

<Edited on 15 June>

Just wondering, would it be possible for AWS to assign an elastic IP to the EBS environment, so that we don't need to update the IP value for the A record every now and then?

Thank you.

1 Answers


I understand you want to access your website from both and The issue you facing CX is due to CNAME limitation, where CNAME cannot co-exist with another record. To solve this, when DNS is Hosted in R53, we normally advised CX to use A (alias) in root/parent domain. Below will be the necessary steps needed to take when creating an alias[1]:

  • Sign in to the AWS Management Console and open the Route 53 console
  • In the navigation pane, choose Hosted zones
  • Choose the name of the hosted zone that you want to use to route traffic to your Elastic Beanstalk environment
  • Choose Create record
  • Specify the following values
  • Choose Create records


answered 21 days ago
  • Hi Lwazi,

    Thank you for your reply.

    Currently, my CNAME record is working fine. However for my A record value, we have to keep checking up the IP address of the EBS environment, and updating it accordingly. Also, based on the link that you provided, for EBS environment URL that does not include the region, we can only use CNAME to route the traffic via the subdomain, which we have already done so (refer. Record 1). In that case, how should we go about if we want to route traffic to the root domain as well.

    Thank you.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions