IAM policy to allow user access to add AWS configs

Hi,

I’m trying to give a user very specific access to allow them to add AWS/Azure integration via Settings Classic → Cloud and virtualization menu; they should not have access to the entire Settings menu, preferably.
This is what they currently see:

What would the policy need to contain to achieve this?
I’ve tried the below, but he still doesn’t get access to AWS in the menu.

ALLOW settings:schemas:read;<br>ALLOW hyperscaler-authentication<img class="lia-deferred-image lia-image-emoji" src="https://community.dynatrace.com/html/@F9676CCDE08B8746467ACFFDC4C9827E/images/emoticons/aws.png" alt=":aws:" title=":aws:">authenticate;<br>ALLOW settings:objects:write WHERE settings:schemaId = 'group:cloud-and-virtualization' AND settings:schemaId = 'builtin:cloud.aws';<br>ALLOW settings:objects:read WHERE settings:schemaId = 'group:cloud-and-virtualization' AND settings:schemaId = 'builtin:cloud.aws';

Hi @andre_vdveen ,
This requires environment level settings permission.
I think this would work in this case.

ALLOW environment:roles:manage-settings WHERE settings:schemaId = 'group:cloud-and-virtualization' AND settings:schemaId = 'builtin:cloud.aws';

Let me know if it works.
Regards,
@Maheedhar_T

Hi @Maheedhar_T

Thanks for the suggestion, but unless I understand the documentation wrong, that role only works with condition

<span>environment:management-zone</span>

I’ve set it up using a Mgmt Zone that the user has access to, but it didn’t work;even if I leave the WHERE clause out and just add

ALLOW environment:roles:manage-settings;

over and above what I originally added.

I think herein lies the answer to my question and problem.

This means I have to assign the policy “Environment role - Change monitoring settings” to the user, which means they can change any setting, not just AWS.

Agree 100%.  I posted in Dec 2023 about this and other scenarios.  Crazy that it is not fixed yet.

https://community.dynatrace.com/t5/Open-Q-A/Settings-1-0-2-0-and-some-settings-are-on-neither/td-p/231226

Looking more at this, this is setting 1.0 so you should be able to provide write access to page (not read).  I just tested write access to aws page and it worked.

Here is my IAM policy
ALLOW settings:objects:write, settings:schemas:read WHERE settings:schemaId IN (“builtin:cloud.aws”);