During first usage of Klotho I followed the "Your First Kloto App" flow from documentation. What I found was that I spent a lot of extra time to get my local environment set up. Mainly related to Permissions for my AWS user. The points that would have saved me time and made experience smoother would have been: All required environment setup should be evaluated as early as possible in Klotho execution, I suggest at Klotho compile time or somewhere very early in deployment steps in order to not waste time: * Check that aws can authenticate (Maybe just do an "aws get-user"?) * Check that docker deamon is running and can connect to socket (This happens very late in Pulumi build script, so it takes a lot of time before the warning arrives. That time is wasted if docker is not setup) * Explicitly list all Policy's the AWS user should have permissions for at compile time. Use the exact name of the policy as shown in AWS IAM interface. (This warning is not shown until latest point in Pulumi-script so it takes a lot of iterations to get all the correct permissions set up, the errors in Pulumi do not say the exact permissions Policy to use. I hate working with permissions on the various cloud providers interfaces...)