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'm trying to run an ecs task that provisions infrastructure

Hey <@U02FZC2RE0Y> thank you for replying!

the ecs task (fargate) would run an index.py that imports pulumi and pulumi_aws

Why'd you choose Fargate for that use case?

(As opposed to a CodeBuild pipeline or something?)

<@U02FZC2RE0Y> its part of a step function and it is provisioning cloudfront resources that could take longer than 15 mins (otherwise I'd use a docker based lambda instead of fargate)

I was unsuccessful when creating a dockerfile for the fargate task while trying to install the python libs with a reqs.txt file

was wondering if there was something I might be missing

Ahh. You'll probably want to package your deps in the image itself.

Start with the image for your language (the `pulumi/pulumi` image is huge and not where I'd start): <https://github.com/pulumi/pulumi-docker-containers>

<@U02FZC2RE0Y> what if I wanted to run a python env that did more than using the pulumi cli?

or would it still be possible to run (for example: `python index.py` in the env of an image based off of `pulumi/pulumi-python?`

Are you familiar with the Automation API? I think that's what you probably want: <https://www.pulumi.com/docs/guides/automation-api/>

Basically, it flips the dependency on the Pulumi CLI: You can run `python index.py` and in `index.py`, you can run Pulumi commands programmatically.

(as opposed to `pulumi up`, which then will find and run `__main__.py` as a Pulumi program)

correct, I would like to run a python file that imports pulumi, pulumi_aws, and utilizes create_pulumi_program

I'll try that out, thank you so much <@U02FZC2RE0Y>

<@U02FZC2RE0Y> would this be possible w/o setting a pulumi_access_token?

so far I only set the PULUMI_CONFIG_PASSPHRASE when running
```create_pulumi_program```
<https://www.pulumi.com/blog/automation-api-python/>

I think a token is more appropriate. I'm not sure whether it's possible without setting a token.

what if I use an s3 backend and don't have a token? I am still running into the same error on the fargate task about `PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions`