invalid user: ‘vagrant:vagrant’ fix

This means you don't have such user in guest OS. Check also `override.ssh.username` in machine Vagrantfile

AWS after destroying instance creates it again fix

When you cannot stop and destroy instance and something creates them again, remove autoscaling group/configuration from menu on the left.

The issue appears after using ecs-cli utility and creating EC2 clusters.

Aws ecs-cli created fargate instance instead of ec2 fix

Be sure you ran ecs-cli up --capability-iam --instance-type t2.micro  with argument --cluster-config <configname>
, where configname is already created with ecs-cli configure command.