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: examples/fscloud/README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,13 +3,13 @@
3
3
This example demonstrates how to use the [fscloud profile](../../profiles/fscloud/) module to lay out a complete "secure by default" coarse-grained CBR topology in a given account.
4
4
5
5
This examples is designed to show case some of the key customization options for the module. In addition to the pre-wired CBR rules documented at [fscloud profile](../../profiles/fscloud/), this examples show how to customize the module to:
6
-
1. Open up network traffic flow from ICD mongodb, ICD Postgresql to the Key Protect private endpoints
7
-
2. Open up network traffic flow from Schematics to Key Protect public endpoints
8
-
3. Open up network traffic flow from a block of IPs to the Schematics public endpoint
9
-
4. Open up network traffic flow from the VPC created in this example to ICD postgresql private endpoints
6
+
1. Open up network traffic flow from ICD mongodb, ICD Postgresql to the Key Protect private endpoints.
7
+
2. Open up network traffic flow from Schematics to Key Protect public endpoints.
8
+
3. Open up network traffic flow from a block of IPs to the Schematics public endpoint.
9
+
4. Open up network traffic flow from the VPC created in this example to ICD postgresql private endpoints.
10
10
11
11
Context: this examples covers a "pseudo" real-world scenario where:
12
-
1. ICD Mongodb, and Postgresql instances are encrypted using keys storage in Key Protect.
12
+
1. ICD Mongodb and Postgresql instances are encrypted using keys storage in Key Protect.
13
13
2. Schematics is used to execute terraform that create Key Protect keys and key ring over its public endpoint.
14
14
3. Operators use machines with a set list of public IPs to interact with Schematics.
15
15
4. Applications are running the VPC and need access to PostgreSQL via the private endpoint - eg: a VPE.
Copy file name to clipboardExpand all lines: modules/fscloud/README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,10 @@ This module creates default coarse-grained CBR rules in a given account followin
4
4
- COS -> KMS
5
5
- Block storage -> KMS
6
6
- ROKS -> KMS
7
-
- Activity Tracker route -> COS (pending addition of AT as zone)
8
-
- VPCs -> container registry
7
+
- Activity Tracker route -> COS
9
8
- VPCs where clusters are deployed -> COS
9
+
- VPCs -> container registry
10
+
- All ICD -> KMS
10
11
11
12
This module is designed to allow the consumer to add additional custom rules to open up additional flows necessarity for their usage. See the `custom_rule_contexts_by_service` input variable, and an [usage example](../../examples/fscloud/) demonstrating how to open up more flows.
12
13
@@ -48,6 +49,7 @@ The services 'compliance', 'directlink', 'iam-groups', 'containers-kubernetes',
48
49
| <aname="input_allow_at_to_cos"></a> [allow\_at\_to\_cos](#input\_allow\_at\_to\_cos)| Set rule for Activity Tracker to COS, default is true |`bool`|`true`| no |
49
50
| <aname="input_allow_block_storage_to_kms"></a> [allow\_block\_storage\_to\_kms](#input\_allow\_block\_storage\_to\_kms)| Set rule for block storage to KMS, default is true |`bool`|`true`| no |
50
51
| <aname="input_allow_cos_to_kms"></a> [allow\_cos\_to\_kms](#input\_allow\_cos\_to\_kms)| Set rule for COS to KMS, default is true |`bool`|`true`| no |
52
+
| <aname="input_allow_icd_to_kms"></a> [allow\_icd\_to\_kms](#input\_allow\_icd\_to\_kms)| Set rule for ICD to KMS, deafult is true |`bool`|`true`| no |
51
53
| <aname="input_allow_roks_to_kms"></a> [allow\_roks\_to\_kms](#input\_allow\_roks\_to\_kms)| Set rule for ROKS to KMS, default is true |`bool`|`true`| no |
52
54
| <aname="input_allow_vpcs_to_container_registry"></a> [allow\_vpcs\_to\_container\_registry](#input\_allow\_vpcs\_to\_container\_registry)| Set rule for VPCs to container registry, default is true |`bool`|`true`| no |
53
55
| <aname="input_allow_vpcs_to_cos"></a> [allow\_vpcs\_to\_cos](#input\_allow\_vpcs\_to\_cos)| Set rule for VPCs to COS, default is true |`bool`|`true`| no |
validate_allow_rules=var.allow_cos_to_kms|| var.allow_block_storage_to_kms|| var.allow_roks_to_kms|| var.allow_vpcs_to_container_registry|| var.allow_vpcs_to_cos?true:tobool("Minimum of one rule has to be set to True")
189
186
## define FsCloud pre-wired CBR rule context - contains the known default flow that must be open for fscloud ref architecture
0 commit comments