Vivek M. Chawla

Entrepreneurial technophile, Cloud Computing expert, and wannabe dog whisperer.

For some reason, every time I sit down with an Entity Relationship Diagram, the first thing I have to do is try to remember what the relationship symbols mean. Doesn't matter if I cranked out five ERDs last week. The meanings of the various chicken-scratches...err, crow's feet...just never stick in my brain.

To help myself out, I've created this single page, printable PDF and tacked it to my bulletin board.

Download the PDF here: ERD Relationship Symbols Quick Reference.pdf

ERD "Crow's Foot" Relationship Symbols Cheat Sheet

For some reason, every time I sit down with an Entity Relationship Diagram, the first thing I have to do is try to remember what the relationship symbols mean. Doesn't matter if I cranked out five ERDs last week. The meanings of the various chicken-scratches...err, crow's feet...just never...

Using only the tools available in Amazon S3 and Amazon Route 53, this guide will teach you how to create a URL Redirect that automatically forwards http://url-redirect-example.vivekmchawla.com to the AWS Console sign-in page aliased to "MyAccount", located at https://myaccount.signin.aws.amazon.com/console/.

The steps outlined here can be used to set up URL forwarding to any URL, not just ones from Amazon. You will learn how to set up forwarding to specific folders (like /console in my example), and how to change the protocol of the redirect from HTTP to HTTPS (or vice versa).

Step One: Create Your S3 Bucket

What goes here?

Open the S3 management console and click "Create Bucket".

Step Two: Name Your S3 Bucket

  1. Choose a Bucket Name. This step is really important! You must name the bucket EXACTLY the same as the URL you want to set up for forwarding. For this guide, I'll use the name url-redirect-example.vivekmchawla.com.
  2. Select whatever region works best for you. If you don't know, keep the default.
  3. Don't worry about setting up logging. Just click the "Create" button when you're ready.

Step 3: Enable Static Website Hosting and Specify Routing Rules

  1. In the properties window, open the settings for "Static Website Hosting".
  2. Select the option to "Enable website hosting".
  3. Enter a value for the "Index Document". This object (document) will never be served by S3, and you never have to upload it. Just use any name you want.
  4. Open the settings for "Edit Redirection Rules".
  5. Paste the following XML snippet in it's entirety.
<RoutingRules>  
  <RoutingRule>
    <Redirect>
      <Protocol>https</Protocol>
      <HostName>myaccount.signin.aws.amazon.com</HostName>
      <ReplaceKeyPrefixWith>console/</ReplaceKeyPrefixWith>
      <HttpRedirectCode>301</HttpRedirectCode>
    </Redirect>
  </RoutingRule>
</RoutingRules>  

If you're curious about what the above XML is doing, visit the AWM Documentation on "Syntax for Specifying Routing Rules". A bonus technique (not covered here) is forwarding to specific pages at the destination host, for example https://redirect-destination.com/console/special-page.html. Read about the <ReplaceKeyWith> element if you need this functionality.

Step 4: Make Note of Your Redirect Bucket's "Endpoint"

Make note of the Static Website Hosting "endpoint" that Amazon automatically created for this bucket. You'll need this for later, so highlight the entire URL, then copy and paste it to notepad.

CAUTION! At this point you can actually click this link to check to see if your Redirection Rules were entered correctly, but be careful! Here's why...

Let's say you entered the wrong value inside the <Hostname> tags in your Redirection Rules. Maybe you accidentally typed myaccount.amazon.com, instead of myaccount.signin.aws.amazon.com. If you click the link to test the Endpoint URL, AWS will happily redirect your browser to the wrong address!

After noticing your mistake, you will probably edit the <Hostname> in your Redirection Rules to fix the error. Unfortunately, when you try to click the link again, you'll most likely end up being redirected back to the wrong address! Even though you fixed the <Hostname> entry, your browser is caching the previous (incorrect!) entry. This happens because we're using an HTTP 301 (permanent) redirect, which browsers like Chrome and Firefox will cache by default.

If you copy and paste the Endpoint URL to a different browser (or clear the cache in your current one), you'll get another chance to see if your updated entry is finally the correct one.

To be safe, if you want to test your Endpoint URL and Redirect Rules, you should open a private browsing session, like "Incognito Mode" in Chrome. Copy, paste, and test the Endpoint URL in Incognito Mode and anything cached will go away once you close the session.

Step 5: Open the Route53 Management Console and Go To the Record Sets for Your Hosted Zone (Domain Name)

  1. Select the Hosted Zone (domain name) that you used when you created your bucket. Since I named my bucket url-redirect-example.vivekmchawla.com, I'm going to select the vivekmchawla.com Hosted Zone.
  2. Click on the "Go to Record Sets" button.

Step 6: Click the "Create Record Set" Button

Clicking "Create Record Set" will open up the Create Record Set window on the right side of the Route53 Management Console.

Step 7: Create a CNAME Record Set

  1. In the Name field, enter the hostname portion of the URL that you used when naming your S3 bucket. The "hostname portion" of the URL is everything to the LEFT of your Hosted Zone's name. I named my S3 bucket url-redirect-example.vivekmchawla.com, and my Hosted Zone is vivekmchawla.com, so the hostname portion I need to enter is url-redirect-example.
  2. Select "CNAME - Canonical name" for the Type of this Record Set.
  3. For the Value, paste in the Endpoint URL of the S3 bucket we created back in Step 3.
  4. Click the "Create Record Set" button. Assuming there are no errors, you'll now be able to see a new CNAME record in your Hosted Zone's list of Record Sets.

Step 8: Test Your New URL Redirect

Open up a new browser tab and type in the URL that we just set up. For me, that's http://url-redirect-example.vivekmchawla.com. If everything worked right, you should be sent directly to the sign-in page of your AWS console!

Because we used the myaccount.signin.aws.amazon.com alias as our redirect's destination URL, Amazon knows exactly which account we're trying to access, and takes us directly there. This can be very handy if you want to give a short, clean, branded AWS login link to employees or contractors.

Conclusions

I personally love the various AWS services, but if you've decided to migrate DNS management to Amazon Route 53, the lack of easy URL forwarding can be frustrating. I hope this guide helped make setting up URL forwarding for your Hosted Zones a bit easier.

If you'd like to learn more, please take a look at the following pages from the AWS Documentation site.

How To Set Up URL Forwarding in AWS Using Only Route 53 and S3

Using only the tools available in Amazon S3 and Amazon Route 53, this guide will teach you how to create a URL Redirect that automatically forwards http://url-redirect-example.vivekmchawla.com to the AWS Console sign-in page aliased to "MyAccount", located at https://myaccount.signin.aws.amazon.com/console/. The steps...