Hi folks! We're trying to use Pulumi Deployments with a self-hosted (customer-managed) workflow runner on our own EC2 instance, primarily because our Pulumi worker needs VPC access to call AWS APIs (EKS, RDS, IAM, etc.) during

pulumi up

. The docs say Customer-Managed Workflow Runners are available on the Business Critical edition. A few questions: 1. Is there any way to use self-hosted runners on Team or Enterprise plan, or is Business Critical strictly required? 2. Is there an alternative approach to give Pulumi Deployments (managed runners) access to a private AWS VPC without self-hosting — e.g., via OIDC or IAM role assumption from Pulumi's runner IPs? For context: we're using Pulumi Cloud for state management and just need the runner to have AWS credentials + private network access. Happy to hear if there's a recommended pattern for this use case short of Business Critical. Thanks!

Hi Schitiz, happy to discuss this over a call as you'll always have options with Pulumi. It's best to focus on the technical fit first and then we try to make commercials align. I've sent you a DM, once you let me know your location I can ask a colleague to arrange a time to chat with you if that works?

Hi Dipali, I am based out of Bengaluru, India.

I've sent a reply to your DM, thanks!