I'm trying to configure cloudflare dns to point to an elasticbeanstalk application.
Most of the tutorials are using route53 but I'm trying to see how it'll work with cloudflare
I bought a domain: myapp.com and it's already pointing to the cloudflare nameservers.
On the cloudflare there's NO dns record right now.
I can access the eb app by url :
myapp-env.eba-uistqmhg.ap-southeast-1.elasticbeanstalk.com
so how do i point myapp.com to the eb app ?
Do I simply add a CNAME that points to the eb url or I need to use the eb ipv4 instance?
You can add a CNAME for myapp-env.eba-uistqmhg.ap-southeast-1.elasticbeanstalk.com. After making the change, it might take few minutes for the DNS to propogate.
Related
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/
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 have an express, node, mongo app running on elasticbeanstalk perfectly. the url value of this elasticbeanstalk is something like example.eu-west-1.elasticbeanstalk.com.
Now I also have customer domain, lets say example.com which is registered on aws route53 and in the hostedzone I have soa and ns record.
I wanted to load elasticbeanstalk when user visit my custom domain example.com. I have tried following aws docs
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-beanstalk-environment.html with no luck.
I have created A record with alias that targets elasticbeanstalk environment url value. I have tried creating cname record as well. Waited over 48 hours but still my example.com doesn't load any app.
I am not an expert on any of these issue. Please help me.
Please note, my example.com domain was pointing to a cloudfont and s3 bucket before.
Thanks you so much.
Make sure you've route53 NS entries in your domain provider console so example.com can resolve to your ElasticBeanstalk LoadBalancer address. After you have entered nameserver entries in domain provider console check if DNS servers are propagated successfully. MoreOver for domain entry select A record type with Alias to your ElasticBeanstalks's LocadBalancer address.
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.
I am trying to point Cloudflare DNS into Amazon's AWS EC2 server, but am unable to do so. When I set this up, the request to go into my url simply times out.
Based on this previous question, I have tried the steps (except using route53) but the subdomain still cannot not be accessed. tracert shows the request timed out half way.
How can I successfully point Cloudflare to AWS EC2 server without using route53?
Cloudflare explains how to do this here.
https://support.cloudflare.com/hc/en-us/articles/360020991331
You add a CNAME record at Cloudflare to your AWS hostname, the URL that looks like this: my-cool-cachepp-1344276401.eu-west-1.elb.amazonaws.com
CloudFlare is an authoritative DNS provider, you have absolutely no need for another DNS provider like Route53.
Instead you set the nameservers which CloudFlare issued you at your domain registrar.
You will need to enter in your existing DNS records at your DNS registrar into CloudFlare for any DNS records you wish to migrate: