How to Make AWS S3 Files Accessible via Google Drive — Sync S3 Buckets for Team Collaboration
Your developers store everything in S3 buckets. Your marketing team uses Google Drive. When marketing needs a file from S3, they ask a developer to download and share it. There's a better way.
AWS S3 is powerful and cost-effective, but it's designed for developers. The AWS Console isn't user-friendly for non-technical team members, and sharing individual S3 objects requires generating presigned URLs. By syncing selected S3 folders to Google Drive, everyone can access the files they need without AWS credentials.
Manage & Sync All Clouds in One Place
RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.
- One-click jobs: Copy · Sync · Compare
- Schedulers & history for reliable automation
- Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
Free core features. Plus automations available.
The Problem
- Developers store assets, reports, and exports in S3.
- Non-technical teams (marketing, sales, management) can't access S3 easily.
- Current workaround: Someone downloads from S3, uploads to Google Drive manually.
- Result: Stale files, extra work, and frustrated teams.
The Solution
Use RcloneView to sync specific S3 folders to Google Drive automatically:
S3: reports/monthly/ → Google Drive: Shared/Monthly Reports/
S3: assets/marketing/ → Google Drive: Shared/Marketing Assets/
S3: exports/data/ → Google Drive: Shared/Data Exports/
Setup
1) Connect both accounts
Add AWS S3 and Google Drive as remotes:
2) Create selective sync jobs
Don't sync the entire S3 bucket — sync only the folders non-technical teams need. Use filter rules to include specific paths or file types.
3) Schedule automatic updates
Sync every hour or daily so Google Drive always has the latest files:
4) Verify sync completeness
One-Way vs Two-Way
One-way (S3 → Google Drive)
Use Copy or Sync from S3 to Google Drive. Google Drive is read-only (a mirror). Changes must be made in S3.
Best for: Reports, exports, generated assets.
Two-way
Sync both directions. Changes in Google Drive sync back to S3 and vice versa.
Best for: Shared working folders where both teams contribute.
Filter for Relevance
Don't flood Google Drive with everything in S3. Use filters:
- Include only
*.pdf,*.xlsx,*.pptx— business documents. - Exclude raw data, logs, and temporary files.
- Use
--max-age 90dto sync only recent files.
Cost Awareness
S3 egress costs money ($90/TB for the first 10 TB). For frequent syncs of large datasets, consider:
- Sync during off-peak hours.
- Use filters to limit data volume.
- Consider Backblaze B2 or Wasabi as an intermediate (free/cheap egress).
Getting Started
- Download RcloneView from rcloneview.com.
- Add S3 and Google Drive as remotes.
- Create targeted sync jobs for specific folders.
- Schedule hourly or daily updates.
- Share the Google Drive folders with your team.
Bridge the gap between developer infrastructure and team collaboration.
Related Guides:
Supported Cloud Providers
