generated from terraform-ibm-modules/terraform-ibm-module-template
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: adopt best practises for VPE gateway examples (#544)
- Loading branch information
Showing
17 changed files
with
21 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,12 @@ | ||
# End-to-end example | ||
# Advanced dedicated service VPE gateway | ||
|
||
This example creates the following infrastructure: | ||
- A resource group, if one is not passed in. | ||
- A VPC, if one is not passed in. | ||
- The VPC is created with three subnets across the three availability zones of the region that is passed as input. | ||
- A security group in the VPC. | ||
- The security group is created with a single inbound rule that allows traffic from resources that are attached to the default VPC security group. This rule is added as an example. | ||
- Two virtual private endpoint (VPE) gateways. By default, one VPE to COS and another VPE to Key Protect are created. You can change the defaults by using the `service_endpoints` input. | ||
- Two virtual private endpoint (VPE) gateways are created. One to COS and the other VPE to Key Protect. | ||
- Each of the two virtual private endpoint gateways are attached to the three VPC subnets. | ||
- The new security group is attached to the two VPE gateways. | ||
- A dedicated postgresql instance with a VPE gateway from the VPC |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# Basic multi-tenant VPE gateway | ||
|
||
This example creates the following infrastructure: | ||
- A resource group, if one is not passed in. | ||
- A VPC | ||
- The VPC is created with three subnets across the three availability zones of the region that is passed as input. | ||
- A virtual private endpoint (VPE) gateways for every multitenant service supported |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters