This is a bit of belt and suspenders, but it works and doesn’t throw irrational errors that keep you chasing your tail. Ideally you should not need the AWS_ACCESS_KEY and ID in your .bash_profile file, but some functions seem to need it.

Kitchen List: Check your Instances and Actions

Kitchen Create: Create an instance

$ kitchen create default-ubuntu-1404
-----> Starting Kitchen (v1.4.2)
-----> Creating <default-ubuntu-1404>...
If you are not using an account that qualifies under the AWS free-tier, you may be charged to run these suites.
The charge should be minimal, but neither Test Kitchen nor its maintainers are responsible for your incurred costs.
Instance <i-d4f71865> requested.
EC2 instance <i-d4f71865> created.
Waited 0/300s for instance <i-d4f71865> to become ready.
Waited 5/300s for instance <i-d4f71865> to become ready.
Waited 10/300s for instance <i-d4f71865> to become ready.
Waited 15/300s for instance <i-d4f71865> to become ready.
Waited 20/300s for instance <i-d4f71865> to become ready.
Waited 25/300s for instance <i-d4f71865> to become ready.
Waited 30/300s for instance <i-d4f71865> to become ready.
Waited 35/300s for instance <i-d4f71865> to become ready.
EC2 instance <i-d4f71865> ready.
Waiting for SSH service on 172.31.63.224:22, retrying in 3 seconds
Waiting for SSH service on 172.31.63.224:22, retrying in 3 seconds
Waiting for SSH service on 172.31.63.224:22, retrying in 3 seconds
[SSH] Established
Finished creating <default-ubuntu-1404> (1m9.39s).
-----> Kitchen is finished. (1m9.46s)
$ kitchen list
Instance Driver Provisioner Verifier Transport Last Action
default-rhel-71 Ec2 ChefSolo Busser Ssh <Not Created>
default-ubuntu-1404 Ec2 ChefSolo Busser Ssh Created