Please expose Distribution in sst/constructs about sst

[zammitjames]

Yes +1 I would use this.

[jayair]

Hmm it's an internal construct. Is there a reason you want to use it?

[iliazlobin]

Yes, sure, there's quite a reason to use it, and I don't see a reason not to, cause everything is well-put and ready to be used for the only exception being not exposed, which you can fix with a simple patch (tested).

I want to use SST Distribution to create a CloudFront distribution and couple it up with a S3 bucket while having other things (like ACM cert) to be taken care of for me. I considered that for image hosting, or other static assets off of alternative origin relative to a website (not necessarily for a fully-fledged static website though, which I know there's another construct exists for)

The simplest pattern I've come up is this:

import { Bucket, Distribution, StackContext, use } from 'sst/constructs'

export function DataStack({ stack }: StackContext) {
  const notionBucket = new Bucket(stack, 'NotionBucket')

  const distribution = new Distribution(stack, 'NotionDistribution', {
    customDomain: staticDomain.value,
    cdk: {
      distribution: {
        comment: 'Static assets for a website',
        defaultBehavior: {
          // viewerProtocolPolicy: ViewerProtocolPolicy.HTTPS_ONLY,
          // allowedMethods: AllowedMethods.ALLOW_ALL,
          origin: new S3Origin(notionBucket.cdk.bucket),
        },
      },
    },
  })
  ...

Though, requires a bit of patching to work. But I hate patching, let's do it properly with author's confirmation