Foundry Virtual Tabletop features integrated support for AWS S3 file storage which lets you use an AWS account and S3 buckets as a built-in browseable and uploadable storage location for media assets that are used within Foundry VTT. To enable this functionality, you must include an entry in your options.json config file which points towards another JSON file that contains your AWS credentials. If such a file is correctly specified and the AWS user has permission to access S3 buckets, those buckets will be available for use in the File Browser for players who are allowed to use it.

How To Enable S3 Support

Add an entry in the Config/options.json config file which exists in your user data location to include key "awsConfig" which provides a relative or absolute file path pointing to another JSON file contraining the following:

  "accessKeyId": "YOUR_ACCESS_KEY_ID",
  "secretAccessKey": "YOUR_SECRET_ACCESS_KEY",

Note that the AWS config file may also include other parameters which are passed to the S3 constructor as described by the JavaScript SDK documentation including options to support a custom endpoint for working with other S3-compatible services.

Take care how you name your S3 Bucket, don't use "." (dot) in the naming as it will break the HTTPS certificate, more info is provided here: AWS S3 VirtualHosting.

How To Restrict Bucket Permissions

You may not wish to allow your AWS account to access all S3 buckets from within Foundry VTT. To avoid this, you should create a specific IAM user whose access credentials are used by Foundry Virtual Tabletop. You can assign am IAM policy to this specific user which only permits access to certain buckets within your overall account. An example IAM policy which allows access to only the bucket named vtt-assets is shown below:

    "Version": "2012-10-17",
    "Statement": [
            "Effect": "Allow",
            "Action": "s3:ListAllMyBuckets",
            "Resource": "*"
            "Effect": "Allow",
            "Action": [
            "Resource": [

This policy allows the AWS user to list all of the available buckets (but not to see their contents unless specifically allowed) - this permission is important so the Foundry VTT software can discover which buckets may be used. It also allows permission to list the contents of a specific bucket or buckets, in this case the vtt-assets bucket. Lastly - it allows permission to read and write objects from that same vtt-assets bucket. This policy can be modified to allow access to a different set of buckets depending on your use case and needs.

For more information, see the following AWS support page:

Enabling User Access

The permission controls on your AWS bucket are used to restrict the ability to upload content only. To use uploaded content in a game session, all players must have access to read the files in your bucket. You can either accomplish this by making your entire bucket public access, specifically assigning a public-read ACL to each uploaded key (the Foundry uploader does this automatically), or by specifically authorizing individual IP addresses of your players for the bucket.

Enabling Cross-Origin Resource Sharing (CORS)

In order to use assets out of your S3 bucket from the virtual tabletop - you may need to set a CORS policy. To do this, navigate to the Permissions tab on the S3 bucket management panel. Under the CORS configuration section apply the following policy:

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="">

For more information, see the following AWS support page: