[aws-s3-deployment] support for empty folder deployement

Description

With the following assets folder:

assets/ |----> FolderA/

Instantiate BucketDeployement has no effect.

new BucketDeployment(this, "DeployWebsite", {
      sources: [Source.asset("./assets")],
      destinationBucket: myBucket
    }); // no effect

What would be expected?

A bucket with the following structure:

Mybucket: |----> FolderA/

Use Case

required to generate folder-level access bucket policies

Proposed Solution

As a workaround, i use empty file to force BucketDeployement to render the folder structures And delete the empty file afterwards

assets/ |----> FolderA/ ---->emptyFiles.txt

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[tstibbs]

I personally think this is still a valid feature request. If someone wants to close it as “won’t ever get around to implementing this” then fair enough, but I don’t think the fact that it hasn’t seen any attention in the last year invalidates the requirement.

[moltar]

S3 has no concept of folders though. S3 is an object store. Each object is a blob, which is identified by a key. A folder is not an object or a blob. It’s a filesystem concept.

The folders are an illusion made by AWS Console. If you use / in the object key name, then the console will pretend the key paths are folders. But as far as the underlying protocol and APIs are concerned - there are no folders, just keys.

The workaround is super simple though. Create a dummy object: your-desired-dir/.keep.

You can do it directly from the Source class, without ever needing this file to exist on disk prior:

Source.data('your-desired-dir/.keep', '')