|
100 | 100 | { |
101 | 101 | "diagram": { |
102 | 102 | "caption": "Secure Landing Zone with VSIs", |
103 | | - "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/${{version}}/reference-architectures/vsi-quickstart.drawio.svg", |
| 103 | + "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vsi-quickstart.drawio.svg", |
104 | 104 | "type": "image/svg+xml" |
105 | 105 | }, |
106 | 106 | "description": "The **QuickStart** flavor of Secure Landing Zone with VSIs requires at least 2 CPUs and 4 GB of memory.\n\nSecure Landing Zone with virtual server instances is implemented with virtual servers. It utilizes two separate 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.\n\nVirtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management.\n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation 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 configuration. Additional security services can be added such as Hyper Connect Crypto Service." |
|
383 | 383 | { |
384 | 384 | "diagram": { |
385 | 385 | "caption": "Secure Landing Zone with VSIs", |
386 | | - "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/${{version}}/reference-architectures/vsi-vsi.drawio.svg", |
| 386 | + "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vsi-vsi.drawio.svg", |
387 | 387 | "type": "image/svg+xml" |
388 | 388 | }, |
389 | 389 | "description": "Secure Landing Zone with virtual server instances is implemented with virtual servers running in a single, defined Virtual Private Cloud (VPC) which is used to manage the environment. The VPC is a multi-zoned, multi-subnet implementation that keeps your VPC secure and highly available. Virtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management. \n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation 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 configuration. Additional security services can be added such as Hyper Connect Crypto Service." |
|
668 | 668 | { |
669 | 669 | "diagram": { |
670 | 670 | "caption": "Secure infrastructure on VPC for regulated industries", |
671 | | - "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/${{version}}/reference-architectures/vpc.drawio.svg", |
| 671 | + "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vpc.drawio.svg", |
672 | 672 | "type": "image/svg+xml" |
673 | 673 | }, |
674 | 674 | "description": "Secure Landing Zone utilizes two separate 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.\n\nVirtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management.\n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation 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 configuration. Additional security services can be added such as Hyper Connect Crypto Service." |
|
991 | 991 | { |
992 | 992 | "diagram": { |
993 | 993 | "caption": "OpenShift Container Platform on VPC for regulated industries", |
994 | | - "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/${{version}}/reference-architectures/roks.drawio.svg", |
| 994 | + "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/roks.drawio.svg", |
995 | 995 | "type": "image/svg+xml" |
996 | 996 | }, |
997 | 997 | "description": "OpenShift Container Platform on VPC for regulated industries is implemented with a Red Hat Openshift cluster running in a single, defined Virtual Private Cloud (VPC) which is used to manage the environment. The VPC is a multi-zoned, multi-subnet implementation that keeps your VPC secure and highly available. Virtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management. \n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation 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 configuration. Additional security services can be added such as Hyper Connect Crypto Service." |
|
0 commit comments