You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you install the CLI on a new machine and use different AWS credentials (with the AdministratorAccess IAM policy attached), running cortex cluster commands will not work. We link to a cortex docs page with instructions on how to address this (implemented in #1392):
error: your aws iam user does not have access to this cluster; to grant access, see https://docs.cortex.dev/v/master/miscellaneous/security#running-cortex-cluster-commands-from-different-iam-users
It would be better if it just works out of the box (assuming that the new IAM user also has the AdministratorAccess IAM policy).
Assume the role of an IAM Role that has access to the cluster. There may already be one created (there is a role visible on the EKS console titled "Cluster IAM Role ARN"), or we may have to create one and grant access to it during cluster spin up.
The text was updated successfully, but these errors were encountered:
Currently, if you install the CLI on a new machine and use different AWS credentials (with the
AdministratorAccess
IAM policy attached), runningcortex cluster
commands will not work. We link to a cortex docs page with instructions on how to address this (implemented in #1392):It would be better if it just works out of the box (assuming that the new IAM user also has the
AdministratorAccess
IAM policy).Relevant info:
Possible solution:
The text was updated successfully, but these errors were encountered: