amazon-route53

I host a site on a single EC2 instance behind CloudFront and need to redirect all non-www traffic to www. From other Q/A here on SO I was able to configure an A record on Route53 to redirect traffic from example.com to www.example.com. However, this only works for http traffic, not https traffic. How can I get the https traffic for the naked (non-www) URL to redirect to my canonical URL https://www.example.com ? I know there are similar questions asked already, but I don't see any with my same configuration (most are for sites hosted in an S3 bucket or for redirecting from www to non-www).

I'm using Amazon SES and Route53 and confused how I specify the TXT value to include the proper SPF config. Amazon gave me a SES TXT name/value pair which looks something like this: Name: "_amazonses.xxx.com" Value: "bInxJfnRbxxxxx9uFXgmxxxxxQHd08UxxxxxxsG+k=" I plugged this into my Route53 Record Set (same as "Zone file" on Godaddy). Sure enough after adding my SMTP credentials to my app and having Amazon verify my account ("grant production access"), it works and I can send email from my site to a variety of accounts (Gmail, Yahoo, Hotmail, my .edu university account). I know nothing about

I have a problem with domain hosting in Route 53. I need to redirect from xyz.com to www.xyz.com , so I created a Hosted Zone on Route 53. I added an A record with the address of my ELB, and a CNAME with a name of www.xyz.com and value of my ELB address. But this set up does not redirect my naked domain to my www prefixed domain. How do I solve this issue? I've gotten this to work using both S3 and CloudFront. You need two buckets: www.yourdomainname.com and yourdomainname.com . Keep your files in the www bucket. For the naked domain bucket properties, go to the "Static Website Hosting"

My iOS software platform runs on AWS Elastic Beanstalk and has a URL we'll call "something.elasticbeanstalk.com". I have a website we'll call "website.com" I purchased and operate the DNS records for through Namecheap. I need to make the URL my iOS client apps use to connect to the server HTTPS since Apple is requiring this soon due to App Transport Security. WHAT I THINK I'M SUPPOSED TO DO What I think I'm supposed to do is, create an SSL certificate for "website.com" and apply that SSL certificate to the AWS EB load balancer. Then I need to create a subdomain for "website.com" that redirects

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 also serving up the maintenance page. Since we dont have sticky sessions enabled, we want to prevent

I have recently transferred my domain name trademarklawexplained.com from One.com to AWS. I have the following set-up in Route53: For some reason, none of my records (SOA, NS and A) have had any effect. trademarklawexplained.com does not map to 35.176.22.92 , nor does it even look at the name server (I tested it with this tool ) Have I set up my hosted zone incorrectly, should I somehow publish it, or is the issue with One.com? If someone could point me in the right direction to troubleshoot it would be greatly appreciated. Figured it out in the end… For a name server to be associated with a

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 have to change its domain's DNS to his own hosted zone in my Route53. My server will handle many domains.