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 assuming you're talking about our automation API to wrap Pulumi?
<https://www.pulumi.com/automation/>

if so, you can configure the credentials using a provider: <https://www.pulumi.com/docs/reference/pkg/aws/provider/#accesskey_nodejs>

Hm. I don't know? :slightly_smiling_face: Not sure I understand the product distinction yet.
I thought I could write some golang binary that (when provided with some credentials) it would setup my AWS for me.

Like wrapping terraform up as an API instead of DSL.

This looks pretty close <https://github.com/pulumi/pulumi-aws/blob/master/examples/lambda-layer-new/index.ts>

<@U02EKMTG7T7> you can do this with Automation API. you'd need to use the AWS SDK to set your credentials up, but then you can use the automation API to provision your infrastructure

you can see an example of a Pulumi automation API program here:
<https://github.com/jaxxstorm/pulumi-productionapp/blob/main/cli/main.go#L73-L86>

How is the automation API different from the other API? I am still lacking a good overview.

this is interesting <https://github.com/jaxxstorm/ploy>