Hey! I promise I will make a revision video with OAC in the future. In the meantime, you can check out a revised GitHub repository I made for you that actually has this change: github.com/Cloudmancermedia/cdk-spa-deployment-oac.git In the README I have some notes on how it was achieved and why its necessary for the workaround. I hope this helps!
Thanks for making this video, it was really helpful for me in my current project. Had a quick question. Is the same possible with a single bucket with multiple folders containing different projects in a single distribution as multiple origins with different subdomains?
I am glad it helped you! To answer your question, kind of. You can have a single S3 bucket with subfolders like dev/ prod/ and have those serve as the source for a distribution. For your specific use case, I am pretty sure you would need a different distribution for each dev/ prod/ x/ folder you wanted to serve as your subdomains website. I know this is possible for sure, as far as how to configure it, let me do some digging. As far as it being a single distribution, I don't think so. While I know its possible to have multiple origins for a distribution, I believe this is intended for serving specific requests to specific paths. You can set it up to serve static content from the bucket and dynamic content from lets say a load balancer in front of an EC2, but this is meant to be the same "website" even though they are different origins. I am pretty sure the domain name wouldn't change for the client, each page would just serve content from different sources based on the path.
No problem! To follow up, I believe that in order to set up a subfolder as the origin you simply would just add the subfolder to the default root object of cloudfront. So just prod/index.html dev/index.html, etc. This way you can have just a single S3 bucket and have each distro with a subdomain set up to each subfolder in the bucket. TBH this is actually probably the preferred way to do it since there are bucket limits! Good suggestion!
What videos do you want to see me make next on this channel?
Do also make one on the use of the OAC over the OAI as per the AWS recommendation.
Hey!
I promise I will make a revision video with OAC in the future. In the meantime, you can check out a revised GitHub repository I made for you that actually has this change: github.com/Cloudmancermedia/cdk-spa-deployment-oac.git
In the README I have some notes on how it was achieved and why its necessary for the workaround.
I hope this helps!
@@cloudmancer thanks a bunch 👍
Thanks for making this video, it was really helpful for me in my current project. Had a quick question. Is the same possible with a single bucket with multiple folders containing different projects in a single distribution as multiple origins with different subdomains?
I am glad it helped you! To answer your question, kind of.
You can have a single S3 bucket with subfolders like dev/ prod/ and have those serve as the source for a distribution. For your specific use case, I am pretty sure you would need a different distribution for each dev/ prod/ x/ folder you wanted to serve as your subdomains website. I know this is possible for sure, as far as how to configure it, let me do some digging.
As far as it being a single distribution, I don't think so. While I know its possible to have multiple origins for a distribution, I believe this is intended for serving specific requests to specific paths. You can set it up to serve static content from the bucket and dynamic content from lets say a load balancer in front of an EC2, but this is meant to be the same "website" even though they are different origins. I am pretty sure the domain name wouldn't change for the client, each page would just serve content from different sources based on the path.
@@cloudmancer thanks for the explanation and tutorial. Subscribed
No problem!
To follow up, I believe that in order to set up a subfolder as the origin you simply would just add the subfolder to the default root object of cloudfront. So just prod/index.html dev/index.html, etc. This way you can have just a single S3 bucket and have each distro with a subdomain set up to each subfolder in the bucket. TBH this is actually probably the preferred way to do it since there are bucket limits! Good suggestion!
@@cloudmancer thanks. I was thinking the same