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

Screen Shot 2021-03-17 at 8.54.14 AM.png

You can uses `aliases` to change the parent of the resource to your component. 

<https://www.pulumi.com/blog/cumundi-guest-post/|https://www.pulumi.com/blog/cumundi-guest-post/>

Makes sense, but we have over 500 resources to import and I was hoping I could import them directly into the final structure instead of aliasing all of them

You can set the parent with `pulumi import --parent ...` if that's how you're importing it.

Aha! And that works for arbitrarily deep nesting? In the example screenshot above, I would be importing under `panther:s3Bucket` (component) -&gt; `aws:s3:Bucket` -&gt; `aws:s3:BucketPublicAccessBlock`

Great, I will try that, thank you! Last question - is there any meaningful difference between importing it from within Pulumi code and using the CLI?