I was experimenting with aliyun command line client against cr Personal Edition. It seems the aliyun cr GetAuthorizationToken command only supports 2016-06-07 API for now
Invoking aliyun --access-key-id "$ak" --access-key-secret "$sk" --region cn-beijing cr GetAuthorizationToken will fail with the following error, with http status code being 404 (req id: 77C730C7-CE62-51FD-AC39-2658DCF9EE05). The aksk was for a RAM user with AdministratorAccess role policy.
Same command but with access key created from "AccessKey Management" works just fine.
My end goal is to use aksk from a RAM user with only permission to access specified repo. Aksk from "AccessKey Management" does not pertain to the least permission security practice.
I was experimenting with
aliyun
command line client against cr Personal Edition. It seems thealiyun cr GetAuthorizationToken
command only supports 2016-06-07 API for nowInvoking
aliyun --access-key-id "$ak" --access-key-secret "$sk" --region cn-beijing cr GetAuthorizationToken
will fail with the following error, with http status code being 404 (req id:77C730C7-CE62-51FD-AC39-2658DCF9EE05
). The aksk was for a RAM user with AdministratorAccess role policy.Same command but with access key created from "AccessKey Management" works just fine.
My end goal is to use aksk from a RAM user with only permission to access specified repo. Aksk from "AccessKey Management" does not pertain to the least permission security practice.