Skip to content
This repository was archived by the owner on Nov 8, 2021. It is now read-only.

Commit 3f60633

Browse files
lukewaitemichaelwittig
authored andcommitted
Formatting fixes (#58)
1 parent 9ea9c41 commit 3f60633

File tree

1 file changed

+23
-23
lines changed

1 file changed

+23
-23
lines changed

README.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -9,27 +9,27 @@ A picture is worth a thousand words:
99
![Architecture](./docs/architecture.png?raw=true "Architecture")
1010

1111
* On first start, all IAM users are imported and local UNIX users are created
12-
* The import also runs every 10 minutes (via cron - calls `import_users.sh`)
13-
* You can control which IAM users get a local UNIX user and are therefore able to login
14-
* all (default)
15-
* only those in specific IAM groups
16-
* You can control which IAM users are given sudo access
12+
* The import also runs every 10 minutes (via cron - calls `import_users.sh`)
13+
* You can control which IAM users get a local UNIX user and are therefore able to login
14+
* all (default)
15+
* only those in specific IAM groups
16+
* You can control which IAM users are given sudo access
1717
* none (default)
1818
* all
1919
* only those in a specific IAM group
20-
* You can specify the local UNIX groups for the local UNIX users
21-
* You can assume a role before contacting AWS IAM to get users and keys (e.g. if your IAM users are in another AWS account)
20+
* You can specify the local UNIX groups for the local UNIX users
21+
* You can assume a role before contacting AWS IAM to get users and keys (e.g. if your IAM users are in another AWS account)
2222
* On every SSH login, the EC2 instance tries to fetch the public key(s) from IAM using sshd's `AuthorizedKeysCommand`
23-
* As soon as the public SSH key is deleted from the IAM user a login is no longer possible
23+
* As soon as the public SSH key is deleted from the IAM user a login is no longer possible
2424

2525
### Demo with CloudFormation
2626

2727
1. Upload your public SSH key to IAM:
28-
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
29-
2. Click the row with your user
30-
3. Select the **Security Credentials** tab
31-
4. Click the **Upload SSH public key** button at the bottom of the page
32-
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
28+
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
29+
2. Click the row with your user
30+
3. Select the **Security Credentials** tab
31+
4. Click the **Upload SSH public key** button at the bottom of the page
32+
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
3333
2. Create a CloudFormation stack based on the `showcase.yaml` template
3434
3. Wait until the stack status is `CREATE_COMPLETE`
3535
4. Copy the `PublicName` from the stack's outputs
@@ -42,11 +42,11 @@ A picture is worth a thousand words:
4242
> Check the [releases](https://github.com/widdix/aws-ec2-ssh/releases) and replace `1.1.0` with the latest released version.
4343
4444
1. Upload your public SSH key to IAM:
45-
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
46-
2. Click the row with your user
47-
3. Select the **Security Credentials** tab
48-
4. Click the **Upload SSH public key** button at the bottom of the page
49-
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
45+
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
46+
2. Click the row with your user
47+
3. Select the **Security Credentials** tab
48+
4. Click the **Upload SSH public key** button at the bottom of the page
49+
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
5050
2. Attach the IAM permissions defined in `iam_ssh_policy.json` to the EC2 instances (by creating an IAM role and an Instance Profile)
5151
3. Install the RPM: `rpm -i https://s3-eu-west-1.amazonaws.com/widdix-aws-ec2-ssh-releases-eu-west-1/aws-ec2-ssh-1.1.0-1.el7.centos.noarch.rpm`
5252
4. The configuration file is placed into `/etc/aws-ec2-ssh.conf`
@@ -55,11 +55,11 @@ A picture is worth a thousand words:
5555
### Install via install.sh script
5656

5757
1. Upload your public SSH key to IAM:
58-
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
59-
2. Click the row with your user
60-
3. Select the **Security Credentials** tab
61-
4. Click the **Upload SSH public key** button at the bottom of the page
62-
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
58+
1. Open the Users section in the [IAM Management Console](https://console.aws.amazon.com/iam/home#users)
59+
2. Click the row with your user
60+
3. Select the **Security Credentials** tab
61+
4. Click the **Upload SSH public key** button at the bottom of the page
62+
5. Paste your public SSH key into the text-area and click the **Upload SSH public key** button to save
6363
2. Attach the IAM permissions defined in `iam_ssh_policy.json` to the EC2 instances (by creating an IAM role and an Instance Profile)
6464
3. Run the `install.sh` script as `root` on the EC2 instances. Run `install.sh -h` for help.
6565
4. 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

0 commit comments

Comments
 (0)