Mongo/S3 Content Storage
There is an implementation of the IContentStorage interface that uses MongoDB to store the parameters and metadata of content objects and a S3-compatible storage system to store files (images, video, audio etc.). You can find it at /packages/h5p-mongos3/src/MongoS3ContentStorage.ts.
Note: You must create the S3 bucket manually before it can be used by MongoS3ContentStorage!


The implementation depends on these npm packages:
  • aws-sdk
  • mongodb
You must add them manually to your application using npm install aws-sdk mongodb!


You must import the storage implementation via a submodule:
import { MongoS3ContentStorage, initS3, initMongo } from '@lumieducation/h5p-mongos3';
or in classic JS style:
const { MongoS3ContentStorage, initS3, initMongo } = require('@lumieduation/h5p-mongos3');
Initialize the storage implementation like this:
const storage = new MongoS3ContentStorage(
accessKeyId: 's3accesskey', // optional if env. variable is set
secretAccessKey: 's3accesssecret', // optional if env. variable is set
endpoint: '', // optional if env. variable is set
s3ForcePathStyle: true,
signatureVersion: 'v4'
( await initMongo(
'mongodb://', // optional if env. variable is set
'testdb1', // optional if env. variable is set
'root', // optional if env. variable is set
'h5pnodejs' // optional if env. variable is set
{ s3Bucket: 'h5pcontentbucket' }


  • The function initS3 creates an S3 client using the aws-sdk npm package.
  • The function initMongo creates a MongoDB client using the mongodb npm package.
  • You can pass credentials and other configuration values to initS3 and initMongo through the function parameters. Alternatively you can use these environment variables instead of using the function parameters:
  • You can change the MongoDB collection name h5p to any name you want. If the collection doesn't exist yet, it will be automatically created.
  • You can change the bucket h5pcontentbucket to any name you want, but you must specify one. You must create the bucket manually before you can use it.
  • The configuration object passed into initS3 is passed on to aws-sdk, so you can set any custom configuration values you want.
  • To achieve greater configurability, you can decide not to use initS3 or initMongo and instantiate the required clients yourself.
  • While Amazon S3 supports keys with up to 1024 characters, some other S3 systems such as Minio might only support less in certain situations. To cater for these system you can set the option maxKeyLength to the value you need. It defaults to 1024.

Using MongoS3ContentStorage in the example

The example Express application can be configured to use the MongoDB/S3 storage by setting the environment variables from above and these additional variables:
An example call would be:

Customizing permissions

By default the storage implementation allows all users read and write access to all data! It is very likely that this is not something you want! You can add a function to the options object of the constructor of MongoS3ContentStorage to customize access restrictions:
getPermissions = (
contentId: ContentId,
user: IUser
) => Promise<Permission[]>;
The function receives the contentId of the object that is being accessed and the user who is trying to access it. It must return a list of permissions the user has on this object. Your implementation of this function will probably be an adapter that hooks into your rights and permission system.

Increasing scalability by getting content files directly from S3

In the default setup all resources used by H5P content in the player (images, video, ...) will be requested from the H5P server. The H5P server in turn will request the resources from S3 and relay the results. This means that in a high load scenario, there will be a lot of load on the H5P server to serve these static files. You can improve scalability by setting up the player to load content resources directly from the S3 bucket. For this you must grant read access on the bucket to anonymous users. If you have content that must not be accessible to the public (for e.g. copyright reasons), this is probably not an option.
This currently only works for the player, not for the editor. Because of this you must still serve the 'get content file' route to make sure the editor can work with resources correctly.
  1. 1.
    Grant read-only permission to anonymous users for your bucket with bucket policies. See the AWS documentation for details.
  2. 2.
    Set the configuration option contentFilesUrlPlayerOverride to point to your S3 bucket. The URL must also include the contentID of the object. For this, you must add the placeholder {{contentId}} to the configuration value. Examples:
contentFilesUrlPlayerOverride = '{{contentId}}';
// or
contentFilesUrlPlayerOverride = '{{contentId}}';

Developing and testing

There are automated tests in /test/implementation/db/MongoS3ContentStorage.test.ts. However, these tests will not be called automatically when you run npm run test or other test calls. The reason is that the tests require a running MongoDB and S3 instance and thus need more extensive setup. To manually execute the tests call npm run test:db.
To quickly get a functioning MongoDB and S3 instance, you can use the Docker Compose file in the scripts directory like this (you obviously must install Docker and Docker Compose first):
docker-compose -f scripts/mongo-s3-docker-compose.yml up -d
This will start a MongoDB server and MinIO instance in containers. Note that the instances will now be started when your system boots. To stop them from doing this and completely wipe all files from your system, execute:
docker-compose -f scripts/mongo-s3-docker-compose.yml down -v
The MinIO instance will not include a bucket by default. You can create one with the GUI tool "S3 Browser", for example, or with the AWS CLI.