No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I missed the notes at top of docs <https://www.pulumi.com/registry/packages/aws/api-docs/iam/rolepolicyattachment/>

most likely am hitting those conflicts

ie. the role _is_ created with some managed policy id's

is the workaround to not pass managed id's to the `new Role`  and instead just do a for loop with individual policy resources after?

albeit this will now 5-10x our pulumi cloud credit usage per role :upside_down_face:

You can use the managed policy IDs, just attach them using another RPA. Don't mix inline and attached policies.