AWS S3 static website buckets routing per subdomain - amazon-web-services

I have created a hosted zone: "abc.com" and 2 s3 buckets: "app1.abc.com" and "app2.abc.com" with respective index.html. I am able to accesss individual default s3 website successfully (ex: app1.abc.com.s3-website-ap-southeast-1.amazonaws.com and app2.abc.com.s3-website-ap-southeast-1.amazonaws.com)
Now, How to create record sets to redirect traffic lets say if "app1.abc.com" called, then index.html of "app1.abc.com" bucket should be accessed. If "app2.abc.com" called, then index.html of "app2.abc.com" bucket should be accessed.
Is it possible to do with s3 and route53? If not any other ways to redirect traffic based on url to s3 bucket?
I went through documentation but no clue. Appreciate for help.

You simply need to create a CNAME record that point app1.abc.com to app1.abc.com.s3-website-ap-southeast-1.amazonaws.com. The procedure is the same for the second bucket.
For documentation, see https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingCustomURLs

Related

Redirect directories to individual s3 buckets?

I have a Laravel application hosted on a domain. I have several dynamic directories ie:
example.com/directory
example.com/random
example.com/moon
I would like each of these directories to resolve to a different s3 bucket while masking the URL (I want to see the URL above, not the s3 bucket URL). What's the best way to accomplish this? I could possibly create a primary bucket and host example.com on it and create routing rules on that s3 bucket to redirect to the other s3 buckets (I think). What do those routing rules look like? I was unable to find directions in the AWS documentation that showed how to redirect to other buckets. Is there another, more simple way to go about this?
It's worth noting the Laravel application may not need to be involved in the actual routing as much as using the AWS sdk to dynamically configure the directories.
You have to use Route53 along with S3 enabling static website hosting.
For detail configuration about static website hosting in S3, you can take a look here.
After that choose Route53 as a service in AWS Console.
Select your hosted zone and add a CNAME recordset, in the value field enter the S3 bucket endpoint url and in the Name field enter the url that you want to point to the S3 bucket.
For using Route53 you can read this AWS document.
The best way would be to create a CloudFront (CF) distribution with three different origins. Then each origin would respond to different Origin Path which would lead to different buckets.
example.com could be defined in Route53, with Alias A record to the CF distribution. The benefit of using CF with S3 is that you not only can speed up your website (CF is CDN), but also you can keep your buckets and objects private:
Amazon S3 + Amazon CloudFront: A Match Made in the Cloud

Can I Use same AWS S3 bucket for 2 domains whilst using the cloudflare CDN

I am using AWS S3 bucket for storing and displaying the user upload image files.
My website name is example.net and as I want to use cloudflare CDN and show the image url path as images.example.net (as I want to mask the S3 url).
I created a S3 bucket with name images.example.net and mapped the CNAME images.example.net.s3.us-east-1.amazonaws.com as images.
So I am able to access the images using url images.example.net/myPic.jpg
Recently I got a new domain example.com (only the extension is different), and now I want to use the same S3 bucket example.net to store the files and the url needs to shown as images.example.com/myPic.jpg
If I create a new S3 bucket images.example.com , then I can do it, but I want to use the existing one only.
Is there any method to configure in cloudflare for that ?
Can I do it without creating a new bucket named images.example.com ?
If you're using virtual hosting then you're limited to a single domain per bucket by using the domain as the bucket name.
The only options available to you are:
Create a second S3 bucket with your other domain name as the CNAME
Create a CloudFront distribution in front of your S3 bucket and specify both domains as alternative domain names. Then on CloudFlare use the CloudFront CNAME. Disable all caching to allow CloudFlare to handle all the CDN functionality.
Obviously neither are ideal for your scenario, however these are the options available at this time.

Hosting multiple sub-domains from a single aws s3 bucket

Is it possible to host multiple subdomains from a single bucket folders?
Example -
Lets assume bucketname is my aws s3 bucket.
To access the site url is - http://bucketname.s3.amazonaws.com.
Now lets assume i have 5 folders inside it - a,b,c,d & e.
Can i create subdomains pointing to their respective folders inside the s3 bucket. Like -
http://a.bucketname.s3.amazonaws.com site works from folder a of the bucket
http://b.bucketname.s3.amazonaws.com site works from folder b of the bucket
http://c.bucketname.s3.amazonaws.com site works from folder c of the bucket
and so on.
Is it possible ?
Amazon S3 alone cannot do what you ask for.
The URL will point to only one bucket.
Typically, however, people want a Custom URL to point to content. For example, you could point mycompanyname.com to Amazon S3. This involves:
Owning the domain name
Creating a bucket with a name that matches the domain name (thus, you'd need one bucket per domain/subdomain)
Configuring the DNS entry (in Amazon Route 53 or your own DNS provider) to with a CNAME that points to the S3 bucket
Alternatively, behaviours can be configured in Amazon CloudFront that can present content from various back-ends.
Naming conventions for bucket URL are fixed by AWS. You cannot change to subdomain URL. You can use CloudFront to host it in your own domain or it can host under *.cloudfront.net.
Subdomain for cloudfront is also random. Will look like the following.
d3v7q0dqls688r.cloudfront.net
Hope it helps.

have multiple subdomains refer to the same S3 bucket without HTTP redirect

I have a bucket called subdomain.domain.com that hosts code that should be used whenever users go to various subdomains.
e.g. going to:
- a.domain.com
- b.domain.com
- c.domain.com
Should go to the same bucket.
I've set the CNAME for all the subdomain URL's to go to the URL of the subdomain.domain.com bucket. The problem is that, AWS tries to look for bucket a.domain.com' instead of just going tosubdomain.domain.com' bucket
I've read some suggestions saying I can create a bucket like a.domain.com and have it redirect back to subdomain.domain.com but I don't want a URL change and I'd like to be able to upload just to one bucket and all subdomains will be updated.
Some features that appear to be "missing" in S3 are actually designed into CloudFront, which complements S3. Pointing multiple domain names to a single bucket is one of those features. It isn't possible to do this with only S3 since, as you noticed, S3 matches the hostname with the bucket name.
Create a CloudFront distribution, defining each of the desired domain names as Alternate Domain Names.
For the origin server, type in the web site endpoint hostname of the bucket, found in the S3 console. (Don't select the bucket from the dropdown list).
Point the various hostnames to CloudFront in DNS.
CloudFront will translate the incoming hostnames so that S3 serves all the domains from a single bucket, the one you specified as the origin server.
Note that this configuration also allows you to optionally use SSL with your web hosting buckets, which is another feature that S3 relies on CloudFront to implement.

How to convert amazon aws subdomain into new format

The default endpoint & URL for an AWS hosted website is http://*username*.s3-website-us-east-1.amazonaws.com/index.html
But I have seen some like this https://s3.amazonaws.com/username/index.html
how do you do this?
You can always access an s3 hosted resource at:
http://s3.amazonaws.com/<bucket name>/<resource key (usually a filename)>
+1 for free-dom's answer...
...but even cooler is that you can use your own host/domain to access the content of the bucket.
Step 1. Create a bucket named, say, img.example.com, where you control the DNS for that domain.
Step 2. Add a CNAME entry in DNS that maps img.example.com to s3.amazonaws.com.
Step 3. There is no Step 3.
You can then access the files in that S3 bucket using http://img.example.com/FILENAME
This protects you in the event you want to change where your files are hosted to somewhere other than S3 (e.g., Amazon CloudFront CDN or another provider).