Other: Separate API keys for each destination
AnsweredWe have separate redshift destinations for our software development lifecycle (dev, stage, and prod), and usually keep our API credentials separate for each environment. This keeps each environment isolated from each other, for example to ensure that dev and stage don't interact with with prod.
How can we setup separate API keys for each destination?
-
Official comment
Hi Jay Johnson, we currently associate API keys with account owners/admins, so a workaround here might be creating 3 users associated with the 3 environments.
We're currently digging into re-architecting how we handle API keys (and separating them from 1-to-1 user relationships). What would you consider ideal for your use case? Any examples of companies that manage API keys well that you like?
Please sign in to leave a comment.
Comments
1 comment