2022 June 13
Issues with cli configured aws resources can almost always be found in the differences between your cli resource and a manually configured one. What you want to do to find the solution quickly is to manually configure a resource in the dashbord and compare it to yours. For example, if you try to configure a t2.micro instance with cli and you can't login then go manually configure an instance with the rules you wanted and see if ssh login works.
For example, in this case I noticed that when you create a new vpc with the cli it does not create the right rule in the route table to forward traffic to the igw. The dashboard configured instance lives in a default vpc that does have such a rule in its route table. So the solution is to make sure to add your own rule forwarding that traffic.
I’ve seen much time wasted because people refuse to compare their resources to a working, manually configured copy.
If you have a project or you want help or advice with aws you can hire me.