ContextQMD
Back to Remotion

Bucket Security

packages/docs/docs/lambda/bucket-security.mdx

4.0.4632.0 KB
Original Source

Before Remotion Lambda, v4.0.418, buckets created with Remotion Lambda used a public-read ACL. This means that:

  • Items not explicitly made private (by setting the privacy option in renderMediaOnLambda()) are accessible to anyone.
  • People can "list" the buckets by visiting the bucket URL or using the AWS SDK

Risk

If you also accepted user uploads to the bucket, anyone could list the bucket and see user items.
If you did not set the privacy option for renders, anyone could list the bucket and see renders.

The new default<AvailableFrom v="4.0.418" />

From Remotion Lambda v4.0.418, the default is to not set an ACL, but to set a bucket policy:

  • Items not explicitly made private (by setting the privacy option in renderMediaOnLambda()) are only accessible if you know the URL.
  • People cannot "list" the buckets anymore.

This new default only applies for newly created buckets and only if you added the s3:PutBucketPolicy permission to your IAM user.
Existing buckets and new buckets created without the s3:PutBucketPolicy permission will continue to have a public-read ACL. s3:PutBucketPolicy is only available as part of getUserPolicy() since v4.0.418.

Recommendation

Since it is not required for the public to be able to list the bucket, we recommend disabling this to minimize exposure of your files.

For new buckets: Ensure you add s3:PutBucketPolicy to your IAM user policy (default only from v4.0.418, if upgrading, you need to manually update your user policy). Then create a bucket.

For existing buckets: Visit the bucket in the S3 console. Go to "permissions". Under Access control list, click Edit and remove List for Everyone.

See also