Understanding your responsibilities with IBM Cloud Event Notifications

Learn about the management responsibilities and applicable terms and conditions when you use IBM Cloud Event Notifications. For a high-level view of the service types in IBM Cloud and the breakdown of responsibilities between the customer and IBM for each type, see Shared responsibilities for IBM Cloud offerings.

Review the following sections for demarcation of responsibilities between you and IBM when you use IBM Cloud Event Notifications. For the overall terms of use, see IBM Cloud® Terms and Notices.

Incident and operations management

You and IBM share responsibilities for the setup and maintenance of your IBM Cloud Event Notifications instance.

You are responsible for incident and operations management of your application and application data.

Table 1. Responsibilities for incident and operations
Task	IBM Responsibilities	Your Responsibilities
Incidents	Provide notifications for planned maintenance, security bulletins, or unplanned outages.	Set preferences to receive emails about platform notifications, and monitor the IBM Cloud status page for general announcements.

Change management

You and IBM share responsibilities for keeping IBM Cloud Event Notifications service components at the latest version.

You are responsible for change management of your application and application data.

Table 2. Responsibilities for change management
Task	IBM Responsibilities	Your Responsibilities
Applications	Provide infrastructure operating system (OS), version, and security updates.	Use the API, SDK, CLI, or console tools to apply the provided updates for the local entities (app code, CLI, and SDK).

Identity and access management

You and IBM share responsibilities for controlling access to your IBM Cloud Event Notifications instances and resources.

You are responsible for identity and access management of your application and application data.

Table 3. Responsibilities for identity and access management
Task	IBM Responsibilities	Your Responsibilities
Applications	Offer ability to restrict access to resources.	Depending on your needs, restrict access to resources and service functions by using Cloud IAM access policies. For more information, see Managing user access.

Security and regulation compliance

IBM is responsible for the security and compliance of IBM Cloud Event Notifications.

You are responsible for the security and compliance of your application and application data.

Table 4. Responsibilities for security and regulation compliance
Task	IBM Responsibilities	Your Responsibilities
Encryption	Automatically apply security fix updates for infrastructure. Enable security settings, such as encrypted disks. Disable insecure actions, such as user SSH access to the host. Encrypt communication with TLS. Continuously monitor IBM Cloud Event Notifications entities to detect vulnerability and security compliance issues. Integrate IBM Cloud Event Notifications with IBM Cloud Identity and Access Management (IAM).	Manage IBM Cloud credentials, and keep credentials secure.

Disaster recovery

IBM is responsible for the recovery of IBM Cloud Event Notifications components if there is a disaster.

You are responsible for the recovery of the workloads that run IBM Cloud Event Notifications and your application and application data.

Table 5. Responsibilities for disaster recovery
Task	IBM Responsibilities	Your Responsibilities
Availability	Provide high availability capabilities, such as IBM-owned infrastructure in multizone regions, to meet local access, and low latency requirements for each supported region. Run IBM Cloud Event Notifications deployments with three replicas in the same region for high availability. Continuously monitor IBM Cloud Event Notifications infrastructure to ensure the reliability and availability of the service environment by site reliability engineers. Maintain service availability across worldwide regions so that customers can deploy projects across zones and regions for higher DR tolerance.	Use the list of available regions to plan for and create new instances of the service to meet performance and availability requirements exceeding the default that is provided by IBM. Set up more IBM Cloud Event Notifications instances across zones and regions to increase disaster recovery tolerance that exceeds the default that is provided by IBM.

If you need zero downtime during a regional disaster recovery, create and maintain backup instances in other regions. Review the API documentation and decide the data that you want backed up and restored if there is a disaster. To synchronize a service instance in one region with an instance in a different region, you can use the APIs mentioned here.

Some API examples are as follows:

Table 2. Example API endpoints
Entity	Endpoint	Description
sources	`/v1/instances/{instance_id}/sources`	Your platform sources
topics	`/v1/instances/{instance_id}/topics`	All registered topics
rules	`/v1/instances/{instance_id}/rules`	All rules created on topics
destinations	`/v1/instances/{instance_id}/destinations`	All registered destinations
subscriptions	`/v1/instances/{instance_id}/subscriptions`	All the subscriptions

For each data set that you need to back up and restore, use GET calls to get a copy of the data. And use the corresponding PUT / POST API to populate the new instance on a different region.