Exactly. If I can guarantee that if I'm calling an EC2 module tested and demonstrated to work correctly, launching it in the early stages of development can be

Exactly. If I can guarantee that if I'm calling an EC2 module tested and demonstrated to work correctly, launching it in the early stages of development can be a significant time sink. However, due to the nature of AWS and being able to authenticate to one region and make calls to another, it's nice to have the authenticate path working correctly from Step 1. I have never used Pulumi, but I think the same path would apply; you want to focus on the business logic, and waiting for an EC2 to spin up and down while you're iterating gets annoying quickly. Once you have all the kinks worked out, you can drop in your actual EC2 module and expect the same authentication patterns (where many bugs happen), although the outputs would most likely need some tune-up.