- Read CSV, JSON, and other data files from S3 buckets
- List and browse objects in a bucket with prefix filtering
- Integrate external data sources into your Lovable app
- Access batch data exports from enterprise data pipelines
Common use cases and example apps
| Example app | Example prompt | Description |
|---|---|---|
| Data explorer | Build a data explorer that lists files in my S3 bucket and lets me preview CSV and JSON files. | Browse and preview files stored in S3 without leaving your app. The app lists objects in the bucket and renders previews of supported file formats inline. |
| Analytics dashboard | Build a dashboard that reads a daily export CSV from S3 and shows charts for revenue and user signups. | Turn S3 data exports into live dashboards. The app reads the latest export file from your bucket and visualizes key metrics automatically. |
| Report viewer | Build an internal report viewer that loads JSON reports from S3 and displays them in a searchable table. | Give your team a clean interface to browse reports. The app pulls JSON files from a specific S3 prefix and renders them as filterable, sortable tables. |
| File download portal | Build a file download portal where users can browse and download files from our shared S3 bucket. | Create a simple self-service file access layer on top of S3. The app lists available files and lets users download them directly, without needing AWS console access. |
| Data pipeline monitor | Build a tool that checks my S3 bucket for new data files and shows when each pipeline last wrote output. | Monitor data pipeline health by tracking file freshness. The app lists objects by prefix and surfaces the last-modified timestamps so you can spot stale or missing exports. |
How AWS S3 connections work
Each AWS S3 connection is tied to a single S3 bucket. When you connect AWS S3, you provide IAM credentials with read access to that bucket. Within your Lovable workspace:- You can create multiple AWS S3 connections.
- Each connection targets a specific bucket and AWS region.
- Each connection uses its own IAM credentials.
- Multiple projects within a single workspace can use the same connection.
The AWS S3 connector provides read-only access. Your app can list and download objects but cannot upload, modify, or delete files in the bucket.
How to connect AWS S3
Workspace admins and owners can connect AWS S3. When a connection is created, the S3 bucket becomes available across all projects in the workspace.Prerequisites
Before connecting AWS S3, make sure you have:- An AWS account with access to the S3 bucket you want to connect
- An IAM user with read-only access to the bucket (see below)
- The bucket name and AWS region
- Lovable workspace admin or owner role
Step 1: Create an IAM user with read-only access
Before setting up the connection in Lovable, create an IAM user in AWS with the minimum permissions needed.Open the AWS IAM console
Go to the AWS IAM console and create a new IAM user, or use an existing one, for Lovable to use.
Attach a read-only S3 policy
Create and attach an inline policy, or managed policy, with the following permissions. Replace
YOUR-BUCKET-NAME with your actual bucket name:Step 2: Connect AWS S3 to Lovable
Name the connection
In Display name, enter a name for the connection, for example
S3 (Production Data).Configure the connection
Fill in the required fields:
- Bucket name: the name of the S3 bucket (for example,
my-data-bucket) - AWS region: the region where the bucket is located (for example,
us-east-1) - Access key ID: the IAM access key ID from the previous step
- Secret access key: the IAM secret access key from the previous step
Limitations
The AWS S3 connector does not support:- Writing, uploading, or deleting objects in the bucket (it has read-only access)
- Connecting to S3-compatible services other than AWS S3, such as MinIO or DigitalOcean Spaces
- Per-user AWS login where each end user connects their own AWS account
- Real-time event notifications or S3 event triggers
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.