
# Fedora Repository

Open-source preservation repository with an AWS Terraform deployment.

Canonical page: https://launchinyourcloud.com/directory/fedora-repository/
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.


## Fedora Repository

Open-source preservation repository with an AWS Terraform deployment.

- Listing: https://launchinyourcloud.com/directory/fedora-repository/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Package / binary installer
- Architecture: Fedora Repository application on EC2 with PostgreSQL in RDS.
- 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://wiki.lyrasis.org/display/FF/Fedora+Repository+Home
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.


### 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.

### Deployment boundaries


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


### Cloud deployment evidence

- fcrepo-aws-deployer (aws): https://github.com/fcrepo-exts/fcrepo-aws-deployer
  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.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

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

- Upstream project: https://github.com/fcrepo/fcrepo

### Sources

- fcrepo-aws-deployer: https://github.com/fcrepo-exts/fcrepo-aws-deployer

- Apache-2.0 LICENSE: https://github.com/fcrepo/fcrepo/blob/main/LICENSE

- GitHub Releases: https://github.com/fcrepo/fcrepo/releases

### Licensing sources

- https://github.com/fcrepo/fcrepo/blob/main/LICENSE

### Infrastructure sources

- https://github.com/fcrepo-exts/fcrepo-aws-deployer


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Sources checked — unresolved. 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. Scope: Fedora Repository application authentication; institutional front ends and external reverse-proxy integrations need their own configuration evidence. Source: https://github.com/fcrepo/fcrepo/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Community-maintained Fedora AWS deployment recipe; provider path and upstream application artifacts have separate versions. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/fcrepo-exts/fcrepo-aws-deployer/tree/master. Artifact reference: master (moving branch); select compatible Fedora, servlet-container and database versions. Supporting source: Upstream runtime packaging — https://github.com/fcrepo/fcrepo/blob/main/README.md.

- Minimum footprint / sizing: Documented. 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. Scope: Fedora community AWS recipe defaults, not a validated 1 TB repository or HA design. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Supporting source: Configurable recipe inputs — https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/variables.tf.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Fedora Repository; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/fcrepo/fcrepo/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Fedora Repository upstream application; verify compatibility with the selected package. Source: https://github.com/fcrepo/fcrepo/releases/tag/fcrepo-6.5.2 (reviewed 2026-11-19).






