Member since
07-25-2019
184
Posts
42
Kudos Received
39
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3591 | 03-25-2019 02:25 PM | |
| 1758 | 01-22-2019 02:37 PM | |
| 2141 | 01-16-2019 04:21 PM |
03-25-2019
02:25 PM
@Nathaniel Vala This might be of help.
... View more
01-22-2019
02:37 PM
Hi @Anton Zadorozhniy Currently there is no such fine grained authorization implemented in Cloudbreak and regions, VPC-s and subnets are fetched on the fly from the cloud provider. What you can do is to create role based credential with a specific AWS role constrained to only specific resources (instead of "Resource": [
"*"
]) You can specify resource type level authorization permissions in Cloudbreak with the help of workspaces, resources will be shared inside a workspace. Hope this helps!
... View more
01-16-2019
04:21 PM
1 Kudo
@Manu A I assume you are using Cloudbreak. If so, then the AWS tag value is validated against this pattern, which fails because the value starting with aws. The documentation shows that aws: prefix is reserved. Hope this helps!
... View more