Managing access keys
Access keys are how your tools log in to Object Storage. Manage them when you set up a new tool, rotate keys on a schedule, or replace a key that may have leaked.
How keys work
- Keys belong to an S3 user. All of a user's keys have exactly the same permissions. You can't give one key less access than another.
- Each S3 user can have up to 2 key pairs. You can't delete the last remaining pair.
- When you delete a key, it's gone for good. The secret can't be recovered.
:::tip Need a key with fewer permissions? For example, a key that can only upload backups from one IP range. Because permissions belong to the user, not the key, this needs a separate S3 user. Contact support to create one, then limit it with a bucket policy. The backup target guide walks through the full setup. :::
Create a key pair
- Go to S3 > Access.
- In the S3 access keys section, click Create.
Copy a key
- Go to S3 > Access.
- Click the copy icon next to the key to copy the access key ID.
- Click the ellipsis (…) next to the key, then click Copy secret access key.
Disable a key
Disabling a key stops it working straight away without deleting it. Use it when you suspect a leak, or to check that nothing still uses an old key before you delete it.
- Go to S3 > Access.
- Click the ellipsis (…) next to the key, then click Disable.
Delete a key
- Go to S3 > Access.
- Click the ellipsis (…) next to the key, then click Delete.
Rotate keys without downtime
Because you can have two keys at once, you can switch over without interrupting your tools:
- Create a second key pair.
- Update every tool, script and server to use the new key, and check that they work.
- Disable the old key. Watch for errors for a day or two. If something breaks, you've found a tool you missed.
- Delete the old key.
Rotate keys regularly, and straight away when a key may have been exposed, for example in a public repository or a log file.