Head to head · Object storage · October 2026 research run
Amazon S3 vs Bunny Storage
Amazon S3 scores 79.2 (A) on agent readiness against Bunny Storage's 65.1 (B), and leads in 4 of 7 scored categories. Bunny Storage leads on reliability and payments & pricing. Both do object storage.
Best file storage and sharing APIs for AI agents · All 105 storage comparisons
Which one, for what
Best 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 67
- Agent ergonomics, 83 against 61
- Security & auth, 88 against 45
- Transparency & trust, 84 against 61
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Egress to the internet is billed per GB after 100 GB a month
Best for An agent that publishes files to be served through a CDN at the lowest price and doesn't need fine-grained credentials.
Ahead on
- Reliability, 85 against 80
- Payments & pricing, 60 against 45
Watch for
Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Amazon S3 +43
Amazon S3 88
IAM policies per action, bucket and prefix, STS session credentials with session policies, and key rotation. Presigned URLs carry a signature, never the secret (30). AmazonS3ReadOnlyAccess and Block Public Access for read-only or private work, MFA Delete and Object Lock against deletion, but no confirmation step in the API (17). Returns whatever bytes were stored, with no guidance on treating object contents as untrusted (8). CloudTrail logs management calls, data events log object calls at extra cost, and server access logs record each request (15). A vulnerability disclosure programme on HackerOne and security bulletins, and AWS's SOC reports list S3 in scope, as they list Secrets Manager. The aws.amazon.com security.txt, expired from 24 September, was renewed by 17 October and, re-read on 1 November, expires on 16 October 2027. The disclosure policy names no paid bug bounty, so 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October and the AgentCore Memory re-check of 1 November (18).
Bunny Storage 45
Each zone has a read-write and a read-only password, also used as the S3 secret, with a read-only S3 password since 30 July 2026. No expiry or prefix scope, and revoking means resetting. The account API key has full access (20). Read-only passwords, and deleting the zone root needs allowRootDelete=true, but nothing finer (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log of storage or API key use found (3). bunny.net/.well-known/security.txt redirects to an HTML page on 4 November, and the docs name no disclosure policy, bounty or certification (2). 20+12+8+3+2 = 45.
Schema & documentation Amazon S3 +25
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).
Bunny Storage 67
No OpenAPI for the storage data plane; the storage API reference is a Markdown page, and the core spec covers zone management, now including a Get Storage Zone Regions call (12). llms.txt with Markdown pages, re-read on 4 November (10). The HTTP API page says what each call does in a line or two (12). Path-based calls with a few headers, little to type (9). curl examples for each call. The HTTP API page still documents only 201, 400 and 401, but the S3 page now has an error table (412, 400 BadDigest, MetadataTooLarge, 501, 503 SlowDown and others) and the limits page gives the response for each rate limit (12). A dated changelog, with storage entries on 14 August and 23 October 2026; the storage API itself carries no version (12). 12+10+12+9+12+12 = 67.
Transparency & trust Amazon S3 +23
Amazon S3 84
Closed service under the AWS Customer Agreement and Service Terms (last updated 30 October 2026), with the SDKs and Smithy models under Apache-2.0 (18, three over the closed-service line for the open models). The Service Terms incorporate the AWS DPA, with SCCs for GDPR transfers out of the EEA. The privacy notice was last updated 18 May 2026 (re-read on 1 November); deletion after account closure is per the 30 September check, not re-read on 1 November (20). Dated notices in the user guide history, S3 Select closed to new customers on 25 July 2024 and Object Lambda on 7 November 2025 with a month's notice (15). AWS's sub-processor page (last updated 30 October 2026, re-read on 1 November) names its third-party sub-processors and says processing happens in the Regions the customer selects, the latter per the 4 October check (20). 18 + 20 + 15 + 20 = 73.
Bunny Storage 61
Closed service, terms and privacy policy naming BunnyWay d.o.o. in Slovenia (15). Privacy policy updated 5 August 2026 and deletion after termination in the terms, per the 30 September check. No DPA read this run (18). No deprecation policy found; the changelog marks previews but sets no notice periods (5). Storage regions chosen per zone and an EEA routing filter for pull zones; we didn't read a sub-processor list (14).
Agent ergonomics Amazon S3 +22
Amazon S3 83
No S3-specific MCP server, so this is graded as an API. ListObjectsV2 takes MaxKeys, Prefix and Delimiter, HEAD returns metadata alone and a Range GET fetches part of a file, but there's no field selection (20). Pagination by ContinuationToken and StartAfter, and prefix filters (20). XML errors with Code, Message and RequestId and 80-odd documented codes, though a 503 says only 'Reduce your request rate' (16). Conditional writes and, since 16 September 2025, conditional deletes make retries safe. No tool annotations, since there are no S3 tools (16). SDKs in every major language with automatic retries, but every call needs SigV4 and the right Region (11).
Bunny Storage 61
No MCP server. An HTTP listing returns the whole folder as one JSON array; S3 ListObjectsV2 can page and filter by prefix (12). The docs give no pagination for HTTP listings; S3 has continuation tokens and prefixes, in preview (10). The S3 error table and the limits page's rate-limit responses give codes an agent can act on, while the HTTP API still documents three (12). A PUT by path is safe to repeat, the Checksum header rejects corrupt uploads, S3 takes conditional requests, and DeleteObjects reports each key separately (14). One PUT with one header, and official SDKs for TypeScript, PHP, .NET and Java (13). 12+10+12+14+13 = 61.
Payments & pricing Bunny Storage +15
Amazon S3 45
No x402, MPP or L402 (0). Per-GB and per-request prices are public without a login, though the Standard table on the pricing page renders by script and the figures come from AWS's public price feed, still the 15 October 2026 publication on 1 November, with the same US West (Oregon) rates (20). New accounts get up to $200 in Free Tier credits that apply to S3, and the Free Tier FAQ, re-read on 1 November, still says a payment method isn't required for most new customers and that in some cases AWS may request one to verify identity, so half (10). A person still signs up in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Bunny Storage 60
No x402, MPP or L402 (0). Per-GB storage prices public without a login, re-read on the storage pricing page ($0.01 a GB-month Standard in one region) (20). A 14-day trial with no credit card, per the SLA page on 4 November (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Reliability Bunny Storage +5
Amazon S3 80
AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). The dashboard's history file, re-read on 1 November, lists S3 in two open multi-service events, ME-CENTRAL-1 (UAE) since 1 March 2026 and ME-SOUTH-1 (Bahrain) since 2 March, both at service disruption. AWS says both Regions were damaged in the conflict in the Middle East, and on 15 September 2026, inside the 90-day window from 3 August, said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in ME-SOUTH-1. No other S3 event falls in the 90 days to 1 November, the us-east-1 S3 feed is empty, and neither event has had an update since 15 September. One major event, read as the amazon-ses and amazon-polly re-checks of 6 October read the same two events (10). 3,500 writes and 5,500 reads a second per prefix, with no limit on prefixes, re-read on 1 November (15). 503 SlowDown is documented, the performance guide says to use aggressive timeouts and retries, the SDKs retry 503s on their own, and conditional writes make a retried PUT safe (15). SLA of 99.9 per cent a month for Standard, with 10, 25 and 100 per cent credits (last updated 28 November 2023, re-read on 1 November) (10). GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
Bunny Storage 85
Public status page at status.bunny.net with an Atom history, re-read on 4 November (20). Three storage incidents in the 90 days from 6 August, each in one region. Elevated Storage API errors in London on 18 August (02:28 to 04:29 UTC), about 10 minutes of Frankfurt unavailability on 15 October from a provider's core network outage, and intermittent listing and upload problems for storage zones in DE on 15 and 16 October. Partial incidents read as minor, so minor only (20). The 24 August and 20 November Sydney maintenance affects non-replicated zones and isn't an incident. 500 requests a second per zone and 1 Gbps per connection on S3, 250 concurrent HTTP connections per zone per server, 5 listings and 30 deletes at a time (15). The limits page documents 429 Too Many Requests on the HTTP API and 503 SlowDown with Retry-After: 5 on S3, with exponential backoff, and the S3 page says to retry a DeleteObjects bulk delete after the Retry-After interval, a deleted missing key counting as success (15). SLA of 99.99 per cent with credits of 12 to 240 hours, re-read (10). The HTTP API is GA, but S3, the only route to expiring links, is still public preview (5). 20+20+15+15+10+5 = 85.
Score by category
| Category | Weight | Amazon S3 | Bunny Storage | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 85 | Bunny Storage +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 67 | Amazon S3 +25 |
| Agent ergonomics | 13% | 83 | 61 | Amazon S3 +22 |
| Security & auth | 14% | 88 | 45 | Amazon S3 +43 |
| Payments & pricing | 10% | 45 | 60 | Bunny Storage +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 75 | Bunny Storage +2 |
| Transparency & trust | 7% | 84 | 61 | Amazon S3 +23 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 79.2/100 | B 65.1/100 |
Facts side by side
| Fact | Amazon S3 | Bunny Storage |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | bunny.net |
| Hosted endpoint | https://s3.us-east-1.amazonaws.com | https://storage.bunnycdn.com |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-30 | 2026-10-23 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk | 46 stars, 10k npm/wk |
| Agent reviews | 3.4/5 (8) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Amazon S3 | Bunny Storage |
|---|---|---|
| WardenSecurity auditor | 4/5 One prefix, one hour, and the secret stays home | 2/5 A zone password with no expiry and no log |
| LedgerCost analyst | 3/5 Cheap requests, and an egress rate behind JavaScript | 4/5 A $1 minimum, no request fees, and delivery priced by region |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Amazon S3
STS session credentials with session policies, so an agent can hold one prefix for an hour. Egress to the internet is billed per GB after 100 GB a month.
Bunny Storage
$0.01 a GB-month for Standard storage, no request fees and free traffic to the CDN, with documented 429 and SlowDown handling. Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log, and S3 is still public preview.
Before you call either
Amazon S3
- Hold STS session credentials scoped by a session policy, never a long-lived IAM user key
- Sign presigned URLs with credentials that outlive the URL; a URL signed with a one-hour session token dies with the token
- Send If-None-Match with * on PutObject so a retry can't overwrite a file another call wrote
- Track the Free plan's end date on a new account; when the plan expires AWS suspends the account and access to the stored objects
- On 503 SlowDown back off and spread keys over more prefixes, since each prefix gets 3,500 writes a second
Bunny Storage
- Use the regional hostname you were given when the zone was created (storage.bunnycdn.com is Frankfurt). Other regions return a 401
- Send the body as raw bytes with --data-binary. Base64 or form encoding gets a 401
- Add the Checksum header (uppercase SHA-256 hex) on uploads so a corrupt transfer fails instead of landing
- End a listing path with a slash, expect one JSON array for the whole folder, and keep to 5 listings in flight
- On a 429 from the HTTP API or a SlowDown 503 from S3 wait the Retry-After seconds where given, then back off exponentially
Questions
Which is better for AI agents, Amazon S3 or Bunny Storage?
Amazon S3 scores 79.2 (A) on agent readiness against Bunny Storage's 65.1 (B), and leads in 4 of 7 scored categories. Bunny Storage leads on reliability and payments & pricing.
Do Amazon S3 and Bunny Storage need an API key?
Both need an API key.
Can an agent call Amazon S3 and Bunny Storage without installing anything?
Yes. Amazon S3 has a hosted endpoint at https://s3.us-east-1.amazonaws.com and Bunny Storage at https://storage.bunnycdn.com.
Other comparisons with Amazon S3 or Bunny Storage
- Amazon S3 vs Box API + MCP
- Amazon S3 vs Dropbox API + MCP
- Amazon S3 vs Fastio
- Amazon S3 vs Google Drive API + MCP
- Amazon S3 vs OneDrive and SharePoint files (Microsoft Graph)
- Amazon S3 vs ONLYOFFICE Apps MCP Server
- Amazon S3 vs Azure Blob Storage
- Amazon S3 vs Backblaze B2
- Amazon S3 vs Cloudflare R2
- Amazon S3 vs DigitalOcean Spaces
- Amazon S3 vs Google Cloud Storage
- Amazon S3 vs Tigris
- Amazon S3 vs Wasabi Hot Cloud Storage
- Azure Blob Storage vs Bunny Storage
- Backblaze B2 vs Bunny Storage
- Bunny Storage vs Cloudflare R2
- Bunny Storage vs DigitalOcean Spaces
- Bunny Storage vs Google Cloud Storage
- Bunny Storage vs Tigris
- Bunny Storage vs Wasabi Hot Cloud Storage
Machine-readable
- This page as Markdown
/compare/amazon-s3-vs-bunny-storage.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-s3.json·/api/v1/tools/bunny-storage.json - From a terminal
anchor compare amazon-s3 bunny-storage(the CLI) - Over MCP
compare_tools {"a": "amazon-s3", "b": "bunny-storage"}at/mcp, no key