IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

website: Add code coloring to aws_security_group doc

Browse Source
This commit is contained in:
Paul Thrasher 2017-05-04 17:00:17 -07:00 committed by Martin Atkins
parent 58f5257678
commit 26a91abd0c
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/docs/providers/aws/r/security_group.html.markdown
View File

@ -45,7 +45,7 @@ resource "aws_security_group" "allow_all" {
Basic usage with tags: Basic usage with tags:
``` ```hcl
resource "aws_security_group" "allow_all" { resource "aws_security_group" "allow_all" {
name = "allow_all" name = "allow_all"
description = "Allow all inbound traffic" description = "Allow all inbound traffic"
@ -116,12 +116,14 @@ specifically re-create it if you desire that rule. We feel this leads to fewer
surprises in terms of controlling your egress rules. If you desire this rule to surprises in terms of controlling your egress rules. If you desire this rule to
be in place, you can use this `egress` block: be in place, you can use this `egress` block:
```hcl
egress { egress {
from_port = 0 from_port = 0
to_port = 0 to_port = 0
protocol = "-1" protocol = "-1"
cidr_blocks = ["0.0.0.0/0"] cidr_blocks = ["0.0.0.0/0"]
} }
```
## Usage with prefix list IDs ## Usage with prefix list IDs
@ -129,7 +131,7 @@ Prefix list IDs are managed by AWS internally. Prefix list IDs
are associated with a prefix list name, or service name, that is linked to a specific region. are associated with a prefix list name, or service name, that is linked to a specific region.
Prefix list IDs are exported on VPC Endpoints, so you can use this format: Prefix list IDs are exported on VPC Endpoints, so you can use this format:
``` ```hcl
# ... # ...
egress { egress {
from_port = 0 from_port = 0