aws-ec2-ssh | Manage AWS EC2 SSH access with IAM | AWS library

Upload SSH public key. Upload SSH public key. 1Check the releases and use the latest released RPM.
Upload your public SSH key to IAM: Open the Users section in the IAM Management Console Click the row with your user Select the Security Credentials tab Click the Upload SSH public key button at the bottom of the page Paste your public SSH key into the text-area and click the Upload SSH public key button to save
Attach the IAM permissions defined in iam_ssh_policy.json to the EC2 instances (by creating an IAM role and an Instance Profile)
Install the RPM1: rpm -i https://s3-eu-west-1.amazonaws.com/widdix-aws-ec2-ssh-releases-eu-west-1/aws-ec2-ssh-1.9.2-1.el7.centos.noarch.rpm
The configuration file is placed into /etc/aws-ec2-ssh.conf
The RPM creates a crontab file to run import_users.sh every 10 minutes. This file is placed in /etc/cron.d/import_users
Upload SSH public key. Upload SSH public key.
Upload your public SSH key to IAM: Open the Users section in the IAM Management Console Click the row with your user Select the Security Credentials tab Click the Upload SSH public key button at the bottom of the page Paste your public SSH key into the text-area and click the Upload SSH public key button to save
Attach the IAM permissions defined in iam_ssh_policy.json to the EC2 instances (by creating an IAM role and an Instance Profile)
Run the install.sh script as root on the EC2 instances. Run install.sh -h for help.
The configuration file is placed into /etc/aws-ec2-ssh.conf
Connect to your EC2 instances now using ssh $Username@$PublicName with $Username being your IAM user, and $PublicName being your server's name or IP address
Role for Cross-Account Access. Provide access between AWS accounts you own.
In the users account, create a new IAM role
Select Role Type Role for Cross-Account Access and select the option Provide access between AWS accounts you own
Put the dev account number in Account ID and leave Require MFA unchecked
Skip attaching a policy (we will do this soon)
Review the new role and create it
Select the newly created role
In the Permissions tab, expand Inline Policies and create a new inline policy
Select Custom Policy
Paste the content of the iam_ssh_policy.json file and replace <YOUR_USERS_ACCOUNT_ID_HERE> with the AWS Account ID of the users account.
For your EC2 instances, you need a IAM role that allows the sts:AssumeRole action.
In the dev account, create a new IAM role
Select ROle Type AWS Service Roles and select the option Amazon EC2
Skip attaching a policy (we will do this soon)
Review the new role and create it
Select the newly created role
In the Permissions tab, expand Inline Policies and create a new inline policy
Select Custom Policy
Paste the content of the iam_crossaccount_policy.json file and replace <YOUR_USERS_ACCOUNT_ID_HERE> with the AWS Account ID of the users account and <YOUR_USERS_ACCOUNT_ROLE_NAME_HERE> with the IAM rol name that you created in the users account
Create/edit the file /etc/aws-ec2-ssh.conf and add this line: ASSUMEROLE="IAM-ROLE-ARN or run the install.sh script with the -a argument