amazon-route53 | 易学教程

Linking Amazon Route 53 Domain Name to EC2 instance

阅读更多关于 Linking Amazon Route 53 Domain Name to EC2 instance

问题 I have registered a domain name with Amazon Route53 and I'm trying to link it to an EC2 instance. I'm unable to do this successfully. I have read documentation many times over, I have looked at many tutorials online, I have read many stack overflow answers. I still haven't been able t figure it out. Help will be greatly appreciated. What I have done so far: Launched EC2 instance and installed LAMP stack. I'm running a web app on the instance. Associated an Elastic IP to the instance and I'm

S3 hosted website Cloudfront distribution and API Gateway custom domain pointing to the same subdomain

阅读更多关于 S3 hosted website Cloudfront distribution and API Gateway custom domain pointing to the same subdomain

问题 I have a subdomain for my website named api.example.com and I want to have the following achieved: have 1 CloudFront distribution for an S3 static website mapped to api.example.com have the API Gateway custom domain name mapped to the same subdomain api.example.com The steps I did to achieve this setup are: Create an API Gateway custom domain api.example.com and set the base mappings for the APIs I want to expose as v1 (version 1 for now) In Route 53 I created a CNAME record api.example.com

Redirect subdomain URL to URL subdirectory on Amazon AWS

阅读更多关于 Redirect subdomain URL to URL subdirectory on Amazon AWS

问题 We've created a subdomain via Route 53 on AWS that points to an external server. We now want to redirect that traffic back to the main domain, but to a subdirectory. shop.mydomain.com would redirect to mydomain.com/shop DNS doesn't like resolving subdirectories like that... any suggestions? 回答1: If I understand correctly, you want ALL requests to shop.mydomain.com to redirect to mydomain.com/shop . In that case I recommend using S3's "Redirection Rules". Create a bucket in S3 called shop

Multiple IP addresses for Resource Record Sets of Route 53

阅读更多关于 Multiple IP addresses for Resource Record Sets of Route 53

问题 I'm studying aws route53, when I'm creating the resource record set, I can add multiple IP addresses to value of record set. What is the purpose of multiple IP addresses here? Ex: my domain will route to server 1 and server 2. I tried to stop server 1 and access to my domain, but it did NOT route to server 2. What is the issue here? Could you please explain multiple IP addresses of record set's value? Thanks! 回答1: The correct question is stated in the AWS Route 53 documentation: https://aws

How can I redirect a request to a subdomain to another subdomain on Route 53?

阅读更多关于 How can I redirect a request to a subdomain to another subdomain on Route 53?

问题 I have a GitHub Pages Jekyll blog at blog.Antrikshy.com. I have been meaning to move it to code.Antrikshy.com for a while now. I made the new address a CNAME for antrikshy.github.io on Amazon and wired everything correctly to make it work. Now my blog.Antrikshy.com URL is broken. How can I set it to redirect it to the new subdomain? I'm new to this. Comment if you want any more information. Preferably I'd like to do a 301 redirect and also retain the entire path, but that's not very important

Terraform: Creating and validating multiple ACM certificates

阅读更多关于 Terraform: Creating and validating multiple ACM certificates

问题 I'm running into a really confusing Terraform resource issue automating the generation and DNS validation of SSL certificates in ACM for a list of (Terraform-managed) hosted zones. Code can also be found in this gist. I'm starting by bootstrapping hosted zones referencing this environment-specific variable. hosted_zones = [ { domain = "site1.com" zone_id = "MANUALLY FILL" } ] The block I am using to build the zones seems to work reliably. resource "aws_route53_zone" "zones" { count = "$

Restricting website access by country

阅读更多关于 Restricting website access by country

问题 I am hosting my website using AWS. The website is on 2 ec2 instances, with a load balancer (ELB) balancing traffic between them. Currently, I am using my DNS (Route 53) to restrict the access to the website by using Route 53's geolocation routing: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo (The geolocation restriction is just to limit the initial release of my website. It is not for security reasons. Meaning the restriction just needs to

How do you redirect from one toplevel domain to another using Route53

阅读更多关于 How do you redirect from one toplevel domain to another using Route53

Apologies if my terminlogy is not quite correct here I have the domain albunack.net working fine on Route53. I also have domain albunack.com under Route 53 control I want any requests to albunack.com to redirect to albunack.net and also to show the user they are on albunack.net not albunack.com (via the webbrowser address) I tried creating an A record as Alias for albunack.com and setting alias target to albunack.net but that didnt work it didnt recognise albunack.net , how am i meant to do it ? You can do this by using an S3 bucket to redirect to albunack.net. First, you'll need to create an

Serve non-subdomain routes

阅读更多关于 Serve non-subdomain routes

I want to use Wordpress to host company's blog. Main website is an ASP app. They are hosted on different EC2 instances. Blog should have non-subdomain URL: example.com/blog , not blog.example.com . How can this be done? Can load-balancing tool like Cloudflare help with that? I tried doing some kind of masking using Route53. Also experimented with hosting the blog in IIS side-by-side with main site. You could put nginx upstream of both of them and use it as a reverse proxy to both of them matching the URL that is being targeted. A sample nginx config might look something like this: server {

How to redirect traffic from non www domain name to www.example.com in AWS Route 53

阅读更多关于 How to redirect traffic from non www domain name to www.example.com in AWS Route 53

问题 I own a domain name in AWS Route 53 'www.derbyware.com', I have a web application running at 'http://node147934-env-7029269.phx.enscaled.us' on Jelastic. now for my users I want them to access the web application using www.derbyware.com not the ugly url 'http://node147934-env-7029269.phx.enscaled.us'. I successfully made www.derbyware.com act as the domain name for the web application. now non www 'derbyware.com' does not work. you can test the urls. 回答1: This is the solution from AWS Support