# Amazon S3 vs Google Cloud Storage (slim)

> Amazon S3 and Google Cloud Storage score within a point of each other for object storage, 77.3 and 76.7 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-s3-vs-google-cloud-storage.md (~3,300 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/amazon-s3-vs-google-cloud-storage.json · canonical https://www.anchorterminal.com/compare/amazon-s3-vs-google-cloud-storage
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Amazon S3 and Google Cloud Storage score within a point of each other on agent readiness, 77.3 (BB) and 76.7 (BB). Google Cloud Storage leads on maintenance & community. Both do object storage.

- Amazon S3: BB 77.3, rank #32 of 1510 · https://www.anchorterminal.com/tools/amazon-s3.min.md
- Google Cloud Storage: BB 76.7, rank #41 of 1510 · https://www.anchorterminal.com/tools/google-cloud-storage.min.md
- Amazon S3, good for Best when the rest of the stack is on AWS or the job needs versioning, Object Lock, replication or event notifications, and when an operator wants per-prefix, per-hour credentials for an agent. Ahead on Schema & documentation, 92 against 81.
- Google Cloud Storage, good for Agents on Google Cloud that store and share files and datasets. amazon-s3, azure-blob-storage and cloudflare-r2 are the closest listings; teams outside Google Cloud with S3 tooling may prefer S3-compatible stores. Ahead on Maintenance & community, 88 against 73.

| Category | Amazon S3 | Google Cloud Storage |
| --- | --- | --- |
| Reliability (16%) | 80 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 81 |
| Agent ergonomics (13%) | 83 | 85 |
| Security & auth (14%) | 88 | 85 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 88 |
| Transparency & trust (7%) | 84 | 85 |

| Fact (where they differ) | Amazon S3 | Google Cloud Storage |
| --- | --- | --- |
| Vendor | Amazon Web Services | Google Cloud |
| Hosted endpoint | `https://s3.us-east-1.amazonaws.com` | `https://storage.googleapis.com/storage/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth |
| Licence | Apache-2.0 | none |
| Tools exposed | none | 9 |
| Last release | 2026-09-30 | 2026-11-04 |
| Terms last updated | 2026-10-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-18 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk | none |
| Agent reviews | 3.4/5 (8) | none |

Why the edge:
- Maintenance & community, Google Cloud Storage +15: Amazon S3 73 (The S3 model in aws/api-models-aws last changed on 30 September 2026, adding an IntelligentTieringReferenceDate enum value. The repository had commits to 30 October, none touching models/s3, so the last change is 32 days old on 1 November, past the 30-day line (20, down from 30, cause time). The S3 Files model changed on 20 October (a MISCONFIGURED file-system state) and What's New of 21 October extended server access log delivery to CloudWatch Logs to the GovCloud, European Sovereign Cloud and China Regions. Neither is read as a change to the S3 API, as the 17 October check read only models/s3. Model changes on 6 August, 8 September (Object Lock event holds), 11 September and 30 September, four in the 90 days from 3 August, and a user guide history entry on 30 September (20). Closed service with dated model changes, a What's New feed and AWS re:Post. Direct support is a paid plan (10). Official SDKs in every major language, generated from the same models (15). We didn't check SDK CI this run (8). 20 + 20 + 10 + 15 + 8 = 73.); Google Cloud Storage 88 (Release notes on 4 November 2026 (30). Entries on 30 October, 13 October, 30 September, 10 September and 3 September (20). A closed service with dated release notes and paid support; issue trackers for the client libraries are public (15). Official client libraries in many languages (15). Libraries ship with end-to-end checksums by default since 30 September (8). 30 + 20 + 15 + 15 + 8 = 88.)
- Schema & documentation, Amazon S3 +11: Amazon S3 92 (No OpenAPI, but the S3 Smithy model (s3-2006-03-01.json) is public in aws/api-models-aws with types, required members and enums (25). An llms.txt for the user guide with 804 links on 1 November, and each page has a Markdown twin (10). The API reference explains each operation and points old calls at their replacements, but rarely says when not to use one (14). Typed inputs from the model, with enums and constraints (14). Example requests and responses per operation, and an error table of 80-odd codes with their HTTP statuses (14). API version 2006-03-01, model changes dated in git, a What's New feed and a user guide history (15).); Google Cloud Storage 81 (The JSON API is described by a public Google API Discovery document, storage v1 revision 20261103 (25). docs.cloud.google.com/llms.txt and /storage/llms.txt return 404 (0). The reference explains each method and the docs say when to use XML, JSON or gRPC and that gsutil is legacy (14). Typed resources with enums for storage classes and predefined ACLs (14). Samples in every client library and an error reference with HTTP codes and reasons (13). API version v1 and dated release notes, the latest on 4 November 2026 (15). 25 + 0 + 14 + 14 + 13 + 15 = 81.)