Nightly backup of Sentra 311
Every night, all 311 requests are copied to a dated JSON file in the city's S3 bucket.
Amazon S3 and S3-compatible storage such as MinIO and Wasabi hold backups, exports and archives for many city IT teams. A bucket the city controls is a simple, cheap place to keep plain copies of important data.
SentraBridge reads files from a bucket, writes new ones and archives processed files. Typical flows write nightly JSON or CSV backups of cloud systems into the city's own bucket. The backup lives in your storage; SentraBridge keeps only counts and file names.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Files | CSV, JSON, JSON Lines, XML, fixed-width, ACH, BAI2, GeoJSON, Shapefile | write files (including positive pay), transfer documents | yes (new files) | Columns from the file |
Every night, all 311 requests are copied to a dated JSON file in the city's S3 bucket.
A permits table is exported nightly to a dated CSV, so there's always a plain-text copy outside the database.
Records from several systems are written as JSON Lines under one prefix for the analytics team.
Self-hosted cities write exports to their own MinIO server with the same S3 settings.
Systems cities commonly connect with Amazon S3, each with its own connector page.
Yes. A scheduled flow reads all or changed records and writes a dated JSON or CSV file to your bucket. Templates exist for 311 and database backups.
Yes. Any S3-compatible storage works; set its endpoint address in the connection.
ListBucket, GetObject, PutObject and DeleteObject, limited to the bucket and prefix flows use.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.