On AWS we have 2 Elastic Beanstalk instances and one S3 bucket for a static website. Since app used Login With Amazon we added https protocol. Recently we moved a domain to Route 53, created SSL certificates and configured Load Balancers with https for each of instances.
The website/elastic instances work well when addressed to generic by AWS domains.
But we faced with a problem when using the created domain on route 53. Sometimes domain is not available and we don't know why (see attached video). Failed to open route 53 domain
This issue reproduces on Safari when you refresh a web page many times and our servers become unavailable. We spent 1 week trying to fix this problem without any success. The real problem is that we don't even know what can be a reason. Any thoughts?
Thanks for any response!
As I can see from your domain informations you are pointing to an AWS IP-Address with an A-Record.
You should point your domain as "CNAME" to the AWS Url.
The IP of your Elastic Beanstalk Instances can change, the Elastic Beanstalk Url does not.
Greetings
Dominik
Resolved with this answer on AWS forum
https://forums.aws.amazon.com/thread.jspa?threadID=295461
Updated:
Unfortunately, the link is broken and I can't remind myself how it was fixed. It was a few years ago...
Related
I have hosted a website using the LAMP stack in AWS Lightsail.
I am trying to enable SSL certificates for AWS Lightsail and custom DNS Cloudflare. I have already tried all the steps from 1-18 listed in the below article
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/verify-tls-ssl-certificate-using-dns-cname-https
Additionally, I added two CNAME records to my Cloudflare one for the root domain and the other for the www subdomain with a target as the Lightsail Load balancer and proxy status as proxied (tried DNS only).
I have tried all the possible combinations to make it work however, even after a couple of days status is showing as validation in progress.
Just wanted to check if anyone else had faced the same problem or if someone can suggest some troubleshooting steps or if I have missed anything?
Thanks in advance!
Regards,
Piyush
Try adding a CAA record pointing to amazon.com in your Cloudflare DNS settings. Then create the TLS certificate from your Lightsail load balancer page.
If the above doesn't work I suggest you install AWS CLI and perform a aws lightsail get-load-balancer-tls-certificates. The response will show a failureReason field which will help you investigate. For example if the failureReason field returns "CAA_ERROR", then adding CAA records as I descibed above will solve the problem.
get-load-balancer-tls-certificates' documentation: https://docs.aws.amazon.com/cli/latest/reference/lightsail/get-load-balancer-tls-certificates.html
Actually, I made a mistake while creating the CNAME record hence, it was not validated. After removing some additional fields from the string, worked!
Thanks
I have been trying to host our php website using Elastic Beanstalk however I had no luck under Hosted Zones. Domain is registered with the same AWS account.
Things I did:
Created a hosted zone named mycustomdomain.com
Created a A type record set with ALIAS to my environment. (Selected through drop down of AWS itself.)
The domain name of EB Environment
environmentname.randomclashofcharacters.region.elasticbeanstalk.com
assigned by AWS works flawlessly so I can say that there is nothing wrong with the config at Elastic Beanstalk side of things.
I followed through the guide uploaded by AWS themselves
I see one weird thing that might be causing that. The name servers listed under domain name is different from ones listed in Hosted Zone. Should I change them. AWS guide doesn't says to do so, so I didn't do it.
Thanks for your help beforehand.
Cheers,
~bio
Thanks to corrective help from #heplalump the problem is resolved. I actually needed to make domain's name-servers same with the hosted zones. Still cannot reach from desktop Safari but reachable via chrome and iPhone safari. If you want to do this procedure for yourself just follow the guide amazon provided.
I have recently bought a domain (caracara.es) with Route 53. It seemed to register all good and AWS created a hosted zone automatically for it.
I wanted to link it to the web hosted on S3 and as per instructions I created an A record and selected a bucket Alias from the dropdown (its set as web bucket etc.). That is the result:
The issue I'm having is that I don't seem to be able to access my domain from the outside world (I waited about 12 hours now) and I'm not sure how can I debug what's wrong with it... (ping says unknown host)
BTW, I have NS records, SOA records automatically created by AWS.
Would appreciate any help,
Thanks,
Michal
It turns out my domain was not setup correctly. The hosted zones NS automatically created by AWS didn't match the name server names of the domain itself.
Once I updated the domain to use nameservers from Hosted Zone - everything works fine.
Thanks for your help.
Michal
at the first place, we hosted our React App on the S3 to which we assigned CloudFront distribution and then we connected it to somedomain.com domain.
The thing is that for marketing tests we had to change A-record in Route53 to point to a totally different server than AWS. So the problem is that some of the users already used our React App with ServiceWorker that was hosted on S3, and even that we changed A-records to point to different server - they still see AWS cached version.
We have no idea where is the problem, and if we should change something in Route 53 or Cloudfront?
I have come across this before, but don't have a good explanation as to why it happened.
I had to remove the domain from the CloudFront distribution before I got all traffic being sent correctly to the new record in Route 53.
After removing the domain from the CloudFront config, traffic immediately started being sent to the value in the A record in Route 53.
Hope this helps.
I have a hosted zone and the accompanying record sets defined to serve a domain which lives in GoDaddy. I went to the AWS console today and found my hosted zone is no longer listed. However, it is still working and routing to my AWS server instance. Has anyone else see this issue in AWS? Any advice for finding my missing, yet working, hosted zone definition?
Double-check the account you use. Asking on AWS' own forums may get you some help from the employees.