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 can't find it now, unfortunately, but a community user wrote a dynamic provider that would "throw files in s3" and was a single resource, I'll try track it down

Similarly to the script idea mentioned, we leverage the `aws` cli, because the `sync` command is great:
```aws s3 sync ./static-site s3://$(pulumi stack output contentFilesBucketId) --delete```

You could also try leveraging the <https://www.pulumi.com/registry/packages/command/|command provider>, so you can use `aws s3 sync` as one resource within pulumi

Ah, <@UCWG26BH7>, I think I found the one you're talking about: <https://www.npmjs.com/package/@wanews/pulumi-throw-files-in-s3>

That being said, I also mentioned in the <#CRH5ENVDX|> thread that I've heard of (but haven't seen code for) a solution that uploads a file archive and uses Glue to unzip it.

Great, thanks all :slightly_smiling_face:

Is there a convenient way I can expose my current pulumi session credentials to a pulumi.Command somewhat idiomatically?

Ie. I use `assumeRole` in aws provider config and so the cli usage of aws s3 sync would need to assume that role to

would be nice to re-use the pulumi session than create another one

That would be the route I would go for now. The Command provider is still in preview and may be missing some functionality that would make sense for general use; if you think it's a good feature, it would be great if you'd add an issue on the repo! <https://github.com/pulumi/pulumi-command/issues>