Google Cloud Storage
Google Cloud Storage (GCS) provides S3-compatible access through its XML API interoperability layer. AeroFTP includes a dedicated Google Cloud Storage preset with pre-configured endpoint and path-style addressing.
Why Use AeroFTP with Google Cloud Storage
- Dedicated GCS preset with auto-configured endpoint
- Desktop bucket browsing and object transfer workflows
- Works alongside Google Drive (separate protocol) in the same interface
- One interface for GCS, AWS S3, Azure, R2, and other S3-compatible services
What You Need
- a Google Cloud project with Cloud Storage enabled
- an HMAC Access Key and Secret
- your target bucket name
Creating HMAC Keys
- Open the Google Cloud Console.
- Go to Cloud Storage > Settings > Interoperability.
- If prompted, click Set project as default.
- Under User account HMAC or Service account HMAC, click Create a key.
- Copy the Access Key and Secret immediately (the Secret is shown only once).
How to Connect
- Open AeroFTP.
- Select Google Cloud Storage from the S3 provider presets.
- Enter your HMAC Access Key and Secret.
- Enter your bucket name.
- Select a location (or leave as Auto).
- Connect and save the profile.
The endpoint is pre-configured as:
text
storage.googleapis.comRecommended Defaults
| Setting | Value |
|---|---|
| Endpoint | storage.googleapis.com (auto-filled) |
| Path style | Enabled (required for GCS) |
| Region | auto (recommended) |
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Access denied | Wrong HMAC keys | Regenerate keys in Cloud Storage > Settings > Interoperability |
| Bucket not found | Wrong bucket name | Verify exact name in Cloud Storage > Buckets |
| Connection timeout | HTTP/2 negotiation | AeroFTP forces HTTP/1.1 automatically for GCS compatibility |
| Project not set | Missing default project | Set your project as default in the Interoperability tab |
Related Documentation
- S3-Compatible Storage
- Google Drive (separate OAuth-based protocol)
- Quick Start