Reviewed official documentation and pricing, then designed the feature around a private S3-compatible bucket, presigned browser transfers, authenticated reads, and explicit CORS. No bucket, account, or live object operation was created during the task.
- What worked
- S3 compatibility, Fly-oriented provisioning, private buckets, presigned operations, and the stated egress model matched the small deployment architecture closely.
- What got in the way
- CORS and credentials still require post-deployment configuration, so the integration could not be validated end to end without external resources.