Using STIM deploy with AWS provider does not respect leases

[gyoza]

INFO[0018] AWS credentials (REDACTED) from aws/MYCREDS active
5 seconds later rerun deploy
INFO[0010] AWS credentials (OTHER_REDACTED) from aws/MYCREDS active

[thorix]

The problem here is that stim creates new AWS creds each time you run a deploy. It doesn't reuse AWS creds or verify that the old ones can or should still work for the next deploy. Some idea of a configurable set of how long a deploy can take could be set. Then stim could look at the lease time and see if the current deploy needs a new cred based on the length of time the deploy could take.