Reactive Resume - Self-Hosted Resume and CV Builder

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

## Overview

Reactive Resume is a free and open-source, privacy-friendly resume and CV builder. Create and maintain as many resumes and cover letters as you like, keep earlier versions, organise them with tags, preview changes live as you type, choose from a range of templates and typography, share a resume with a public link, and export a finished PDF - all from a modern web interface running inside your own AWS account rather than someone else's service. This AMI delivers Reactive Resume fully installed and secured so you can go from EC2 launch to building your first resume without editing a single configuration file.

## The Problem This Solves

Reactive Resume is a multi-service application: the web app, a PostgreSQL database and a Redis cache normally wired together by hand with container orchestration, a reverse proxy and a set of shared secrets. Teams report spending hours configuring Docker Compose files, generating secrets, setting up networking and troubleshooting first-boot failures. This image eliminates that entire process. It runs the official upstream release unmodified, pinned by digest, behind a single reverse proxy on port 80, and generates every secret uniquely on each instance's first boot.

## Who This Is For

• Careers services and universities: a private, self-hosted resume builder for students and jobseekers, keeping every resume and its earlier versions inside an account the institution controls rather than a third-party service
• Recruitment and outplacement agencies: consultants building, versioning and exporting polished PDF resumes for candidates, with public sharing links, on an instance they fully own
• Privacy-conscious individuals and teams: anyone who wants a modern resume builder with live preview, templates and PDF export without sending their personal history to a hosted service

## Application Stack

The Reactive Resume web application, a bundled PostgreSQL database and a bundled Redis cache each run as their own container, orchestrated on a private internal network and fronted by a single nginx reverse proxy on port 80. Neither PostgreSQL nor Redis is exposed to the network: they have no host port and are reachable only inside the private container network; the application binds to the loopback interface behind nginx. systemd starts the whole stack on boot. All application data - the database, the Redis data and uploaded resume PDFs, avatars and artboards - lives on a dedicated data volume, independently resizable and separate from the OS disk. PDF export is generated in-process, so there is no external rendering service to run.

## Security Hardening

This image follows a defence-in-depth approach:

• No default, shared or blank credentials: the session signing key, the encryption secret, the PostgreSQL password and the Redis password are generated uniquely on each instance's first boot, and a single owner account is seeded with a cryptographically random per-instance password written only to a root-only file
• Public sign-up disabled by default: open self-registration is switched off in the application itself (server-side, not a proxy trick) so a fresh public instance is not world-joinable, and can be re-enabled by the operator with a single documented setting
• Network isolation: PostgreSQL and Redis are never published to any host port; the application binds to loopback only; only the nginx reverse proxy on port 80 is reachable
• Empty database on capture: the captured image carries no database, no account, no uploaded file and no secret; every instance re-initialises a clean stack on first boot
• Dedicated data volume: the database, cache and uploads live on their own disk, surviving OS-disk changes and resizable independently
• Automatic restart: systemd supervises the whole stack and restarts it on failure

Buyers requiring formal compliance documentation should contact cloudimg to discuss specific requirements.

## AWS Integration

Deploy on any EC2 instance type. Put the reverse proxy behind an Application Load Balancer and terminate TLS with your own domain and certificate. Back up your database, cache and uploads using EBS snapshots or AWS Backup of the dedicated data volume, which you can resize independently of the OS disk as your resume library grows.

## Getting Started

1. Launch the AMI on your chosen EC2 instance type.

2. Read your unique owner credentials from the root-only file on the instance.

3. Open the web interface in your browser and sign in with the seeded owner account.

4. Create your first resume - add sections, choose a template and typography, preview live as you type.

5. Share a public link or export a PDF when ready.

6. To let a team self-register, enable public sign-up with a single documented setting.