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
Hi, asking the user to provide account ID is an unnecessary complication. Only access and secret keys should be enough to obtain all necessary information. Using a standard awscred file like aws-cli will make a lot of sense here.
Hi @akostadinov and thank you for the input. OCM provides the Account ID to the accountClaim CRD (more info in https://github.com/openshift/aws-account-operator ) in order to setup the account for OSD CCS clusters.
As this is a hard requirement in one of OCM dependencies we can't remove this field.
@igoihman , my suggestion is for OCM to obtain the account ID using the provided access and secure keys, then provide it to whatever CRD or other component needs it.
If OCM does not verify this account id, it may also be a bug in the system with unknown consequences.
Hi, asking the user to provide account ID is an unnecessary complication. Only access and secret keys should be enough to obtain all necessary information. Using a standard awscred file like aws-cli will make a lot of sense here.
Obtaining account by access keys should be easy:
https://docs.aws.amazon.com/STS/latest/APIReference/API_GetCallerIdentity.html
The text was updated successfully, but these errors were encountered: