Skip to content

Commit d2f2ef9

Browse files
Update deploy-arch-ibm-slz-vpc-standard.md (#1045)
1 parent 729788d commit d2f2ef9

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

reference-architectures/deploy-arch-ibm-slz-vpc-standard.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22

33
copyright:
4-
years: 2023, 2024
5-
lastupdated: "2024-09-26"
4+
years: 2023, 2024, 2025
5+
lastupdated: "2025-09-03"
66

7-
keywords:
7+
keywords: Cloud foundation for VPC, VPC Landing Zone
88

99
subcollection: deployable-reference-architectures
1010

@@ -29,7 +29,7 @@ docs: https://cloud.ibm.com/docs/secure-infrastructure-vpc
2929
image_source: https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone/blob/main/reference-architectures/vpc.drawio.svg
3030

3131
related_links:
32-
- title: "VPC landing zone - Standard variation"
32+
- title: "Cloud foundation for VPC - Standard (Financial Services edition) variation"
3333
url: "https://cloud.ibm.com/docs/deployable-reference-architectures?topic=deployable-reference-architectures-vpc-ra"
3434
description: "A deployable architecture that is based on the IBM Cloud for Financial Services reference and that provides virtual servers in a secure VPC for your workloads."
3535

@@ -43,27 +43,27 @@ content-type: reference-architecture
4343

4444
{{site.data.keyword.attribute-definition-list}}
4545

46-
# VPC landing zone - Standard variation
46+
# Cloud foundation for VPC - Standard (Financial Services edition) variation
4747
{: #vpc-ra}
4848
{: toc-content-type="reference-architecture"}
4949
{: toc-industry="Banking,FinancialSector"}
5050
{: toc-use-case="Cybersecurity"}
5151
{: toc-compliance="FedRAMP"}
5252
{: toc-version="8.5.0"}
5353

54-
The Standard variation of the VPC landing zone deployable architecture uses two Virtual Private Clouds (VPC), a Management VPC, and a Workload VPC to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure. A transit gateway connects the VPCs to each other and Virtual Private Endpoints are used connect to IBM Cloud services.
54+
The Standard (Financial Services edition) variation of the Cloud foundation for VPC deployable architecture uses two Virtual Private Clouds (VPC), a Management VPC, and a Workload VPC to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure. A transit gateway connects the VPCs to each other and Virtual Private Endpoints are used connect to IBM Cloud services.
5555

5656
IBM Cloud Flow Logs for VPC enables the collection and storage of information about the internet protocol (IP) traffic that is going to and from network interfaces within your VPC. In addition, Activity Tracker logs events from enabled services. IBM Cloud Flow Logs for VPC and Activity Tracker are included in this deployable architecture. You can add more security services, such as Hyper Protect Crypto Services.
5757

5858
## Architecture diagram
5959
{: #ra-vpc-architecture-diagram}
6060

61-
![Architecture diagram for the Standard variation of VPC landing zone](vpc.drawio.svg "Architecture diagram of VPC landing zone deployable architecture"){: caption="Figure 1. Standard variation of VPC landing zone" caption-side="bottom"}{: external download="vpc.drawio.svg"}
61+
![Architecture diagram for the Standard variation of VPC landing zone](vpc.drawio.svg "Architecture diagram of VPC landing zone deployable architecture"){: caption="Standard (Financial Services edition) variation of Cloud foundation for VPC" caption-side="bottom"}{: external download="vpc.drawio.svg"}
6262

6363
## Design requirements
6464
{: #ra-vpc-qs-design-requirements}
6565

66-
![Design requirements for VPC landing zone](heat-map-deploy-arch-slz-vpc-standard.svg "Design requirements"){: caption="Figure 2. Scope of the design requirements" caption-side="bottom"}
66+
![Design requirements for VPC landing zone](heat-map-deploy-arch-slz-vpc-standard.svg "Design requirements"){: caption="Scope of the design requirements" caption-side="bottom"}
6767

6868
<!--
6969
TODO: Add the typical use case for the architecture.
@@ -81,7 +81,7 @@ business challenge, or target cloud environments.
8181
| * Provide infrastructure/application administration access to monitor, operate, and maintain the environment. \n * Limit the number of infrastructure/application administration entry points to ensure security audit. | Management VPC service | | |
8282
| * Provide infrastructure for service management components like backup, monitoring, IT service management, shared storage \n * Ensure you can reach all IBM Cloud and on-premises services | Workload VPC service | | |
8383
| * Set up network for all created services \n * Isolate network for all created services \n * Ensure all created services are interconnected | Secure landing zone components | Create a minimum set of required components for a secure landing zone | Create a modified set of required components for a secure landing zone in preset |
84-
{: caption="Table 1. Architecture decisions" caption-side="bottom"}
84+
{: caption="Architecture decisions" caption-side="bottom"}
8585

8686
### Network security architecture decisions
8787
{: #ra-vpc-components-arch-net-sec}
@@ -91,7 +91,7 @@ business challenge, or target cloud environments.
9191
| * Isolate management VPC and allow only a limited number of network connections \n * All other connections from or to management VPC are forbidden | ACL and security group rules in management VPC| | More ports might be opened in preset or added manually after deployment |
9292
| * Isolate workload VPC and allow only a limited number of network connections \n * All other connections from or to workload VPC are forbidden | ACL and security group rules in workload VPC | | More ports might be opened in preset or added manually after deployment |
9393
| Load VPN configuration to simplify VPN setup | VPNs | VPN configuration is the responsibility of the customer | |
94-
{: caption="Table 2. Network security architecture decisions" caption-side="bottom"}
94+
{: caption="Network security architecture decisions" caption-side="bottom"}
9595

9696
<!--
9797
## Compliance

0 commit comments

Comments
 (0)