You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,7 +195,8 @@ Sometimes it is handy to have public access to Redshift clusters (for example if
195
195
This module is able to provision the collection of VPC Flow Logs by setting `enable_flow_log = true`.
196
196
The [default behaviour](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/complete-vpc) will push the Flow Logs to a CloudWatch log group that gets created together the required IAM role.
197
197
Through the module's arguments it is possible to pass in an existing [CloudWatch log group](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-cloudwatch-log-group) and/or an existing [IAM role](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-cloudwatch-role) to be used instead of creating these resources.
198
-
It is also possible to pass in a [S3 bucket](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-s3-bucket) as the destination for the logs, instead of a CloudWatch log group.
198
+
It is also possible to push FLow Logs to S3.
199
+
To that end the module allows for a [S3 bucket](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-s3-bucket) to be proivided as the destination for the logs, or to [have it created by the module](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-create-s3-bucket).
199
200
200
201
## Examples
201
202
@@ -206,6 +207,7 @@ It is also possible to pass in a [S3 bucket](https://github.com/terraform-aws-mo
206
207
*[Flow Log CloudWatch log group provided](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-cloudwatch-log-group)
207
208
*[Flow Log IAM role for CloudWatch provided](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/vpc-flow-provided-cloudwatch-role)
* Few tests and edge cases examples: [#46](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/issue-46-no-private-subnets), [#44](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/issue-44-asymmetric-private-subnets), [#108](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/issue-108-route-already-exists)
210
212
211
213
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
Configuration in this directory creates set of VPC resources with FLow Logs enabled and configured to push to a new S3 bucket.
4
+
5
+
## Usage
6
+
7
+
To run this example you need to execute:
8
+
9
+
```bash
10
+
$ terraform init
11
+
$ terraform plan
12
+
$ terraform apply
13
+
```
14
+
15
+
Note that this example may create resources which can cost money (AWS Elastic IP, for example). Run `terraform destroy` when you don't need these resources.
16
+
17
+
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
18
+
## Outputs
19
+
20
+
| Name | Description |
21
+
|------|-------------|
22
+
| azs | A list of availability zones spefified as argument to this module |
23
+
| nat\_public\_ips | List of public Elastic IPs created for AWS NAT Gateway |
24
+
| private\_subnets | List of IDs of private subnets |
25
+
| public\_subnets | List of IDs of public subnets |
0 commit comments