
# Archivematica

Open-source digital-preservation processing system with an institutional AWS deployment recipe.

Canonical page: https://launchinyourcloud.com/directory/archivematica/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Archivematica

Open-source digital-preservation processing system with an institutional AWS deployment recipe.

- Listing: https://launchinyourcloud.com/directory/archivematica/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: Wellcome Collection's Terraform-managed application services, databases and preservation storage.
- Operations: 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.
- Product website: https://github.com/wellcomecollection/archivematica-infrastructure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Wellcome Collection's Terraform-managed application services, databases and preservation storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source digital-preservation processing system with an institutional AWS deployment recipe.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/wellcomecollection/archivematica-infrastructure (checked 2026-11-19). 


### Cloud deployment evidence

- Wellcome Terraform (aws): https://github.com/wellcomecollection/archivematica-infrastructure
  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.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mcantelon, Hwesta, sevein, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/artefactual/archivematica/graphs/contributors

- Upstream project: https://github.com/artefactual/archivematica

### Sources

- Wellcome Terraform: https://github.com/wellcomecollection/archivematica-infrastructure

- Bootstrap Docs: https://docs.wellcomecollection.org/archivematica/administering-archivematica/bootstrapping

- AGPL-3.0 LICENSE: https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE

- GitHub Releases: https://github.com/artefactual/archivematica/releases

### Licensing sources

- https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE

### Infrastructure sources

- https://github.com/wellcomecollection/archivematica-infrastructure


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The 1.18 security guide documents Shibboleth and CAS user authentication for both Dashboard and Storage Service, with separately configured backends. OIDC is also described but explicitly experimental. These login paths are distinct from pipeline/API service credentials. Scope: Versioned Dashboard/Storage Service federation; retain the OIDC experimental qualification. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/security/security/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The 1.18 installation guide documents supported dependency/package installation and links advanced Ansible deployment options. Choose matching Dashboard, Storage Service and dependency versions and configure processing/storage locations, secrets and backups. Institutional AWS Terraform examples have their own maintenance and version scope. Scope: Official package/automation installation workflow; not a claim that every historical institutional stack supports the current release. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/installation-setup/installation/installation/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The 1.18 guide recommends a viable production minimum of 2 CPU cores, 4 GB RAM and 200 GB processing disk, with 8 cores/16 GB more commonly deployed. It separately recommends 20 GB plus four times the largest transfer for processing space; source and archival storage, media type and concurrency change requirements. Scope: Production processing guidance; archival retention storage and HA replicas are additional. Source: https://www.archivematica.org/en/docs/archivematica-1.18/admin-manual/installation-setup/installation/installation/ (reviewed 2026-11-21).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Archivematica; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/artefactual/archivematica/blob/qa/1.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v1.18.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Archivematica upstream application; verify compatibility with the selected package. Source: https://github.com/artefactual/archivematica/releases/tag/v1.18.0 (reviewed 2026-11-19).






