Hello everyone. Looking for some advice on this: • I have one domain (ie: https://www.mydomain.com) and will have multiple SST frontend projects for separate business needs. • How can I have these multiple SST frontend projects distributed like that? ◦ https://www.mydomain.com/application1 ◦ https://www.mydomain.com/application2 ◦ https://www.mydomain.com/application3 Any ideas on how to accomplish that? Thanks in advance!

You are looking at a concept named “micro-frontends”. Googling that phrase should help. Warning: This is going to be much harder than you are probably thinking, and will likely be specific to your frontend choice (not SST).

If I could just import an existing distribution and add additional behavior, it would solve the issue, but it's NOT possible as their documentation suggests. So, I'm working with two workaround scenarios: 1. Continue having all these SST projects separate and SST will provision and deploy as usual, then having a shared CloudFront created manually on AWS so that I can just add a new distribution on the AWS console pointing to that s3 react site bucket deployment that SST just created. Pros: I won't need any complex or extra config on my SST. Cons: Have to manually create a new distribution for the shared CloudFront and keeping not used CloudFront and distribution automatically created for that app (any way to say to SST not creating these?) 2. Having a mono repo, then I first create a Distribution and add all the buckets internally created for all the apps contained in the monorepo. Pros: not needing to create anything manually on AWS. Cons: having the have all projects in a single repo

If you have simple sites with only S3, that makes it a little easier. • There is no reason for SST to be involved, really, and you will end up with [# of projects] meaningless cloudfronts and really slow deploys. SST only has single site constructs. • Either case you present is merely repo organization and the end product will look the same in AWS. That decision is totally up to you, either is possible and about the same difficulty. In either case, you will need to create the buckets and upload the sites FIRST, then create and hook the Cloudfront to them, though.

actually these SST projects may also contain simple lambdas, but for that it's easy to put behind

<https://api.mydomain.com/application1>

@Leo Hick if u do decide to take the monorepo approach, ur app would probably look something like this:

app
  .stack(Site1Stack)
  .stack(Site2Stack)
  .stack(Site3Stack)
  .stack(CloudFrontStack);

So in each of the Site stack, you can create a

sst.Bucket

to house the file; use the

BucketDeployment

construct to deploy ur files to the bucket (doc). Finally, in the CloudFront stack, you create a distribution and map the s3 origins.

@Derek Kershner @Frank thank you for your insights!

@Frank this is what I was thinking to do too.

I think you are misreading above. Should be 1 CFront.

The problem is…

You can, definitely, do what you say, and I think it will probably work, but just was pointing out that would be against the above advice and would have significant downsides on complexity and cost.

Makes sense, yes.