So I just bought a domain with godaddy www.abc.com (example)
I have then uploaded my flask back end and successfully deployed it to elastic beanstalk.
The elastic beanstalk has given a url as elastic-region.com.
However this url is HTTP, therefore
I have then created a certificate for www.abc.com
Now the problem is I cannot link my godaddy to my elastic bean server.
I have set up the CNAME where Name = www and Value = elastic-region.com.
As well as the certificate as name = xyz value = yzx
After all the configuration I still am not able to connect it to the elastic bean. When I enter the url www.abc.com it redirects be back to godaddy account page
I would suggest moving your DNS to route53 DNS service. You can do this by adding a hosted zone in route53 and changing your name servers in GoDaddy. In Route53 you can directly alias towards your elastic beanstalk environment on A / AAAA records.
If you want to continue hosting your DNS at GoDaddy; I would suggest using tools like https://mxtoolbox.com/ to verify if your DNS is set correctly. The method you described in your post would be sufficient to CNAME towards your EB environment.
AWS resource to create an alias towards Elastic beanstalk:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-beanstalk-environment.html#routing-to-beanstalk-environment-create-alias-procedure
Some resources to help you change nameservers:
https://www.godaddy.com/help/change-nameservers-for-my-domains-664
https://virtualizationreview.com/articles/2020/07/14/migrating-dns-services-aws.aspx
you can also move your whole domain to AWS;
https://blog.shikisoft.com/transferring-domain-registrations-from-godaddy-to-amazon-route-53/
Related
I have a url that points to a s3 hosted angular application. at example.com
That works fine and its running under https
now I want to take my django powered API and running on elastic beanstalk and make it work as a subdomain called api of my example.com website.
So to get to the backend they type api.example.com
the domain is registerd with godaddy.
There I have CNAMES for www.example.com and example.com
now for the subdomain I can't do a A record because I don't have the IP address of the elastic beanstalk instance.
Cant do the CNAME way as it was giving me an error. When I put the elasticbeanstalk url in the points to field
http://example-env.eba-thingy.somereigion.elasticbeanstalk.com
I get an error that says: Enter either # or a valid host name such as: "subdomain.domain.tld"
CNAMES A Names Subdomains its all so foreign. What do I need to do to handle this correctly?
I also tried the subdomains form with no success
I have created a spring boot application and deployed it to AWS elastic beanstalk. I could easily access it with the environment URL provided by AWS. Then I implemented SSL in my app. I tested it locally and it was responding on https request but not on http request. Then I got a domain from godaddy and I linked it to my AWS elastic beanstalk app by following AWS route 53 documentation carefully. How can I access my spring boot app now? None of these CNAME, Alias or any other record set URL is working
These are the record sets I have created and linked to my elastic beanstalk app
You should only need an "A" record type here that directs www..com to your EB url and then one name server "NS" record where you'll enter the detail retrieved from your GoDaddy account in "My Domains" > "Select Domain" > "Domain Settings".
One record for NS and the "value" portion will be the 4 name servers you found in GoDaddy.
I have running app in elastickbeanstalk on domain:
secret-development.eu-central-1.elasticbeanstalk.com
And I would like to route my domain into this app.
I created CNAME www to secret-development.eu-central-1.elasticbeanstalk.com
But it is not working.
What is wrong?
I created CNAME www to secret-development.eu-central-1.elasticbeanstalk.com
Unfortunately, you can't create working www CNAME record to the default EB domain. The reason is that this is AWS owned domain and you have no control over it.
If you don't want to use AWS provided domain for you EB environment, you have to create/buy your own domain, e.g. mydomain.com. This can be done in Route53, but can also use any other domain seller.
How to use Route53 to setup a custom domain for EB is explained in the following AWS documentation:
Creating an Amazon Route 53 record that routes traffic to your Elastic Beanstalk environment
If you have your own domain (e.g., mydomain.com), then you can also setup a subdomain (www.mydomain.com) for it and point it to EB environment.
Having your own domain will also enable you to setup https to your EB environment.
I'm having issues to point a domain to a new server.
Currently our application is hosted in Google Clould.
We have a domain that is pointed to the public IP address of the Google Cloud instance and there is no other Google Cloud name servers attached to it. In our domain manager, we only have something like this:
domain.com A <google-cloud-ip-address>
We're moving this app to an AWS Beanstalk environment and these are the steps we did:
Setup the app in an AWS Beanstalk Environment
Create a Hosted Zone in Route 53
Add an A Record Set with an Alias pointing to the Beanstalk application
This is what we have in Route 53 now:
domain.com A ALIAS application-domain.beanstalk.com
domain.com NS nameserver1.aws.com, nameserverN.aws.com ...
domain.com SOA ...
Route 53 only gives me name servers, but the domain is currently pointed to an IP address, how should I proceed in this case to point the domain to Route 53, since I don't have any public IP addresses to replace it on my domain manager?
What I tried to do is: remove the current IP record from the domain manager and add all the AWS name servers but that didn't work.
Anyone had this experience and could share something with me?
Thanks.
I have setup a Wordpress on Lightsail, and have created a static IP which I can access WP ok.
I have migrated my .co.uk domain across to Route53 from another provider and am trying to point blog.example.co.uk to my Lightsail instance.
In Lightsail I have setup a DNS record like this:
A example.co.uk 12.34.56.78
A blog.example.co.uk 12.34.56.78
It then lists these DNS servers in Lightsail:
ns-849.awsdns-42.net
ns-1643.awsdns-13.co.uk
ns-341.awsdns-42.com
ns-1516.awsdns-61.org
I've taken those DNS servers and set on the root of my domain in Route 53 under Domains > Registered Domains
I am not sure if that was the correct thing to do, as I will have other subdomains eventually that will point elsewhere, should the Lightsail DNS servers be added at that level? If not, what do I set them back to be?
I have also created a Route53 Hosted Zone, and have created an "A" entry that links blog.example.co.uk to 12.34.56.78, is that required?
As mentioned in the comments, I was facing the same challenge.
What ended up working for me was simply creating an Alias Record (A) for my subdomain, subdomain.example.com, that points to the static IP of my Lightsail instance.
I did not add Lightsail's DNS servers anywhere on Route53.
I made sure that the NS entries for my root domain – example.com – pointed to the Name servers entries on my registered domain in Route53.
You can find the name servers associated with your Route53 registered domain by going to Registered domains > mydomain.com; they're located on the upper-right corner.