Archives & collections management on AWS
Archival description, accessions, digital collections and researcher access.
10 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Arches | AWS | Customer-operated Servers / containers | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Source / language package | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe AWS deployment guide covers the application, while the S3 guide covers media storage. Mentions of storage on other providers do not establish corresponding application installs. Heritage-resource inventories are distinct from complete archival accession and records-disposition workflows.
Cloud evidence reviewed 2026-11-19 |
| Archivematica | AWS | Customer-operated Servers / containers | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe AWS implementation is maintained by Wellcome Collection. It is an institutional deployment pattern rather than an upstream support commitment. Preservation outputs, access interfaces and storage/recovery policies require separate configuration.
Cloud evidence reviewed 2026-11-19 |
| ArchivesSpace | AWS | Customer-operated Servers / containers | Open Source / Open Core Open source; optional membership/support services | Docker or ZIP distribution with production MySQL and required search/runtime services | Customer operates the application, production database, search services and backups.Scope and evidenceThe project documents Docker and ZIP installations. Its FAQ explicitly distinguishes archival description from managing digital files or digitization workflows. Provider-specific deployment support was not verified.
Cloud evidence reviewed 2026-11-12 |
| Avalon Media System | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceAvalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
Cloud evidence reviewed 2026-11-19 |
| Dataverse Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache-2.0 application; dependencies and dataset reuse licenses are separate. | Official installer and AWS EC2 creation script; follow the production installation/configuration and upgrade guides for the selected release. | Institution operates application and infrastructure, permissions, persistent identifiers, database/files, backups, monitoring and upgrades. External identity, citation and analysis services require configuration.Scope and evidenceReview used 6.12.1; Docker users need the corrected 6.12.1-noble-r3 image or newer described by upstream. The AWS developer script creates the full application but is not a production hardening shortcut. Configure HTTPS, restricted APIs, database/file recovery and appropriate sensitive-data controls before opening access. This is unrelated to Microsoft Dataverse.
Cloud evidence reviewed 2026-11-13 |
| DSpace Self-Hosted | AWS | Customer-operated Servers / containers | Open Source / Open Core BSD-3-Clause core; dependencies and optional commercial hosting/support have separate terms. | Matched official backend and Angular frontend releases with PostgreSQL/Solr; an AWS/JHU reference describes deployment on ECS/Fargate. | Institution manages the application releases, collection permissions, metadata, storage, backups and upgrades. AWS can operate container compute through Fargate; the institution still operates its repository services.Scope and evidenceReview used backend/frontend 10.1. Follow the current installation guide for runtime and database/search compatibility; protect Solr from public access and enable HTTPS. The Johns Hopkins AWS case study demonstrates an institutional deployment, not a turnkey installer or a blanket upstream cloud-support commitment. External identity, analytics and scholarly integrations are operator choices.
Cloud evidence reviewed 2026-11-13 |
| Fedora Repository | AWS | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Terraform; Package / binary installer | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceThe repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
Cloud evidence reviewed 2026-11-19 |
| FormKiQ Archives and Collections ManagementDirectory Publisher | AWS | Customer-operated Serverless | Commercial Only Commercial FormKiQ Advanced or Enterprise; confirm required extensions | Configure the solution in a FormKiQ deployment; CloudFormation installs the platform. | Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.Scope and evidenceThis is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.
Cloud evidence reviewed 2026-11-12 |
| InvenioRDM | AWS | Customer-operated Servers / containers | Open Source / Open Core MIT application code; framework modules, institutional customizations and dependencies retain their own terms. | Official Invenio CLI and production deployment guidance; Caltech publishes its customized AWS EC2 setup and configuration. | Institution operates application and workers, identity, search, data services, configuration, backups and upgrades. Cloud resources are separate from the public Zenodo hosted service.Scope and evidenceThe upstream project identifies v14. Caltech documents its own EC2 deployment and earlier release-specific setup, not universal v14 compatibility. Follow current upstream production requirements and review the institution-specific files before reuse. Docker Compose reference defaults require production adaptation. External DOI, identity, mail and analytics services have separate data boundaries.
Cloud evidence reviewed 2026-11-13 |
| Omeka S | AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock | Customer-operated Servers / containers | Open Source / Open Core GPLv3 application; the packaged OIDC module is GPL-3.0-or-later. | Cloudron package on a customer VM; upstream also documents a PHP/MySQL installation. | Customer manages collection access, researcher/editor roles, modules and themes, mail, database and file backups, restoration and coordinated upgrades.Scope and evidenceReviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.
Cloud evidence reviewed 2026-11-13 |
Deployment evidence and category fit
Arches
Open-source cultural-heritage inventory and resource-information platform.
The AWS deployment guide covers the application, while the S3 guide covers media storage. Mentions of storage on other providers do not establish corresponding application installs. Heritage-resource inventories are distinct from complete archival accession and records-disposition workflows.
- Arches AWS EC2 Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Arches application on EC2, PostgreSQL/PostGIS and separately configured media storage. The AWS deployment guide covers the application, while the S3 guide covers media storage. Mentions of storage on other providers do not establish corresponding application installs. Heritage-resource inventories are distinct from complete archival accession and records-disposition workflows.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Archivematica
Open-source digital-preservation processing system with an institutional AWS deployment recipe.
The AWS implementation is maintained by Wellcome Collection. It is an institutional deployment pattern rather than an upstream support commitment. Preservation outputs, access interfaces and storage/recovery policies require separate configuration.
- Wellcome Terraform ↗
Institution deployment · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Wellcome Collection's Terraform-managed application services, databases and preservation storage. The AWS implementation is maintained by Wellcome Collection. It is an institutional deployment pattern rather than an upstream support commitment. Preservation outputs, access interfaces and storage/recovery policies require separate configuration.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
ArchivesSpace
Dedicated archival description and collections management with finding aids and digital-object metadata. ArchivesSpace describes and links digital objects; it is not a DAM, file repository or digitization workflow system.
The project documents Docker and ZIP installations. Its FAQ explicitly distinguishes archival description from managing digital files or digitization workflows. Provider-specific deployment support was not verified.
- ArchivesSpace community Terraform deployment on AWS ECS ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
This maintained community Terraform module deploys ArchivesSpace as an ECS service on Fargate or EC2, with an Nginx proxy, database setup and EFS persistence. The inspected complete example uses upstream ArchivesSpace and Solr images plus RDS and load balancing. This is a community-maintained deployment recipe, not an upstream support commitment; pin compatible application/Solr/database versions and review secrets, storage, networking and upgrades.
- Complete AWS infrastructure example for the ArchivesSpace module ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected example provisions the supporting VPC, ECS, EFS, RDS, load-balancer and service-discovery resources in the Terraform caller's AWS account. It references official archivesspace/archivesspace and archivesspace/solr images. Adapt example domain names, image tags, sizing and access controls to the actual deployment.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Avalon Media System
Open-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
- avalon-terraform ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Avalon application and media-processing/storage services provisioned by the project's Terraform scripts. Avalon application versions and turnkey Terraform versions are separate. Confirm current media-processing dependencies, storage policies and institutional access controls before production use.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Dataverse Self-Hosted
Preserves and publishes research datasets in metadata-rich collections with persistent identifiers and access controls. It is a research-data repository, not grant-application or sponsored-award administration software.
Review used 6.12.1; Docker users need the corrected 6.12.1-noble-r3 image or newer described by upstream. The AWS developer script creates the full application but is not a production hardening shortcut. Configure HTTPS, restricted APIs, database/file recovery and appropriate sensitive-data controls before opening access. This is unrelated to Microsoft Dataverse.
- Upstream AWS EC2 deployment script and instructions ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The project documents AWS credential/role setup and a script that creates an EC2 instance with the Dataverse application, browser access and cleanup steps in the operator account. It is developer-oriented and warns about branch/dependency compatibility. Pair it with the supported-release production installer, hardening and backup guidance.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
DSpace Self-Hosted
Manages institutional and digital collections with deposit, metadata, access and discovery for scholarly and cultural material. Repository preservation is distinct from grant administration or a general enterprise records policy engine.
Review used backend/frontend 10.1. Follow the current installation guide for runtime and database/search compatibility; protect Solr from public access and enable HTTPS. The Johns Hopkins AWS case study demonstrates an institutional deployment, not a turnkey installer or a blanket upstream cloud-support commitment. External identity, analytics and scholarly integrations are operator choices.
- Johns Hopkins institutional DSpace deployment on AWS ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS and the Johns Hopkins authors describe the library team migrating and operating JScholarship on ECS/Fargate with cloud backing services. This establishes application hosting by an adopting institution, not a vendor-hosted subscription or upstream support certification. Adapt the architecture to the selected release and operational requirements.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Fedora Repository
Open-source preservation repository with an AWS Terraform deployment.
The repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
- fcrepo-aws-deployer ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Fedora Repository application on EC2 with PostgreSQL in RDS. The repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
FormKiQ Archives and Collections Management Directory Publisher
Archival description, accessions, digital collections and researcher access.
This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.
- FormKiQ commercial AWS installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12 · Scope: FormKiQ platform; solution configuration and entitlement must be agreed separately. Vendor support commitment: not assessed; confirm the selected release and contract.
The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
InvenioRDM
Provides institutional and research-data repositories with deposit, curation, metadata, access and dissemination. Research-data repository functions do not establish grant administration or clinical regulatory-document control.
The upstream project identifies v14. Caltech documents its own EC2 deployment and earlier release-specific setup, not universal v14 compatibility. Follow current upstream production requirements and review the institution-specific files before reuse. Docker Compose reference defaults require production adaptation. External DOI, identity, mail and analytics services have separate data boundaries.
- CaltechAUTHORS institutional AWS EC2 deployment ↗
Institution deployment · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Caltech Library documents running its customized InvenioRDM repository on AWS EC2 with Ubuntu, application installation and S3 configuration. This is an institution-maintained deployment example, not a stock v14 installer or CERN support commitment. Replace institutional values and reconcile runtime, dependencies, secrets and upgrades with the chosen current release.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Omeka S
Describes digital collection items and media with shared metadata, item sets, linked data and independently curated public exhibits. This does not establish formal retention or legal-hold controls.
Reviewed Cloudron 1.6.1 contains Omeka S 4.2.1 and OIDC module 1.2.0, whose declared compatibility covers Omeka S 4.x. The current package uses OIDC although its package manual still describes LDAP. Change initial administrator credentials, review identity/account linking and researcher defaults, and check extension compatibility before upgrades. Preserve the database, configuration, collection files, modules and themes. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.
- Cloudron EC2 AMI and application installation ↗
Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Omeka S 4.2.1 is available as Cloudron package 1.6.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Deployment and procurement checks
- Private offers
- AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service. Provider source ↗ · Reviewed 2026-11-14
- Cross-account operations
- Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access. Provider source ↗ · Reviewed 2026-11-14
- Government environments
- AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: AWS account. Access: IAM roles and policies. Network: VPC.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings