Understanding data portability for IBM Cloud Event Notifications
Data portability involves a set of tools and procedures that enable customers to export the digital artifacts that are needed to implement similar workload and data processing on different service providers or on-premises software. It includes procedures for copying and storing the service customer content, including the related configuration that is used by the service to store and process the data, on the customer's own location.
Responsibilities
IBM Cloud services provide interfaces and instructions to guide the customer to copy and store the service customer content, including the related configuration, on their own selected location.
The customer is responsible for the use of the exported data and configuration for data portability to other infrastructures, which includes:
- The planning and execution for setting up alternative infrastructure on different cloud providers or on-premises software that provide similar capabilities to the IBM services.
- The planning and execution for the porting of the required application code on the alternative infrastructure, including the adaptation of customer's application code, deployment automation.
- The conversion of the exported data and configuration to the format that is required by the alternative infrastructure and adapted applications.
For more information about your responsibilities for IBM Cloud® Event Notifications, see Shared responsibilities for IBM Cloud® Event Notifications.
Data export procedures
IBM Cloud Event Notifications provides the mechanisms to export your content that is uploaded, stored, and processed when you use the service.
For each data set that you need to export, use GET calls to get a copy of the data. And use the corresponding PUT / POST API to populate the new instance at the place where the data is copied.
| Entity | Endpoint | Description |
|---|---|---|
| sources | /v1/instances/{instance_id}/sources |
Your platform sources |
| topics | /v1/instances/{instance_id}/topics |
All registered topics |
| destinations | /v1/instances/{instance_id}/destinations |
All registered destinations |
| subscriptions | /v1/instances/{instance_id}/subscriptions |
All the subscriptions |
| metrics | /v1/instances/{instance_id}/metrics |
All the metrics |
| templates | /v1/instances/{instance_id}/templates |
All the templates |
| SMTP configurations | /v1/instances/{instance_id}/smtp/config |
All the smtp configurations |
| integrations | /v1/instances/{instance_id}/integrations |
All the integrations |
For more information about all available APIs for exporting data, see API documentation.
/metrics does not have have a POST/PUT api as they are the metrics of usage of the service.
Exported data formats
IBM Cloud Event Notifications resources export the data via Service APIs in JSON format. The schema of the exported data is described in the IBM Cloud Event Notifications service API documentation.
Data ownership
All exported data is classified as customer content and is therefore applied to them full customer ownership and licensing rights, as stated in IBM Cloud Service Agreement.