Apache Subversion (SVN) Server AMI by cloudimg

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

Apache Subversion (SVN) is the enterprise centralised version-control system: a single authoritative repository that stores every version of your files and directories, with atomic commits, branching and tagging, and fine-grained history. This AMI delivers Subversion fully installed and serving a ready-to-use repository over HTTPS, fronted by the Apache HTTP Server and the mod_dav_svn WebDAV module, so your version-control server is answering within minutes of launch.

Setting up SVN from scratch means installing packages, configuring Apache with mod_dav_svn, generating TLS certificates, creating authentication files, provisioning storage, and hardening defaults - a process that can take hours and leaves room for misconfiguration. This AMI eliminates that effort entirely. Unlike a default install where anonymous access is often left open, every instance enforces authentication from the first second. Unlike hosted version-control services, your repository stays in your own AWS account with no vendor lock-in. You get a production-hardened deployment without the operational overhead.

The repository is served over HTTPS on port 443 by Apache with mod_dav_svn and mod_authz_svn. A fresh empty FSFS repository is provisioned at /srv/svn/repo on a dedicated data disk, owned by the Apache service account so commits are written safely. All repository access requires authentication - there is no anonymous read or write. An unauthenticated static health endpoint answers on the same server for load-balancer and uptime checks, and plain HTTP on port 80 serves a landing page and redirects repository clients to HTTPS.

Check out a working copy, add and edit files, and commit atomically to a central history that every member of your team shares. Create branches and tags, review the full revision log, and roll back to any earlier revision. Point your existing Subversion clients and CI tooling at a single repository URL for both checkout and commit.

On the first boot of your instance a one-shot service generates a fresh repository password unique to that instance, generates a per-instance self-signed TLS certificate, writes the bcrypt-hashed password into the Apache authentication file, and records the plaintext in a file only the root user can read. No shared or default credentials or certificates ship in the image, and the server proves the authentication gate and a full commit round-trip before it reports ready.

SSH in, read the generated credentials, and check out the repository with the standard svn client straight away. The repository store lives on a dedicated, independently resizable data disk. For production, replace the self-signed certificate with a CA-signed one as described in the deployment guide. You can launch on a small instance to evaluate the workflow and scale up as your team grows - terminate at any time with no commitment.

• Regulated enterprises managing hardware design files - teams in aerospace, automotive or semiconductor industries that require locked checkouts and full audit trails for binary assets can centralise controlled documents in a single governed repository.
• DevOps teams running many concurrent CI pipelines - a dedicated SVN server in your VPC eliminates network latency to external hosts and gives pipelines reliable, low-latency checkout for build reproducibility at scale.
• Organizations migrating on-premises SVN to AWS - lift your existing repository into your own account without changing client workflows, maintaining the same https access patterns your developers already use.

24/7 technical support by email and chat. Help with deployment, repository layout and access control, TLS certificate replacement, client and CI integration, storage sizing, backup and upgrade planning.

Apache, Apache Subversion and the Apache feather logo are trademarks of the Apache Software Foundation. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.