amazon-route53

问题 How do you put up a maintenance page in AWS when you want to deploy new versions of your application behind an ELB? We want to have the ELB route traffic to the maintenance instance while the new auto-scaled instances are coming up, and only "flip over" to the new instances once they're fully up. We use auto-scaling to bring existing instances down and new instances, which have the new code, up. The scenario we're trying to avoid is having the ELB serve both traffic to new EC2 instances while

问题 I had a question about using the URL in my Load Balancer - and using it as the A Record for my DNS entry via GoDaddy...GoDaddy doesn't allow a URL, and insists on the A Record being an IP address and no other format. But I don't see this option available in the Load Balancer I created, only a URL. What I have so far is this.. I've created a Load Balancer successfully using both HTTP and HTTPS, along with the RapidSSL cert I purchased and imported. When I open my new Load Balancer item in EC2

问题 I am working on a Heroku and don't have much background in networking. The app I am working on seems to be unreachable from some places. We got reports from people not being able to access it A ping service we use (Statuscake) reports that the site is consistently unreachable from certain node locations To fix that, we moved DNS to Amazon Route 53. A week after, there is a change in what countries work by the ping service, but essentially we're still permanently down for some world locations,

问题 I'm building a solution that will be provided to several companies. Any company will have to point their domains (or just a sub-domain) to my server and then I'll handle pages to their customers. I'm testing it with the following config: CustomerABC.com pointing to one hosted zone into Route 53 CustomerDEF.com pointing to another hosted zone into Route 53 Both hosted zones have an A record pointing to the same EC2 server instance That said, every customer that wants to use my service will

问题 I have a subdomain in Amazon Route53. Let's say secure.example.com If requests come like https://secure.example.com it is ok but I would like to force http requests to come through https. When user types http://secure.example.com it needs to be forwarded to https://secure.example.com . Is there a domain level redirecting/forwarding requests coming through http to https in Amazon Route53 ? 回答1: No, there is no way to do this -- because it's not a DNS function to force any particular protocol,

问题 I've got a pretty specific problem here, we've got a system that we already have and maintain, the system involves using subdomains to route people to specific apps. on a traditional server that goes like follows; we have a wildcard subdomain, *.domain.com that routes to nginx and serves up a folder so myapp.domain.com > nginx > serves up myapp app folder > myapp folder contains a static site I'm trying to migrate this in some way to AWS, I basically need to do a similar thing in AWS, I toyed

问题 I have an Amazon EC2 instance on AWS associated with an ElasticIP. I purchased domain from Route 53. It automatically created the Hosted Zone. It worked fine after creating a Record Set for the domain name. I have deleted that Hosted Zone but when I add it again, it is not working. What am I missing there? 回答1: When you delete a hosted zone and then put it back, you're not exactly putting it back. You're just creating one similar to (but not identical to) the original. So don't do that. But,

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . Forgive me if this has been asked before, there are a number of resources that touch on this, but nothing seems to fit for my specific (https) use-case. I'm trying to redirect https://www.example.com to https://example.com. Likewise, this should work for http://www.example.com to https://example.com. I have set

问题 I have a Heroku app set up with SSL certificates, and my DNS does not allow CNAME records at the Apex level. Meaning, I cannot point my A Record at my Heroku app URL (A level records can only be IP addresses and Heroku cannot provide a static IP). There other methods (both here on stack and on heroku's guides) that recommend using other DNS providers, but I would like to try and solve this with AWS (Specifically Route53), while also retaining our https:// in the domain for SSL. I found some

问题 this is how im setting up the entry cat << EOF > /tmp/route53-healthcheck.json { "IPAddress": "10.10.10.10", "Port": 80, "Type": "HTTP", "ResourcePath": "/somefile.txt" } EOF aws route53 create-health-check \ --caller-reference $(date +'%Y%m%dT%H%M%d') \ --health-check-config file:///tmp/route53-healthcheck.json > /tmp/route53-healthcheck.log and when i see the route53 entry, its missing the name (the first entry is a manual entry and the second one is from the snippet above. Im referring to