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

Looks like the AWS SDK supports it:
<https://docs.aws.amazon.com/sdk-for-go/api/aws/session/>

I'm looking for the equivalent of this Terraform configuration:
```terraform {
  backend "s3" {
    bucket = "bucket-in-another-account"
    role_arn = "arn:aws:iam::other-account-id:role/role-in-other-account-with-access-to-bucket"
  }
}```

Yes, you’re referring to using multiple AWS provider instances, see this discussion: <https://pulumi-community.slack.com/archives/C84L4E3N1/p1595517949114200>

Yes, that is a solution, unfortunately it doesn't avoid my current problem. I've already deployed everything using the default provider. If I change from the default provider to an explicit provider pointing at the same account with the same creds, it wants to tear everything down and recreate them. That's my VPC, RDS, DB, AD, my EC2 instances.. it would be destructive. And there's all the extra work on the side, updating keys in vaults etc.
I want to be able to use one provider for the backend, and a different provider that I don't pass into resources via the `provider` opts property. Which is what the Terraform code above achieves.