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


i own domain name in aws route 53 'www.derbyware.com', have web application running @ 'http://node147934-env-7029269.phx.enscaled.us' on jelastic. users want them access web application using www.derbyware.com not ugly url 'http://node147934-env-7029269.phx.enscaled.us'. made www.derbyware.com act domain name web application. non www 'derbyware.com' not work.

you can test urls.

enter image description here

this solution aws support

resolution:

use following procedure redirect domain. in example, redirect example.com example.net.

requirements:

  • a hosted zone domain example.com hosted in amazon route 53.
  • you have permissions add resource records hosted zone of example.com.
  • you have permissions create amazon s3 bucket.
  • you able create s3 bucket exact name example.com.

note: sites must http, because redirect cannot connect s3 on https.

  1. in amazon s3 console, create s3 bucket exact name example.com.

note: s3 bucket names must globally unique. if bucket name need in use, solution cannot used.

  1. choose bucket created, , choose properties. expand static website hosting dropdown menu, , select redirect requests host name.
  2. in redirect requests host name field, enter example.net , choose save.
  3. in route 53 console, select hosted zone named example.com.

  4. create resource record example.com following values:

    • record type: choose ipv4 address.
    • alias: choose yes.
    • alias target: select blank value field, expand drop down menu, , choose s3 bucket under header s3 website endpoints.
    • routing policy: choose simple.
    • evaluate health target: choose no , choose create. note: drop-down menu might take few moments populate bucket name.

you should able redirect example.com example.net. can confirm browsing example.com or curl example.com. should see "301 moved permanently" in curl output, redirecting example.net.


Comments

Post a Comment

Popular posts from this blog

Command prompt result in label. Python 2.7 -

i want put result(output) of shell command label. command works, label shows "0", however, in command prompt, result shown correctly, need showed in label. doing ubuntu. myg1 = button(root, text="rodyti informacija", command=lambda: gauti()) myg1.pack(side=bottom) def gauti(): imti = tekstas.get("1.0", "end-1c") info = subprocess.call("id '{imti}' ".format(imti=imti), shell=true) w = label(root, text= info) w.pack(side = bottom) subprocess.call() returns exit code of process created (in case 0 success). if want text output of process, should instead call subprocess.check_output() .
Read more

javascript - How do I use URL parameters to change link href on page? -

i change href value of link using url parameters. example: default <a id="dlink" href="link-1">link</a> but, when user goes https://url.com/?dlink=link-2 it swaps out link new link <a id="dlink" href="link-2">link</a> first need value url. if you're not using javascript framework can create function using jquery. please check get url parameter jquery or how query string values in js it. after that, element "a" id , set value there. $("#dlink").attr("href", hreffromparam);
Read more

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -

so have domain nameservers pointed aws route 53. site hosted on ec2 instance , reachable resolves site.com, if input www.site.com. i'm curious how site resolve www.site.com. have under route53 domains hosted zone 2 additional record sets outside of ns , soa: a site.com ec2 elastic ip cname www.site.com ec2 public dns i can reach site using both site.com , www.site.com, resolve site.com. there way make if enter either, resolves www.site.com? at first, both should record set. a site.com ec2 elastic ip www.site.com ec2 elastic ip and need redirect setting in web server (nginx, apache, ..) following. (source: how redirect www non-www nginx on centos 7 ) redirect non-www www if want redirect users plain, non-www domain www domain, add server block: server { server_name example.com; return 301 $scheme://www.example.com$request_uri; } save , exit. configures nginx redirect requests "example.com" "www.example.com". not
Read more