Import data from S3¶
Use S3 when the file is in Amazon S3 or compatible object storage such as MinIO.
S3
Convert
Destination
You need to be signed in. Saving the connection once is the usual path.
Before you start¶
You'll need:
- Bucket name
- Object key (the path of the file in the bucket)
- Access key and secret key
- Region (default
us-east-1if you are not sure) - Endpoint, only if you are not using AWS
1. Save the S3 Source¶
Open Sources → Add Source → S3.
Fill in:
| Field | What to enter |
|---|---|
| Name | Something you will recognize, such as Field Data S3 |
| Endpoint | Leave empty for AWS. For MinIO or similar, paste the host URL |
| Region | AWS region, or the region your provider expects |
| Bucket | Bucket name |
| Access key / Secret key | Credentials that can read the object |
| Use path-style addressing | Leave checked for MinIO and many S3-compatible servers |
Click Test, then Save.
The saved Source is the account and bucket. The object key belongs to each workflow.
2. Add S3 on the Canvas¶
Add S3, choose the saved Source, and enter the Key — for example incoming/neighborhoods.gpkg.
Click Import. GeoJibe downloads the object and inspects it.
You can also fill the connection in manually for a one-off import.
3. Make any changes and choose a Destination¶
Add Convert or Transform if needed, then Download, PostGIS, or another Destination.
4. Run¶
Click Run.
What happens next?¶
The object is copied into the workflow. Credentials stay on the saved Source; they are not stored on the converted file.
Having trouble?¶
- Test should say it reached the bucket before you Import
- Private endpoints can be blocked the same way private URLs are
- See Connection problems