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

`jq` would be your friend, but not all resources have the same outputs, i.e., not everything has an `arn` or `id`.

```pulumi stack export | jq -r '.deployment.resources[] | {"urn": .urn, "arn": .arn, "id": .id}'```

Thank you <@U016JNMH6PP> your solution is a good tip. I also managed to use auto-tagging (<https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/>) and created a “Resource Group” in the AWS Console. It’s usefull to have a general overview of the AWS resources created by Pulumi.

Screen Shot 2020-08-03 at 5.29.37 PM.png

>  From the CloudFormation console it’s easy to find an AWS resource create by the stack, everything is linked under the resources tab.
Just a note that the Pulumi Console (<https://app.pulumi.com/>) offers a similar feature.  See the links on the right hand side which deep link into the AWS console (and Azure and GCP and Kubernetes API server).