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

There are constants for managed policies.

<https://github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/iam/managedPolicies.ts>

1) Not problematic per se, since AWS won't let you change them and you'll get a normal failure.

Aside: there's a class of resources, including but not limited to AWS managed policies, that simply never need to be resources. The only thing you ever need from them are their IDs, so why import a resource using its ID if the only thing you ever get from it is its ID? I see this a fair bit in client code: someone gets (for example) a VPC ID from a stack reference, then inflates it using something like `Vpc.fromExistingIds()`, then uses it only to get the VPC ID. This is wasteful. Any time you're thinking of importing or inflating a resource, consider what you're likely to use it for. If it's just the ID.. don't bother!