Update README.md (#1086)
- change the url to the latest redirection destination - cli line fix - update year
This commit is contained in:
parent
8992213558
commit
7cb733c99a
@ -7,7 +7,7 @@ This template will create a fully-working IPsec VPN server on Amazon Elastic Com
|
||||
Available customization parameters:
|
||||
|
||||
- Amazon EC2 instance type
|
||||
> **Note**: It is possible that not all instance type options offered by this template are available in a specific AWS region. For example, you may not be able to deploy an `m5a.large` instance in `ap-east-1` (hypothetically). In that case, you might experience the following error during deployment: `The requested configuration is currently not supported. Please check the documentation for supported configurations`. Newly released regions are more prone to having this problem as there are less variety of instances. For more info about instance type availability, refer to [https://ec2instances.info](https://ec2instances.info).
|
||||
> **Note**: It is possible that not all instance type options offered by this template are available in a specific AWS region. For example, you may not be able to deploy an `m5a.large` instance in `ap-east-1` (hypothetically). In that case, you might experience the following error during deployment: `The requested configuration is currently not supported. Please check the documentation for supported configurations`. Newly released regions are more prone to having this problem as there are less variety of instances. For more info about instance type availability, refer to [https://instances.vantage.sh/](https://instances.vantage.sh/).
|
||||
- OS for your VPN server (Ubuntu 20.04/18.04, Debian 9, CentOS 8/7, Amazon Linux 2)
|
||||
> **Note:** Before using the Debian 9 image on EC2, you need to first subscribe at the AWS Marketplace: [Debian 9](https://aws.amazon.com/marketplace/pp/B073HW9SP3).
|
||||
- Your VPN username
|
||||
@ -69,7 +69,7 @@ You will need to save the private key from the **Outputs** tab to a file on your
|
||||
|
||||
To apply proper permissions to your private key file, run the following command under the directory where the file is located:
|
||||
```bash
|
||||
sudo chmod 400 key-file.pem
|
||||
$ sudo chmod 400 key-file.pem
|
||||
```
|
||||
|
||||
Example command to login to your EC2 instance using SSH:
|
||||
@ -80,4 +80,4 @@ $ ssh -i path/to/your/key-file.pem instance-username@instance-ip-address
|
||||
|
||||
## Author
|
||||
|
||||
Copyright (C) 2020-2021 [S. X. Liang](https://github.com/scottpedia)
|
||||
Copyright (C) 2020-2022 [S. X. Liang](https://github.com/scottpedia)
|
||||
|
Loading…
x
Reference in New Issue
Block a user