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

When you say “give a stack permission to access it”, what exactly do you have in mind?  If you need to construct IAM permissions, you should just be able to use the documented principals and resource arn formats that Timestream provides in their docs from your Pulumi IAM or related resources. 

This is the kind of error we're seeing, and yes I assume it's giving the role more permissions  - is there an example to follow on what that would look like? Also, everyone in our team loves Pulumi, from IT to the software engineers. I always feel I need to mention it because you guys are doing a fantastic job

Figured it out - It was as easy as creating another attached policy and associate it with the same role. I think the less intuitive part (which arguably is because this was the first time we needed to do it) is not having an Array to pass these into vs. defining the objects and from there associating them with the role they'll be attached to. :thumbsup:  All good on our end though