Can I use temporary AWS credentials or single sign-on with Storage Studio?
Short answer: The form takes a long-lived Access Key ID and Secret Access Key; there's no session-token field, and temporary credentials expire, breaking schedules. Create a dedicated user with its own key, limited to one bucket.
The Bucket Storage form takes a long-lived Access Key ID and Secret Access Key; there's no field for the session token that temporary credentials need, and they expire anyway, which would break scheduled transfers.
Create a dedicated user with its own access key for Storage Studio, limited to the one bucket it needs. Temporary keys usually start with ASIA; long-lived user keys usually start with AKIA.