My S3 secret key may have leaked. What should I do?
Short answer: Treat it as compromised: create a new access key in AWS, paste the new key and secret into the account with Edit, test the connection, then delete the old key in AWS. Your transfers and nickname are kept.
Treat it as compromised and replace it now. A secret that appeared in a screenshot, chat or shared terminal output should never be reused.
- In the AWS console, create a new access key for the user.
- In Storage Studio, select the account, click Edit, and paste the new Access Key ID and Secret Access Key. Save.
- Click Test connection to confirm it works.
- Back in AWS, deactivate and delete the old key.
Editing keeps the account, its nickname and its transfers, so nothing else needs redoing.