Revisit environment agnostic operation

[t0yv0]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

CDK has two modes of operation:

• environment agnostic (no account/region)
• user explicitly sets account/region

We need to revisit what is best for Pulumi CDK:

1. how to map this and explain for users that are used to CDK, how does it "translate to Pulumi"?
2. should we consider getting ambient AWS credentials and automatically injecting account/region into CDK stack or not (what the defaults should be)

Affected area/feature