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

Can `pulumi_aws` and `pulumi_aws_native` be used together, especially for `depends_on`? Here's the scenario:

1. Create an iam role via `pulumi_aws`
2. Create imagebuilder lifecycle policy via `pulumi_aws_native`, and adds the IAM role in `depends_on` 
Expect:
The imagebuilder waits for the iam role to be available before create

Actual:
Creating the imagebuilder failed due to iam role not ready yet:
```  aws-native:imagebuilder:LifecyclePolicy (lifecycle-policy-keep-lastest-ami-dev):
    error: creating resource: creating resource (await): operation CREATE failed with "InvalidRequest": The value supplied for parameter 'executionRole' is not valid. The provided role does not exist or does not have sufficient permissions (Service: Imagebuilder, Status Code: 400, Request ID: f6ba505b-c701-4b9e-8409-db62d316dbd3)```
Re-run the `pulumi up` succeeded

Yes. The provider isn't important, any resource can depend on any other resource, so long as it's in the same stack.