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

I ended up doing
```const awsConfig = new pulumi.Config("aws");
const profile = awsConfig.require("profile");```
Instead

I’ll bikeshed myself after I have the entire jigsaw complete, thanks for the alt path that’ll now stick at the back of my mind for the next year though

This is what I've started to do now:
```const awsUsEast1Provider = new aws.Provider("us-east-1", {
  ...aws.config,
  region: "us-east-1",
});```

There is also an argument to be made for always declaring explicit providers, and not using the default configuration.

That’s exactly what I was looking for :sob:

For sure but since every stack we have has at the very least `aws:profile` and `aws:region` the expectation is that `aws.config` should exist.

I’m probably going to update the code now since I prefer to refer to other stacks for other config items but for stuff like aws I’d rather just use the libs `.config` variable.

As a safeguard, you can allowlist certain account IDs in the provider config (which is per-stack). See `allowedAccountIds`: <https://www.pulumi.com/registry/packages/aws/installation-configuration/#configuration-options>