Syncthing
Continuous peer-to-peer file synchronization between devices
Screenshot from verification · Click to enlarge
Application tests passed; AWS environment evidence comes from the referenced platform verification.
Before this version became the public one, it was checked on a real one-off AWS stack: admin area protection, data directory writable by the image user. This excludes full business acceptance and trusted TLS certificate issuance.
Quick Deploy
Deployment paused
Versions
View full version history| Versions | Verified At | Verified | Status | AWS Tested |
|---|---|---|---|---|
| v2.1.6 | Oct 6, 2026 | Deployment paused | Bug Fix | AWS · referenced |
| v2.1.5 | Sep 11, 2026 | Deployment paused | Initial | AWS · referenced |
Technical information
FAQ
How do I access Syncthing after deployment?
After CREATE_COMPLETE, run SSMPortForwardCommand from the stack Outputs in your local terminal and keep it running. Open http://localhost:8080 to initialize the application privately. Public access stays blocked until you explicitly enable HTTPS. The template restricts the GUI to localhost by default. Use SSM port forwarding to configure GUI access protection in Settings > GUI before widening AllowedWebCidr, and enable HTTPS for direct remote access. There are no preset accounts.
Where are application data and credentials stored?
Application data is mounted at /var/syncthing from the encrypted EBS data volume. The volume survives stack deletion and keeps billing; retention is not a backup. Platform proxy credentials and host configuration are on the root disk and are not included in a data-volume snapshot. See the backup guide before deleting anything.