One additional option is to use a CloudFront function to do the redirect. It is pretty straightforward. Here is an example of how to accomplish this using a CloudFront function.
In the example above, replace the location response header (line 9) with the URL to your LinkedIn profile.
I should add, this option does not require any Route53 magic. Just create your Route53 CNAME record to point your personal domain to the CloudFront domain name, and then follow the steps in the tutorial I linked above.
The methods you mentioned are all using CNAME. It is used when you own both domain names. But I guess you are not the owner of
linkedin.com. So they won't work for you.
Instead, you can use client script redirect or HTTP redirect.
Client script redirect:
You can host your website on S3 (https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html)
Configure route53 to route your domain name to the S3 bucket (https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html)
This is the cheapest way.
- Accepted Answerasked 5 months ago
- asked 6 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 9 months ago
- SUPPORT ENGINEERpublished 4 months ago
They are able to redirect directly in S3 so they need only make an S3 bucket of the same name as their domain and configure it to redirect to their LinkedIn page. The next step is to hook up their bucket with an A (Alias) as an apex record in Route 53.
Thanks Richard. While non of those methods call out cname specifically, you are correct that linkedin is not mine. This seems to be why I can't name the bucket linkedin.com. I'm beyond needing AWS for dummies and submitted this to a friend. I'll share your feedback and in the future, I'll advise anybody that isn't an expert or training to use a different registrar.