Fedora Repository
Open-source preservation repository with an AWS Terraform deployment.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Terraform; Package / binary installer
Runs in
Documented customer environment
Fedora Repository application on EC2 with PostgreSQL in RDS.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
fcrepo-aws-deployer ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Terraform; Package / binary installer |
|---|---|
| Infrastructure | Servers / containers Fedora Repository application on EC2 with PostgreSQL in RDS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed Fedora deployment material identifies servlet-container/application security, but does not establish a version-matched external SAML/OIDC login configuration for the repository. A Java authentication library or cloud account IAM alone is not sufficient evidence of a supported user-federation path.
Fedora Repository application authentication; institutional front ends and external reverse-proxy integrations need their own configuration evidence · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The Fedora community publishes a Terraform AWS deployer for the application and RDS, while upstream publishes WAR artifacts for a servlet container. The Terraform inputs and application/server versions must be matched; review its example database/instance defaults rather than treating the recipe as a current production or HA certification.
Community-maintained Fedora AWS deployment recipe; provider path and upstream application artifacts have separate versions · Source ↗ · Deployment artifact ↗ (master (moving branch); select compatible Fedora, servlet-container and database versions) · Upstream runtime packaging ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The community AWS recipe defaults to a t3.small application instance and a small RDS database with a 10 GB allocation. These configurable example values do not establish a production minimum; verify currently supported database classes/engine versions, repository-object storage, index/load growth, backups and redundancy separately.
Fedora community AWS recipe defaults, not a validated 1 TB repository or HA design · Source ↗ · Configurable recipe inputs ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Fedora Repository; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream fcrepo-6.5.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Fedora Repository upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & maintenance
The reviewed upstream contributor history includes cbeer, ajs6f, whikloj, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Archives & collections management
- Open-source preservation repository with an AWS Terraform deployment.
- Document management
- Open-source preservation repository with an AWS Terraform deployment.
Compare within Archives & collections management
- ArchesOpen-source cultural-heritage inventory and resource-information platform.
- AWS
- ArchivematicaOpen-source digital-preservation processing system with an institutional AWS deployment recipe.
- AWS
- ArchivesSpaceSelf-hosted archival description and collections management with searchable finding aids.
- AWS
- Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
- BrowsertrixOpen-source browser-based web archiving and collection-management application.
- DigitalOcean
- Dataverse Self-HostedInstitutional research-data repository for dataset preservation, metadata, access and citation.
- AWS
- DSpace Self-HostedInstitutional digital repository for scholarly works, datasets and cultural collections.
- AWS
- FormKiQ Archives and Collections Management Directory PublisherConnect archival description, linked metadata, digital collections, curated exhibits, and controlled researcher access in your AWS environment.
- AWS
Showing 8 of 11 other listings in Archives & collections management. These products address related workflows; read their category-fit notes before comparing scope. See all of Archives & collections management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- fcrepo-aws-deployer ↗github.com
- Apache-2.0 LICENSE ↗github.com
- GitHub Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- fcrepo-aws-deployer ↗ · AWS
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.
- fcrepo-aws-deployer ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com