1
Store keys outside source control
Save the endpoint URL and keys in a secrets manager or environment variables. Never commit them to git repositories or client-side code.
S3 Access Credentials — Endpoint, Keys and Safe Handling
After provisioning you receive an S3 endpoint URL, an Access Key ID and a Secret Access Key. These credentials authorize full bucket operations, so treat the Secret Key like a password.
📋 Prerequisites
- A provisioned HubforHost S3 bucket with credentials received after payment confirmation
Step-by-Step Instructions
2
Use least-privilege IAM policies
Confirm the agreed bucket policies during provisioning and restrict each application to the minimum buckets and actions it needs.
3
Rotate on staff changes or suspected exposure
Contact support to arrange credential rotation. Update every configured client (AWS CLI, rclone, SDKs) at the same time.
📌 Important Notes
- You are responsible for activity under your credentials and for keeping them confidential.
- For mobile apps, use pre-signed URLs instead of embedding Secret Keys — see the Android integration guide.