This message was deleted.

Hey Colin, to respond to your original question above - no, we don't use CFN to do any deploys. Pulumi's providers (in your case the AWS provider) will make calls to the AWS API directly to create the resources. It then stores the result of that API call in the pulumi state We also do parallel API calls when creating the resources, unless the resources depend on each other. if you pass an output from one resource (ie the result of the creation) to another resource, that dependency means the operations will happen serially because there is a dependency between them. All the rest of the resources will be created on an

up

- you can even see this happen in the output. It's much faster

That's perfect. I'm going to see if I can port over tonight. Any conference talks on Pulumi you might recommend, while I work on the port?

We have a whole host of videos here, webinars etc: https://www.youtube.com/pulumitv I also like this talk by my friend and colleague Paul Stack:

Sweet, thanks

you can define a CFN stack using the CFN resource: https://www.pulumi.com/docs/reference/pkg/aws/cloudformation/ but you can also use the

import

command to import resources that are in your CFN stack, it's a relatively new feature so you might want to play careful with it

Fair enough, our infrastructure is fairly simple, I can probably manually port without too much work.