A storage connection is a bucket or a container, optionally one folder of it, and a way of signing in. A file in it can be added to a map as a layer, and files are read and written in a flow with "Cloud Storage Reader" and "Cloud Storage Writer". See Connect to Your Data for where to create a connection.
Amazon S3
| Field | What to enter |
|---|---|
| "Bucket" | The bucket's name. |
| "Region" | The bucket's region, for example us-east-1. |
| "Access key ID", "Secret access key" | An access key that can read the bucket. |
| "Folder" | Optional. Limits the connection to one folder. |
| "Service address" | Only for storage that works like Amazon S3 but is hosted elsewhere. Leave empty for Amazon S3. |
Google Cloud Storage
| Field | What to enter |
|---|---|
| "Service account key file" | The JSON key file of a service account that can read the bucket. |
| "Bucket" | The bucket's name. |
| "Folder" | Optional. Limits the connection to one folder. |
Azure Blob Storage
| Field | What to enter |
|---|---|
| "Storage account" | The storage account's name. |
| "Container" | The container's name. |
| "Folder" | Optional. Limits the connection to one folder. |
Choose one "Sign-in method":
- "Account key": one of the storage account's access keys.
- "Shared access signature": a signature that allows reading and listing the container. Add writing if flows will save files to it. A signature can be limited to one container and given an end date, which makes it the safer choice.
What the sign-in needs to be allowed to do
- To read: list the bucket or container and read its files.
- To write from a flow: also create and replace files.
How a folder limits a connection
When you set a "Folder", the connection reaches that folder and nothing outside it. The file list starts there, and a flow that names a file elsewhere in the bucket is refused. Use it to hand a flow one part of a shared bucket.
Reading and writing files
- "Cloud Storage Reader" reads one file, named by its path in the bucket or container. The formats are the ones Tamaat reads everywhere: see Supported File Types.
- "Cloud Storage Writer" writes the flow's result to the path you name, replacing a file that is already there. The file's extension picks the format.
Add a file to a map
In a map, add a layer, choose "Connect to source", then the connection, and browse to the file. Tamaat copies the file's data into the layer; "Refresh from source" reads the file again, so a file your own systems replace every night keeps its layer current.
One file becomes one layer. The formats are the ones listed in Supported File Types.