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

```CLI          
Version      3.34.1
Go Version   go1.18.3
Go Compiler  gc

Plugins
NAME    VERSION
nodejs  unknown

Host     
OS       darwin
Version  12.4
Arch     x86_64

This project is written in nodejs: executable='/usr/local/bin/node' version='v16.14.0'

Backend        
Name           <http://pulumi.com|pulumi.com>
URL            <https://app.pulumi.com/rfab>
User           rfab
Organizations  rfab, rivet

Pulumi locates its logs in /var/folders/gt/8l3t_j7n1bg4wx8d_rfyg6v00000gn/T/ by default
warning: Failed to get information about the Pulumi program's plugins: Could not find either /Users/ryanfabela/development/work/dpb/main/infrastructure/yarn.lock or /Users/ryanfabela/development/work/dpb/main/infrastructure/package-lock.json
warning: Failed to get information about the current stack: No current stack```

I added the symlink for the yarn.lock file:
```CLI
Version      3.34.1
Go Version   go1.18.3
Go Compiler  gc

Plugins
NAME    VERSION
aws     5.7.2
docker  3.2.0
nodejs  unknown

Host
OS       darwin
Version  12.4
Arch     x86_64

This project is written in nodejs: executable='/usr/local/bin/node' version='v16.14.0'

Backend
Name           <http://pulumi.com|pulumi.com>
URL            <https://app.pulumi.com/rfab>
User           rfab
Organizations  rfab, rivet

Dependencies:
NAME            VERSION
@pulumi/pulumi  3.34.0
@pulumi/aws     5.7.2
@pulumi/awsx    0.40.0
@types/node     14.18.21

Pulumi locates its logs in /var/folders/gt/8l3t_j7n1bg4wx8d_rfyg6v00000gn/T/ by default
warning: Failed to get information about the current stack: No current stack```

This happens even when I have removed the symlinks and installed everything directly in the services directory

<@U03L4CW4DTJ> can you update pulumi-aws to `5.8.0`

Hi <@U03L4CW4DTJ> - so you can do 1 of 2 things here:

1. Upgrade to 5.8.0 where we removed all credentials validation as it was before
2. set `aws:skipCredentialsValidation true` and it should work for you

you are a gentleman and a scholar. Thank you. That fixed it

Sorry about the issue <@U03L4CW4DTJ> - I have a PR WIP to fix these up atm  <https://github.com/pulumi/pulumi-aws/pull/2004>

no problem, I appreciate the quick response. Thank you for the link