| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-03-30 | ||
| keywords | |||
| subcollection | ContinuousDelivery |
{{site.data.keyword.attribute-definition-list}}
{: #service-dependencies}
{{site.data.keyword.contdelivery_short}} will be discontinued in the following regions on 10 April 2026: eu-es and jp-osa. This discontinuation also applies to any features provided within the service, including Code Risk Analyzer and {{site.data.keyword.DRA_short}}. Learn more {: important}
{{site.data.keyword.contdelivery_short}} will be discontinued in the following regions on 12 February 2027: au-syd, ca-mon, ca-tor, us-east. Code Risk Analyzer and {{site.data.keyword.DRA_short}} will also be deprecated in all regions on that date. However, if a region has no active usage of these features, the features in that region may be discontinued earlier and stop accepting new instances. Learn more {: important}
If a service depends on other {{site.data.keyword.cloud_notm}} services, there can be impacts if any of the dependent services are having issues. The dependency severity indicates the impact to the service when the dependency is down. {: shortdesc}
Critical : When the the dependency is down, the service is down.
Significant : When the dependency is down, the service features are impacted.
Medium : When the dependency is down, the service might be impacted and a workaround is possible.
Minimal : When the dependency is down, the main service features are not impacted.
{: #data-and-control-plane-deployment}
The following dependencies apply to the following deployment locations: Dallas (us-south), Frankfurt (eu-de), London (eu-gb), Sao Paulo (br-sao), Sydney (au-syd), Tokyo (jp-tok), Toronto (ca-tor), Washington DC (us-east).
| Dependencies | Dependency impacts | Customer provided | Control or data plane | Location of dependency |
|---|---|---|---|---|
| IBM Cloud Block Storage | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.BluVirtServers}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.cis_full}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| {{site.data.keyword.cis_full}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| {{site.data.keyword.BluVirtServers}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.iamlong}} | Access management, Availability, Change management, Instance control, Security compliance | No | Both | Global |
| {{site.data.keyword.iamlong}} | Access management, Availability, Change management, Instance control, Security compliance | No | Both | Global |
| {{site.data.keyword.cloudantfull}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same region |
| {{site.data.keyword.vpc_full}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same region |
| {{site.data.keyword.vpc_full}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same region |
| {{site.data.keyword.BluVirtServers}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.BluVirtServers}} | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.cos_full}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| Akamai | Availability, Change management, Disaster recovery, Instance control | No | Both | Global |
| {{site.data.keyword.cos_full}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| {{site.data.keyword.cos_full}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| IBM Cloud Classic DNS Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic DNS Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic DNS Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic DNS Servers | Availability, Change management, Instance control | No | Both | Same data center |
| {: row-headers} | ||||
| {: caption="IBM Cloud Continuous Delivery - Data and Control plane deployment service dependency information - Critical dependencies" caption-side="top"} | ||||
| {: tab-title="Critical dependencies"} | ||||
| {: tab-group="service-dependency-data-for-continuous-delivery-Data-and-Control-plane-deployment"} | ||||
| {: class="comparison-tab-table"} | ||||
| {: #critical-deps-data-and-control-plane-deployment} | ||||
| {: summary="Use the buttons for the dependency level to change the context of the table. This table has row and column headers. The row headers detail the specific dependent service. The column headers identify the details about the dependency and its impact. To understand the details about each dependency, navigate to the row to find the dependency that you need more information about interested in."} |
| Dependencies | Dependency impacts | Customer provided | Control or data plane | Location of dependency |
|---|---|---|---|---|
| IBM Cloud Bare Metal | Availability, Change management, Disaster recovery, Instance control | No | Both | Same data center |
| {{site.data.keyword.atracker_full}} | Availability, Operations, Security compliance | No | Both | Same region |
| IBM Cloud Business Support Services | Availability, Instance control | No | Both | Global |
| IBM Cloud Global Resource Catalog | Availability, Change management, Instance control | No | Both | Global |
| IBM Cloud Classic NTP Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic NTP Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic NTP Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Classic NTP Servers | Availability, Change management, Instance control | No | Both | Same data center |
| IBM Cloud Service Endpoints | Availability, Change management, Disaster recovery, Instance control | No | Both | Same region |
| IBM Cloud Service Endpoints | Availability, Change management, Disaster recovery, Instance control | No | Both | Same region |
| {{site.data.keyword.registrylong}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| IBM Cloud Business System Services User and Account management | Access management, Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| {{site.data.keyword.keymanagementservicefull}} | Availability, Change management, Disaster recovery, Instance control, Security compliance | No | Both | Same region |
| IBM Cloud Console | Availability, Instance control, Operations | No | Both | Global |
| {: row-headers} | ||||
| {: caption="IBM Cloud Continuous Delivery - Data and Control plane deployment service dependency information - Significant dependencies" caption-side="top"} | ||||
| {: tab-title="Significant dependencies"} | ||||
| {: tab-group="service-dependency-data-for-continuous-delivery-Data-and-Control-plane-deployment"} | ||||
| {: class="comparison-tab-table"} | ||||
| {: #significant-deps-data-and-control-plane-deployment} | ||||
| {: summary="Use the buttons for the dependency level to change the context of the table. This table has row and column headers. The row headers detail the specific dependent service. The column headers identify the details about the dependency and its impact. To understand the details about each dependency, navigate to the row to find the dependency that you need more information about interested in."} |
| Dependencies | Dependency impacts | Customer provided | Control or data plane | Location of dependency |
|---|---|---|---|---|
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| IBM GitHub Enterprise | Change management | No | Both | Same region |
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| {{site.data.keyword.pag_full}} | Change management, Operations | No | Both | Same region |
| {: row-headers} | ||||
| {: caption="IBM Cloud Continuous Delivery - Data and Control plane deployment service dependency information - Medium dependencies" caption-side="top"} | ||||
| {: tab-title="Medium dependencies"} | ||||
| {: tab-group="service-dependency-data-for-continuous-delivery-Data-and-Control-plane-deployment"} | ||||
| {: class="comparison-tab-table"} | ||||
| {: #medium-deps-data-and-control-plane-deployment} | ||||
| {: summary="Use the buttons for the dependency level to change the context of the table. This table has row and column headers. The row headers detail the specific dependent service. The column headers identify the details about the dependency and its impact. To understand the details about each dependency, navigate to the row to find the dependency that you need more information about interested in."} |
| Dependencies | Dependency impacts | Customer provided | Control or data plane | Location of dependency |
|---|---|---|---|---|
| GitHub | none | Yes | Both | Global |
| IBM Log Analysis Log Routing | Access management, Operations, Security compliance | No | Both | Same region |
| IBM Cloud CLI | Operations | No | Both | Global |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| Slack | Operations | Yes | Both | Global |
| external-atalassian-bitbucket | none | Yes | Both | Global |
| external-soucelab | none | Yes | Both | Global |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| {{site.data.keyword.monitoringlong}} | Operations | No | Both | Same region |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| SonarQube | none | Yes | Both | Global |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| Segment | Operations | No | Both | Global |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| IBM Cloud Projects | none | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| IBM Cloud Security and Compliance Center | Security compliance | No | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| Amplitude | Operations | No | Both | Global |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| {{site.data.keyword.metrics_router_full}} | Operations | No | Both | Same region |
| {{site.data.keyword.logs_full}} | Access management, Operations, Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS SIEM | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| None | Security compliance | No | Both | Same region |
| OSS Platform | Operations | No | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| SOS Tenable | Security compliance | No | Both | Same region |
| {{site.data.keyword.SendGrid}} | none | No | Both | Global |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| {{site.data.keyword.appconfig_full}} | Customer responsibility | Yes | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Inventory Management | Security compliance | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| Synthetics | Operations | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Privileged Identity Management | Access management, Operations, Security compliance | No | Both | Same region |
| SOS Health-Check, Vulnerability Scanning and Patching | Security compliance | No | Both | Same region |
| PagerDuty | none | Yes | Both | Global |
| SOS Compliance Reporting | Security compliance | No | Both | Same region |
| {: row-headers} | ||||
| {: caption="IBM Cloud Continuous Delivery - Data and Control plane deployment service dependency information - Minimal dependencies" caption-side="top"} | ||||
| {: tab-title="Minimal dependencies"} | ||||
| {: tab-group="service-dependency-data-for-continuous-delivery-Data-and-Control-plane-deployment"} | ||||
| {: class="comparison-tab-table"} | ||||
| {: #minimal-deps-data-and-control-plane-deployment} | ||||
| {: summary="Use the buttons for the dependency level to change the context of the table. This table has row and column headers. The row headers detail the specific dependent service. The column headers identify the details about the dependency and its impact. To understand the details about each dependency, navigate to the row to find the dependency that you need more information about interested in."} |
{: #understand-dependency-data}
If you have any questions about the service dependency data as you review the service dependency information in the tables, you can refer to the following FAQ:
{: #expected-impact}
Each severity tab in the table indicates the impact that your provisioned service might encounter if the dependency were to go offline. This means that the dependency high availability and disaster recovery influences the severity of the impact and therefore is used for general guidance to help you understand potential issues that might arise if the dependency was impacted by an incident.
Services that are regional are not impacted by a severe outage of a single zone because of the failover that is built in to default to another zone. For these occurrences, there might be a slight performance impact, if any, while the system fails over to the other location. This also applies to global services where the impact is lowered even more as it can fail over to other regions if necessary. This reduces the frequency at which these items might have the impact that is shown. {: note}
{: #dependent-services}
The Dependencies column lists the services. These are the major service to service dependencies including major internal dependencies that might not be visible externally.
{: #function-impact}
Functions include access management, availability, change management, configuration management, customer responsibility, disaster recovery, instance control, operations, security compliance, or none. If the dependency goes offline, these functions might be impacted. Definitions for each available value are as follows:
Access management : Authentication, authorization, and governance of the customer users access to the service and service instances.
Availability : Availability of the service and service instances.
Change management : Deployment, upgrade, patch, and so on, of the service and service instances.
Configuration management : Deployment, upgrade, patch, and so on, of the service and service instances.
Customer responsibility : Functions provided by customers to support specific service and service instances function. For example, {{site.data.keyword.keymanagementservicefull_notm}} instances provided by customer to support service BYOK encryption.
Disaster recovery : Backup, recovery, restart of the service and service instances in the case of a disruption.
Instance control : Creation, deletion, start, stop actions on the lifecycle of the service instances.
Operations : Monitoring, troubleshooting, and so on, of the service and service instances.
Security compliance : Vulnerability management and other security and compliance management of the service and service instances.
None : No function impacted.
{: #customer-provided-dep}
The Customer provided column reports if there is any dependency that has been provided by the customer to enable specific functionality. One such example is to properly configure and set up using BYOK into a service, the customer would provision a service like {{site.data.keyword.keymanagementservicefull_notm}}. For more information about how to enable the features and which services you need to provision, see the documentation for the service.
{: #deploy-dependencies}
In the Location of dependency column, you can view if the dependency is located in the same region or deployed to a specific data center. You can use this data with the data in the Control or data plane column for a quick reference to identify if your data leaves the region or not in a standard setup.
To find where your service can be deployed, see Service and infrastructure availability by location.
The table shows a standard cloud deployment. If a special deployment is used like FedRAMP or other region-bound deployment models, the data might differ from the details available in the table. Refer to the specific deployment that you are using for that information. {: note}
{: #separate-plans}
Sometimes, the dependency might have a separate control plane and data plane. In these cases, there are separate lines that show the location in relation to the deployed customer instance of the service where these will be provisioned. The lines might have different impacts and different functions. See the Control or data plane column to understand what possible impact this type of outage might have.
Same region means that the dependent services are in the same region as the provisioned instance. Other values might show data center or region names if the service must be used from a specific region, a specific zone, or set of zones. If a service is tied to a specific region or site, and the region goes offline, the service might go offline as well. It is recommended that you go through the high availability and disaster recovery documentation of the dependency to determine if there are any steps that you should take to mitigate these types of risks.
{: #additional-resources}
For more information about the policies that are related to the services, you can refer to the following resources: