You can run wireshark on remote server (e.g. via ssh) and transfer results back to your machine for convenience.
E.g. this article has an example: ssh firstname.lastname@example.org 'tshark -f "port !22" -w -' | wireshark -k -i - - I'll run capture on remote machine, pipe results to local wireshark where you'd be able to see results in nice GUI.
Private keys should be go-rw and public keys should be go-w at least.
In other words, permission 0660 is bad. chmod go-rw or 0600
Note also that the parent directory must also not be writable to anyone but the owner, so it should be 700 or 750
The reasoning here:
A private key is pretty useless if it is readable to others.
Both public key or private key ...
If the key pair does not exist (in the AWS region required), it can be created using the aws-cli
For example, this assumes your AWS credentials are enabled already and your IAM permissions allow creating a key pair:
To get this working either disable firewall or allow required port in firewall. Off course, still you need to login into ec2 instance to get this done. There are 3 ways to connect with ec2 instance
SSH is not working so I choose Session Manager (Browser based ssh). I follow this video and was able to connect with instance through session manager.