Securely export your web data to Amazon S3

Getting started takes just minutes:

1. Sign up for a free Browse AI account
2. Create and approve your first robot
3. Use our CloudFormation template to set up secure access to your S3 bucket
4. Go to your robot's Integrate tab and select AWS
5. Enter your bucket details and connection information
6. Start exporting data automatically

‍

Browse AI receives only the minimum permissions needed to export data to your specified S3 bucket or folder. Using our CloudFormation template ensures we follow AWS security best practices with:

• Write-only access to your designated bucket/folder
• No access to read or delete existing files
• No permissions to any other AWS services
• A unique External ID for additional security verification

Browse AI supports exporting your data to S3 in both CSV and JSON formats. You can choose the format that best suits your downstream processing needs when setting up your export.

‍

Files in your bucket are organized with a clear structure:

• Each export creates a unique directory named with a timestamp and export ID
• Files are named according to the Table tab from which they come
• Large files are automatically split into manageable chunks
• Optional per-record exports create individual JSON files

Yes! When exporting, you can:

• Choose specific Table tabs to export
• Apply filters to export only certain records
• Include or exclude historical data
• Export only new or changed data from monitoring

Yes, all Browse AI plans include the S3 integration at no additional cost. Credit usage is based on your regular robot runs, not the integration itself.

‍

After setup, run a test export from your robot's Table. Check your S3 bucket to confirm the data was successfully exported with the expected file structure. You can also view your export history in Browse AI.

‍

The integration follows AWS security best practices, including:

• IAM roles with least-privilege permissions
• External ID verification
• Optional path restrictions to limit access
• Encrypted data transfer
• No storage of your AWS credentials

If you encounter problems:

• Verify your IAM role ARN is correct
• Confirm your External ID matches exactly
• Check that your bucket name and region are correct
• Ensure the bucket exists and is properly configured
• Review AWS CloudTrail logs for access issues

Yes! Once your data is in S3, you can use the full AWS ecosystem to process it:

• Trigger Lambda functions when new data arrives
• Create ETL jobs with AWS Glue
• Query data with Amazon Athena
• Build dashboards with QuickSight
• Train ML models with SageMaker

Yes, the S3 integration is ideal for organizations with data residency or compliance requirements. Since data is stored in your own AWS account, you maintain complete control over data location, retention policies, and access controls.

‍