Skip to content
This repository was archived by the owner on Mar 6, 2022. It is now read-only.

Commit fa0d86f

Browse files
authored
Update README.md
1 parent d466a72 commit fa0d86f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,23 +23,23 @@ At a high level, awslambdaproxy proxies TCP/UDP traffic through AWS Lambda regio
2323

2424
## Terraform
2525

26-
1. Clone repository and go to Terraform component folder:
26+
1. Clone repository and go to the `deployment/terraform` directory:
2727
```sh
2828
git clone git@github.com:dan-v/awslambdaproxy.git && cd awslambdaproxy/deployment/terraform
2929
```
3030

31-
2. Configure your Terrafom backend. Read more about Terraform backend [here](https://www.terraform.io/docs/backends/index.html).
31+
2. Install [Terraform](https://www.terraform.io/) and configure your Terraform backend. Read more about Terraform backends [here](https://www.terraform.io/docs/backends/index.html).
3232

33-
3. Create and fill variable defenitions file ([read more here](https://www.terraform.io/docs/configuration/variables.html#variable-definitions-tfvars-files)) if you don't want to use default variables values.
33+
3. Create and fill in a variable definitions file ([read more here](https://www.terraform.io/docs/configuration/variables.html#variable-definitions-tfvars-files)) if you don't want to use default variables values defined in `variables.tf`.
3434

35-
4. Run those commands to init and apply configuration:
35+
4. Run these commands to init and apply configuration:
3636
```sh
3737
terraform init && terraform apply -auto-approve
3838
```
3939

40-
It will create all dependent resources and run awslambdaproxy inside Docker container. EC2 instance SSH key can be found in AWS Secret Manager in your [AWS Management Console](https://console.aws.amazon.com/).
40+
It will create all dependent resources and run awslambdaproxy inside a Docker container. EC2 instance SSH key can be found in AWS Secret Manager in your [AWS Management Console](https://console.aws.amazon.com/).
4141

42-
NOTE: Some AWS regions have a big list of IP CIDR blocks and they can overhead default limits of security group ([read more](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html#vpc-limits-security-groups)). Need to make limit increase request through the AWS Support Center by choosing Create Case and then choosing Service Limit Increase to prevent deployment issues.
42+
NOTE: Some AWS regions have a big list of IP CIDR blocks and they can exceed the default limits of security groups ([read more](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html#vpc-limits-security-groups)). In that case, you'll need to make a limit increase request through the `AWS Support Center` by choosing `Create Case` and then choosing `Service Limit Increase` to prevent deployment issues.
4343

4444
## Manual
4545

0 commit comments

Comments
 (0)