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

The route looks like this
```        {
            path: "/",
            method: "GET",
            eventHandler: async (event) =&gt; {
                console.log('get request received')
                return {
                    statusCode: 200,
                    body: "hello"
                }
            }
        },```

Looks like pulumi logs is still experimental :sad-panda:

`pulumi logs` has always worked for me. Is it possible that the creds you're using don't have read access to CW?

hmmm - So my `Pulumi.dev.yaml` points to `aws:profile: demos` and if I go check `demos`’s permissions it’s `AdministratorAccess`

I’ve been running `pulumi logs` from within the folder where the `Puliumi.dev.yaml` file is

I'm not familiar with the implementation of `pulumi logs`. Maybe try setting up your default / non-Pulumi creds to have the right permissions and see if that fixes it? Maybe it uses the same creds as the backend, instead of the project...