...
- s3:PutObject
- s3:GetObject
- s3:DeleteObject
- s3:ListBucket
- s3:AbortMultipartUpload
Database
The OCFL library used by Fedora uses the same database as that used by Fedora for locking and caching OCFL object details. This is necessary to solve eventual consistency and concurrency issues. Like the other database tables used by Fedora, all information in the database serves as a cache and will be automatically repopulated if deleted.NOTE: Currently, the only supported databases in the underlying OCFL library are PostgreSQL and H2; therefore, in order to use Fedora's S3 feature, Fedora's must be configured to either use PostgreSQL (production) or H2 (test)will by default cache OCFL object details in the database. It only supports PostgreSQL. If you are not using PostgreSQL or do not want to use the database cache, then you can disable it by setting fcrepo.ocfl.s3.db.enabled to false.
Configuration
AWS Credential Configuration
The credentials used to interact with S3 must be available to Fedora per Amazon's guidelines. You can optionally specify them explicitly by setting fcrepo.aws.access-key and fcrepo.aws.secret-key.
Fedora Configuration
The following configuration items are passed to the Fedora application on startup via system properties.
...
| Code Block |
|---|
-Dfcrepo.ocfl.s3.prefix=<some-prefix> |
Non-AWS S3 Implementations
The S3 integration should work with non-AWS S3 implementations, but you should test it to make sure it works as expected. In addition to the standard configuration options, you can specify a custom endpoint using fcrepo.s3.endpoint and enable path-style access, if your implementation requires it, using fcrepo.s3.path.style.access.