Exports that feed reporting
Files your systems already export to S3, like account lists or project reports, feed dashboards and reports without anyone downloading them first.
Go Fig reads CSV, Parquet, and JSON files straight from your Amazon S3 bucket, so exports and file-based data feed the same reports as everything else.
Plenty of business data never reaches a database. It lands in Amazon S3 as exports, nightly files, or output from systems with no direct connection. Your data team connects the bucket once with a solutions engineer. Go Fig reads the files straight from the bucket, doesn't copy them into its own storage, and never changes them. Those files then become part of your data foundation next to every other system you connect, feeding dashboards, scheduled reports, and Celeste, Go Fig's AI analyst. A new file in the bucket is what Go Fig sees the next time it looks.
Files your systems already export to S3, like account lists or project reports, feed dashboards and reports without anyone downloading them first.
If your team keeps years of history in S3 as a data lake (a store of raw files), Go Fig reads it in place next to live data from your other systems.
Go Fig reads the files straight from your bucket, so a new export is what it sees the next time it looks.
In AWS, your data team creates an access key ID and secret access key (a login meant for software, not a person) for Go Fig to use.
They let that key read the bucket Go Fig should use and nothing more, so it can look at the files but never change them.
With your solutions engineer, they add the bucket name, its region, the access key ID, and the secret access key.
Confirm Go Fig can see the files you expect. From then on, Go Fig reads them straight from the bucket each time they are used.
CSV, Parquet, and JSON files in the bucket you connect.
No. The files stay in your S3 bucket and Go Fig reads them there. To find the right data, its search index keeps field names, descriptions, and a few sample rows, as our security page explains.
Go Fig reads the files where they sit each time they are used, so a new file in the bucket is what Go Fig sees next.
No. The connection is read only. Go Fig reads files from the bucket and never changes them.
The bucket name, the region it lives in, and an access key ID and secret access key that can read it.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.