Home > aws, domain, ec2 > Pointing godaddy domain to an aws ec2 instance

Pointing godaddy domain to an aws ec2 instance

You just bought a domain and don’t know how to point it to your server, just follow these easy steps to make it possible:

First we need to set up AWS to provide an IP address for your DNS settings.

  1. On EC2 Management console you will have a vertical menu on the left hand side.
  2. Under “NETWORK & SECURITY” group click on “Elastic IPs”.
  3. On the top menu you will see a blue button “Allocate New Address” click on it.
  4. Just be sure “EIP used in” is set to “EC2” then click “Yes, Allocate”.
  5. A new IP address will be created on the table, select it by clicking on the empty square by the left of the name.
  6. Now click on “Associate Address” on the pop-up click on instance and select the instance you would like to associate to this IP.
  7. Finally click “Associate” and that’s it. For now to access via SSH, FTP, etc. you will need to use the new elastic IP.

On the godaddy side we will set up the points to address with the new elastic ip.

  1. Login into your godaddy account.
  2. Under the upper menu click “Domains” and then click “Manage my Domains”.
  3. Select the domain you would like to change by clicking the link to the domain on the table under “Domain Name” column.
  4. In Domain Details there are three tabs, you should click on “DNS Zone File”.
  5. Under A(Host) , click on “Edit Record” at the end in “Actions” column.
  6. Now change the value on the field “Points to” with the elastic ip of your amazon ec2 instance.
Categories: aws, domain, ec2 Tags: , , ,
  1. January 14th, 2015 at 02:55 | #1

    thank you

  2. February 14th, 2015 at 02:30 | #2

    It took a little while to update. But it worked!!! Thanks :)

  3. Charles
    May 17th, 2015 at 22:22 | #3

    If you use VPC instance, the procedure is largely the same except you must also add the internet gateway to the routing table, the all important second row is not there by default

    Destination Target local igw-xxxxxxxx

    Details can be found here:

  4. Alind
    June 7th, 2015 at 12:08 | #4

    Hey !
    Looks great… other articles were suggesting to go for paid DNS.

  5. July 3rd, 2015 at 13:56 | #5

    Thanks :))

  6. July 5th, 2015 at 22:42 | #6

    Thank you!

  7. September 6th, 2015 at 05:30 | #7

    Thanks you!! It has been super useful

  8. shiva palem
    September 18th, 2015 at 01:49 | #8

    We are running a mail server in EC2 instance with elastic IP 54.169.X.X. We had registered our domain in godaddy and configuration for A and MX records done and working fine. Now how to setup PTR record?
    Please suggest me.

  9. September 18th, 2015 at 02:18 | #9

    Hey ur welcome all ! Shiva I think this can perhaps solve your problem http://serverfault.com/questions/234815/how-to-add-a-reverse-ptr-record-on-amazon-route-53

  10. E.Alen
    February 26th, 2016 at 12:57 | #10

    HI there,

    THank you for the info.

    We have done all the steps and successively pointed the domain to the AWS, however we have the Apache test page coming up instead of the WP site… any idea how to go around this? Thx

  11. March 16th, 2016 at 02:57 | #11


    Sorry for the late reply, for me that sounds more like an apache configuration issue pointing to the wrong directory or something like that. I would need more details to help you better.

  12. December 24th, 2016 at 19:15 | #12

    Awesome, Thank you very much! Worked

  13. November 9th, 2017 at 06:33 | #13

    thanks for sharing this amazing post.

  1. September 27th, 2015 at 13:47 | #1