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
When contributing to this repository, please first discuss the change you wish to make via issue,
4
+
email, or any other method with the owners of this repository before making a change.
5
+
6
+
Please note we have a code of conduct, please follow it in all your interactions with the project.
7
+
8
+
## Pull Request Process
9
+
10
+
1. Update the README.md with details of changes including example hcl blocks and [example files](./examples) if appropriate.
11
+
2. Run pre-commit hooks `pre-commit run -a`.
12
+
3. Once all outstanding comments and checklist items have been addressed, your contribution will be merged! Merged PRs will be included in the next release. The terraform-aws-vpc maintainers take care of updating the CHANGELOG as they merge.
13
+
14
+
## Checklists for contributions
15
+
16
+
-[ ] Add [semantics prefix](#semantic-pull-requests) to your PR or Commits (at least one of your commit groups)
17
+
-[ ] CI tests are passing
18
+
-[ ] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-vpc/#doc-generation
19
+
-[ ] Run pre-commit hooks `pre-commit run -a`
20
+
21
+
## Semantic Pull Requests
22
+
23
+
To generate changelog, Pull Requests or Commits must have semantic and must follow conventional specs below:
24
+
25
+
-`feat:` for new features
26
+
-`fix:` for bug fixes
27
+
-`improvement:` for enhancements
28
+
-`docs:` for documentation and examples
29
+
-`refactor:` for code refactoring
30
+
-`test:` for tests
31
+
-`ci:` for CI purpose
32
+
-`chore:` for chores stuff
33
+
34
+
The `chore` prefix skipped during changelog generation. It can be used for `chore: update changelog` commit message by example.
Copy file name to clipboardExpand all lines: README.md
+20-3Lines changed: 20 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,14 @@ You can add additional tags with `intra_subnet_tags` as with other subnet types.
120
120
121
121
VPC Flow Log allows to capture IP traffic for a specific network interface (ENI), subnet, or entire VPC. This module supports enabling or disabling VPC Flow Logs for entire VPC. If you need to have VPC Flow Logs for subnet or ENI, you have to manage it outside of this module with [aws_flow_log resource](https://www.terraform.io/docs/providers/aws/r/flow_log.html).
122
122
123
+
### VPC Flow Log Examples
124
+
125
+
By default `file_format` is `plain-text`. You can also specify `parquet` to have logs written in Apache Parquet format.
126
+
127
+
```
128
+
flow_log_file_format = "parquet"
129
+
```
130
+
123
131
### Permissions Boundary
124
132
125
133
If your organization requires a permissions boundary to be attached to the VPC Flow Log role, make sure that you specify an ARN of the permissions boundary policy as `vpc_flow_log_permissions_boundary` argument. Read more about required [IAM policy for publishing flow logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-cwl.html#flow-logs-iam).
@@ -183,19 +191,25 @@ It is possible to integrate this VPC module with [terraform-aws-transit-gateway
-[Few tests and edge case examples](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/issues)
185
193
194
+
## Contributing
195
+
196
+
Report issues/questions/feature requests on in the [issues](https://github.com/terraform-aws-modules/terraform-aws-vpc/issues/new) section.
197
+
198
+
Full contributing [guidelines are covered here](.github/contributing.md).
199
+
186
200
<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
| <aname="input_flow_log_cloudwatch_log_group_retention_in_days"></a> [flow\_log\_cloudwatch\_log\_group\_retention\_in\_days](#input\_flow\_log\_cloudwatch\_log\_group\_retention\_in\_days)| Specifies the number of days you want to retain log events in the specified log group for VPC flow logs. |`number`|`null`| no |
371
385
| <aname="input_flow_log_destination_arn"></a> [flow\_log\_destination\_arn](#input\_flow\_log\_destination\_arn)| The ARN of the CloudWatch log group or S3 bucket where VPC Flow Logs will be pushed. If this ARN is a S3 bucket the appropriate permissions need to be set on that bucket's policy. When create\_flow\_log\_cloudwatch\_log\_group is set to false this argument must be provided. |`string`|`""`| no |
372
386
| <aname="input_flow_log_destination_type"></a> [flow\_log\_destination\_type](#input\_flow\_log\_destination\_type)| Type of flow log destination. Can be s3 or cloud-watch-logs. |`string`|`"cloud-watch-logs"`| no |
387
+
| <aname="input_flow_log_file_format"></a> [flow\_log\_file\_format](#input\_flow\_log\_file\_format)| (Optional) The format for the flow log. Valid values: `plain-text`, `parquet`. |`string`|`"plain-text"`| no |
388
+
| <aname="input_flow_log_hive_compatible_partitions"></a> [flow\_log\_hive\_compatible\_partitions](#input\_flow\_log\_hive\_compatible\_partitions)| (Optional) Indicates whether to use Hive-compatible prefixes for flow logs stored in Amazon S3. |`bool`|`false`| no |
373
389
| <aname="input_flow_log_log_format"></a> [flow\_log\_log\_format](#input\_flow\_log\_log\_format)| The fields to include in the flow log record, in the order in which they should appear. |`string`|`null`| no |
374
390
| <aname="input_flow_log_max_aggregation_interval"></a> [flow\_log\_max\_aggregation\_interval](#input\_flow\_log\_max\_aggregation\_interval)| The maximum interval of time during which a flow of packets is captured and aggregated into a flow log record. Valid Values: `60` seconds or `600` seconds. |`number`|`600`| no |
391
+
| <aname="input_flow_log_per_hour_partition"></a> [flow\_log\_per\_hour\_partition](#input\_flow\_log\_per\_hour\_partition)| (Optional) Indicates whether to partition the flow log per hour. This reduces the cost and response time for queries. |`bool`|`false`| no |
375
392
| <aname="input_flow_log_traffic_type"></a> [flow\_log\_traffic\_type](#input\_flow\_log\_traffic\_type)| The type of traffic to capture. Valid values: ACCEPT, REJECT, ALL. |`string`|`"ALL"`| no |
376
393
| <aname="input_igw_tags"></a> [igw\_tags](#input\_igw\_tags)| Additional tags for the internet gateway |`map(string)`|`{}`| no |
377
394
| <aname="input_instance_tenancy"></a> [instance\_tenancy](#input\_instance\_tenancy)| A tenancy option for instances launched into the VPC |`string`|`"default"`| no |
0 commit comments