No t3 instance support
Cheaper and more performant t3 instances with gp3 disk types don't appear to be supported due to lack of driver support.
AWS Kali does not come with any pen test tool
I had try to run nmap , burpsuite and metasploit but could not manage to execute any penetration testing tools. Is this a blank Kali image which does not pre-install with any tools. Disappointed with this AMI Kali, hopefully AWS could provide us with some advice.
no tools
This strange version of kali on aws doesnt come witha any penetrating tools.
I suppose they will fix this beacuse its really annoying
Kali build without the tools
Connected without a problem. As others have said, connect with the username kali. And if you are having problems connecting over SSH, make sure you create a rule in the AWS Security Group for it. It is a bummer that none of the tools that would normally be part of Kali are installed though, so what's the point?
No tools or GUI? Why not just use Debian and install all your own tools.
Who thought up a testing linux without any testing tools?
NOT included with your Kali: nmap, nc, wfuzz, gobuster, dirb, burpsuite, . . . .
Also, no GUI so forget BurpSuite or using a browser.
Kali in name only
Like others mentioned, there is not even one single pen tool installed. What's the point of using Kali if I have to install all the pen tools myself?
There is no any pen testing tool
Where are the usuals tools like wpscan and others. ?
After I connect to EC2 via RDP, there is an empty desktop and at application menu there aren't any tools that usually comes with Kali
https://bugs.kali.org/view.php?id=6094
This is bugged read here please https://bugs.kali.org/view.php?id=6094 and try to contact someone to upload an older version at least. Iptables bug.
Cannot connect
Like the others, I cannot connect to this machine after it is launched. SSH doesn't even connect to allow authentication with the keys.
Can't login to kali linux 2020
There is definitely some issue with kali linux 2020 AMI. Never allowed to login over ssh and not even port 22 is listening to telnet. which suspect something fishy and need to look in to by the provider