Hi, We’re developing a wrapper API on top of Pulumi, containerizing it as a Docker image, and deploying it on ECS. This API is used to manage infrastructure deployments. However, we’re facing a couple of issues: 1. Configuring Pulumi to work inside the Docker container (Python runtime): Our current setup looks like this:

name: dev
description: setup for dev
runtime:
  name: python
  options:
    toolchain: pip
    virtualenv: /projects/pulumi-fastapi/venv
config:
  pulumi:tags:
    value:
      pulumi:template: aws-python

We’re having trouble correctly pointing to the Python runtime inside Docker. 2. Using AWS Assume Role for cross-account deployments: We've added the assume role configuration in the

pulumi.stack.yaml

file, but the S3 state backend is failing to authenticate. Any insights or suggestions on resolving these issues would be greatly appreciated!

I'm afraid you'll have to be a lot more specific for others to be able to help you.

We’re having trouble correctly pointing to the Python runtime inside Docker.

What exactly doesn't work for you?

but the S3 state backend is failing to authenticate.

What does this look like? Can you authenticate to S3 from within the container (e.g., using boto3 or the AWS CLI)?

Have you started with the Pulumi Python Image as your base? That might help speed dev up.

Yes, I have used

pulumi/pulumi-python

as base image. I have resolved this issue by creating a venv inside docker and pointing pulumi projects to use it.