Sorry, I didn’t get it.
When we talk AWS, there is basically the Credentials Pair (AWS Access Key Id, AWS Secret Key). However, on EC2 in Particular, there’s also the SSH Key Pair, which is unrelated.
On EC2, AWS Stores only the public key, and sends you the private (although I don’t recommend - Generate yourself and make AWS import your Public Key - Its better trust me). If you want to share your user access to your EC2 instance, we’re talking SSH, so neither IAM nor even STS could be factored in.
What I suggest is, since the instance is on, to generate/pick each users’ public key, and modify their users (or single user) ~/.ssh/authorized_keys file. Just make sure to make it persistent, as I’m not sure if reboots will keep’em as-is.
There are better solutions for Key Management, specially from ssh.com (the authors of SSH Protocol, but not OpenSSH), and Chef is also a good fit for this case. YMMV.
Note we’re not talking about Network-Level Access (Security Groups). For this, I recommend you understand how Security Groups Work (its more than just Network Address + Port), or consider solutions like OpenVPN Access Server (which I love it for browsing EC2 stuff), as well as Services like Dome9 (http://dome9.com)
Hope it helps
|