1
0
Fork 0
mirror of synced 2025-04-06 06:33:34 +03:00

Update AWS

This commit is contained in:
Scottpedia 2020-08-18 11:29:17 -04:00
parent 576f2e41fc
commit 5ff957b9a7
5 changed files with 27 additions and 5 deletions

View file

@ -8,7 +8,7 @@ You can also use `t2.micro` instance as your server for your deployment, which i
## Available Customization Parameters:
- AWS EC2 Instance Type ([explained here](#instance-type-selection))
- AWS EC2 Instance Type
- OS for your VPN Server (Ubuntu16.04, Ubuntu18.04 or Debian9-stretch)
- Your VPN username
- Your VPN password
@ -18,7 +18,7 @@ You can also use `t2.micro` instance as your server for your deployment, which i
Make sure to do this with an **AWS ROOT ACCOUNT** or an **IAM ACCOUNT** with **ADMINISTRATION PRVILEGE**. AWS Cloudformation requires the template file to be store on AWS S3, while a [copy](./MonAug17-production1.0) is available on Github. If you want to make any contributions to this template, make sure to contact me so that I can update the template on S3.
If you are confused about the instance type available, check out [this section](#instance-type-selection).
If you are confused about the instance types available, go to the [FAQ](#faqs) section and check out **"Instance Type Selection"**.
Click the icon below to initiate the launching sequence.
@ -26,14 +26,36 @@ Click the icon below to initiate the launching sequence.
Make sure that the deployment is successful before going to the [Next Step : Configure VPN Clients](../docs/clients.md).
## Instance Type Selection
# FAQs
<details>
<summary>
Instance Type Selection
</summary>
I have made only a few general-purpose, x64-based instance types available. That's because not all instance types are available in all AWS Regions. Even some of the instance types available in the template are not available in certain AWS regions. So be careful which instance type to choose. The figure below shows the number of regions where each of the selectable instance type is available.
![](instance-type-sheet.png)
A spreadsheet that includes the raw instance data across all AWS regions is available [here](https://vpn-tutorial-template.s3.ca-central-1.amazonaws.com/Analysis+on+Regional+Availability+of+Selected+Instances+Types+on+AWS+EC2.xlsx).
</details>
<details>
<summary>
How to connect to the server via ssh after deployment?
</summary>
AWS does not allow users to access the instances with an SSH password. Instead, users are instructed to create "key pairs", which are used as credentials to access the instances via SSH.
The template here generates a key pair for you during the deployment, and that will be available as plain texts in the **"Output"** section after the stack is successfully created.
You need to note down that key file if you want to later access the VPN server via SSH.
![](show-key.png)
</details>
## Author
Copyright (C) 2020 [S. X. Liang](https://github.com/scottpedia)
Copyright (C) 2020 [S. X. Liang](https://github.com/scottpedia)
## Screenshots
<img src="specify-template.png" width="50%" height="50%" alt="Step 1"><img src="specify-parameters.png" width="50%" height="50%" alt="Step 2"><img src="confirm-iam.png" width="50%" height="50%" alt="Step 4">

BIN
aws/confirm-iam.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 334 KiB

BIN
aws/show-key.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 663 KiB

BIN
aws/specify-parameters.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 279 KiB

BIN
aws/specify-template.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 344 KiB