Syncthing Peer-to-Peer File Sync AMI | Support by cloudimg

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

Syncthing is the popular open source continuous file synchronization program. It synchronizes files between two or more devices over an encrypted, authenticated connection with no central server or third-party intermediary. This AMI delivers Syncthing fully installed and hardened so your private sync node is operational within minutes of launch - no manual compilation, configuration, or credential setup required.

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

Deploying Syncthing from scratch on a bare EC2 instance requires installing dependencies, configuring systemd services, setting up a reverse proxy, generating TLS certificates, and hardening credentials - typically 30-60 minutes of engineering time per node. This image eliminates that effort entirely. Unlike hosted sync services such as Dropbox, your data never passes through a third-party server, keeping sensitive files under your sole control.

A development team with members across multiple AWS regions needs build artifacts, configuration files, and documentation synchronized without relying on a centralized cloud storage provider. Deploy this Syncthing node in your VPC, pair it with Syncthing clients on developer workstations and other EC2 instances, and files stay in sync automatically over encrypted peer-to-peer connections - no egress through third-party services required.

The Syncthing GUI and REST API run as a single Go binary behind nginx as a reverse proxy. The sync protocol listens on port 22000 (TCP/UDP). The GUI binds to the loopback interface and is accessible through the nginx proxy. The underlying OS is managed via systemd for reliable service lifecycle control. The current release is Syncthing 2.1.

• Amazon EBS: Attach persistent EBS volumes to store synced data independently of instance lifecycle. Resize storage as your sync folders grow without rebuilding the node.
• AWS Security Groups: Open port 22000 for the Syncthing protocol and your chosen HTTPS port for GUI access. All other ports remain closed by default.
• Amazon CloudWatch: Forward system and application logs for centralized monitoring and alerting on sync health.
• AWS Systems Manager: Use Session Manager for secure shell access without exposing SSH ports publicly.

On first boot, a one-shot systemd service regenerates the device certificate (creating a fresh, unique Device ID), the REST API key, and the administrator GUI password. These credentials are written to a root-only file. No shared or default credentials ship in the image. Unlike AMIs that reuse a single device identity across all subscribers, every instance you launch has a cryptographically distinct identity from the moment it starts.

1. Launch the AMI in your preferred AWS region.
2. Retrieve your unique GUI password from the root-only credentials file.
3. Sign in to the Syncthing web GUI through the nginx reverse proxy.
4. Add folders you want to sync and the Device IDs of your other Syncthing nodes.
5. Install the Syncthing client on your other machines and pair them with this node.

Syncthing keeps paired devices in sync automatically with no further intervention.

cloudimg provides round-the-clock technical support by email and live chat covering deployment, upgrades, device pairing, TLS termination, and storage configuration. Critical issues receive a one-hour average response time.

Syncthing is a trademark of its respective owner. 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.