Default Link endpoints for IBM Cloud access to your Satellite location
Find information about default Link endpoints for IBM Cloud access to your IBM Cloud Satellite® location.
Default link endpoints for CoreOS enabled locations
Default endpoints are created for your location's control plane cluster and for any other Satellite-enabled services that you run in your location. These endpoints are accessible only from within the IBM Cloud private network.
The following table describes the Link endpoints that are automatically created in your Red Hat CoreOS enabled location.
| Name | Description | Type | Instances |
|---|---|---|---|
local-appLd-<location-ID> |
Allows your location to communicate with LaunchDarkly. | Cloud | One per location |
local-containerapi-<location-ID> |
Allows your location to communicate with the IBM Cloud containers API. | Cloud | One per location |
local-cosRegional-<location-ID> |
Allows the control plane data of your location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
local-cosUS-<location-ID> |
Allows your location to communicate with IBM Cloud® Object Storage. | Cloud | One per location |
local-csLd-<location-ID> |
Allows your location to communicate with LaunchDarkly. | Cloud | One per location |
local-iam-<location-ID> |
Allows requests to your location in IBM Cloud to be authenticated and user actions to be authorized by Identity and Access Management (IAM). | Cloud | One per location |
local-icr-<location-ID> |
Allows the control plane data of your location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
local-icrau-<location-ID> |
Allows your location to communicate with Container Registry. | Cloud | One per location |
local-icrus-<location-ID> |
Allows your location to communicate with Container Registry. | Cloud | One per location |
local-ignition-<location-ID> |
Allows your location to communicate with the ignition service. | Cloud | One per location |
local-konnectivity-<location-ID> |
Allows your location to communicate with the Konnectivity service | Cloud | One per location |
local-master-<location-ID> |
Allows your location to communicate with the management plane. | Cloud | One per location |
local-oauth-<location-ID> |
Allows your location to communicate with the oAuth service. | Cloud | One per location |
satellite-containersApi |
Allows your location to communicate with the IBM Cloud containers API. | Cloud | One per location |
satellite-cosCrossRegion-<location_ID> |
Allows the control plane data of your location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-cosRegional-<location_ID> |
Allows the control plane data of your location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-cosResConf-<location_ID> |
Allows the control plane data of your location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-healthcheck-<location_ID> |
Allows the Satellite management plane to check the health of your location's control plane cluster. | Location | One per location |
satellite-iam-<location_ID> |
Allows requests to your location in IBM Cloud to be authenticated and user actions to be authorized by Identity and Access Management (IAM). | Cloud | One per location |
satellite-kpRegional-<location_ID> |
Allows apps and services in the location to communicate with the IBM Key Protect service API | Cloud | One per location |
satellite-logdna-<location_ID> |
Allows logs for your location to be sent to your IBM® Log Analysis instance. | Cloud | One per location |
satellite-logdnaapi-<location_ID> |
Allows your location to communicate with the IBM® Log Analysis API. | Cloud | One per location |
satellite-sysdig-<location_ID> |
Allows metrics for your location to be sent to your IBM Cloud® Monitoring instance. | Cloud | One per location |
satellite-sysdigapi-<location_ID> |
Allows your location to communicate with the IBM Cloud Monitoring API. | Cloud | One per location |
satellite-sysdigPrometheus-<location-ID> |
Allows your location to communicate with the IBM Cloud Monitoring API. | Cloud | One per location |
openshift-api-<cluster_ID> |
Allows the Red Hat OpenShift on IBM Cloud API to communicate with the master for the service cluster. By default, your Red Hat OpenShift on IBM Cloud API Satellite link endpoints are protected to accept traffic from only the IBM Cloud control plane. To access them, you must create a source list for your endpoint to be accessible from other sources. | Location | One per Satellite-enabled IBM Cloud service in your location |
These endpoints are used to manage and update your location and are enabled by default. If you disable any of these endpoints, your client services that are running on your location can be negatively impacted. To avoid issues, do not disable these endpoints.
Default link endpoints for locations without CoreOS enabled
Default Satellite Link endpoints are created for your location's control plane cluster and for any other Satellite-enabled services that you run in your location. These default Satellite Link endpoints are accessible only from within the IBM Cloud private network.
The following table describes the Link endpoints that are automatically created in your Satellite location.
| Name | Description | Type | Instances |
|---|---|---|---|
satellite-healthcheck-<location_ID> |
Allows the Satellite management plane to check the health of your location's control plane cluster. | Location | One per location |
satellite-containersApi |
Allows your Satellite location to communicate with the IBM Cloud containers API. | Cloud | One per location |
satellite-cosCrossRegion-<location_ID> |
Allows the control plane data of your Satellite location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-cosRegional-<location_ID> |
Allows the control plane data of your Satellite location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-cosResConf-<location_ID> |
Allows the control plane data of your Satellite location to be backed up to your IBM Cloud® Object Storage instance. management plane data is backed up by IBM and stored in an IBM-owned Object Storage instance. Satellite cluster master data is backed up to the Object Storage instance that you own. | Cloud | One per location |
satellite-iam-<location_ID> |
Allows requests to your Satellite location in IBM Cloud to be authenticated and user actions to be authorized by Identity and Access Management (IAM). | Cloud | One per Satellite location |
satellite-kpRegional-<location_ID> |
Allows apps and services in the location to communicate with the IBM Key Protect service API | Cloud | One per location |
satellite-logdna-<location_ID> |
Allows logs for your Satellite location to be sent to your IBM® Log Analysis instance. | Cloud | One per location |
satellite-logdnaapi-<location_ID> |
Allows your Satellite location to communicate with the IBM® Log Analysis API. | Cloud | One per Satellite location |
satellite-sysdig-<location_ID> |
Allows metrics for your Satellite location to be sent to your IBM Cloud® Monitoring instance. | Cloud | One per location |
satellite-sysdigapi-<location_ID> |
Allows your Satellite location to communicate with the IBM Cloud Monitoring API. | Cloud | One per Satellite location |
openshift-api-<cluster_ID> |
Allows the Red Hat OpenShift on IBM Cloud API to communicate with the master for the service cluster. By default, your Red Hat OpenShift on IBM Cloud API Satellite link endpoints are protected to accept traffic from only the IBM Cloud control plane. To access them, you must create a source list for your endpoint to be accessible from other sources. | Location | One per Satellite-enabled IBM Cloud service in your location |
These endpoints are used to manage and update your location and are enabled by default. If you disable any of these endpoints, your client services that are running on your Satellite location can be negatively impacted. To avoid issues, do not disable these endpoints.