en-responsibilities.md

copyright	lastupdated	keywords	subcollection
years 2021, 2024	2024-10-07	event-notifications, event notifications, customer responsibilities, IBM responsibilities, terms and conditions, disaster recovery, toolchain backup	event-notifications

{{site.data.keyword.attribute-definition-list}}

Your responsibilities with {{site.data.keyword.en_full_notm}}

{: #en-responsibilities} {: help} {: support}

Learn about the management responsibilities and applicable terms and conditions when you use {{site.data.keyword.en_full_notm}}. For a high-level view of the service types in {{site.data.keyword.cloud_notm}} and the breakdown of responsibilities between the customer and {{site.data.keyword.IBM_notm}} for each type, see Shared responsibilities for {{site.data.keyword.cloud_notm}} offerings. {: shortdesc}

Review the following sections for demarcation of responsibilities between you and {{site.data.keyword.IBM_notm}} when you use {{site.data.keyword.cloud_notm}} {{site.data.keyword.en_short}}. For the overall terms of use, see {{site.data.keyword.cloud}} Terms and Notices.

Incident and operations management

{: #en-incident-and-ops}

You and {{site.data.keyword.IBM_notm}} share responsibilities for the setup and maintenance of your {{site.data.keyword.en_full_notm}} instance.

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

Task	{{site.data.keyword.IBM_notm}} 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 {{site.data.keyword.cloud_notm}} status page for general announcements.
{: caption="Responsibilities for incident and operations" caption-side="top"}

Change management

{: #en-change-management}

You and {{site.data.keyword.IBM_notm}} share responsibilities for keeping {{site.data.keyword.en_full_notm}} service components at the latest version.

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

Task	{{site.data.keyword.IBM_notm}} 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).
{: caption="Responsibilities for change management" caption-side="top"}

Identity and access management

{: #en-identity-and-access-management}

You and {{site.data.keyword.IBM_notm}} share responsibilities for controlling access to your {{site.data.keyword.en_full_notm}} instances and resources.

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

Task	{{site.data.keyword.IBM_notm}} 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.
{: caption="Responsibilities for identity and access management" caption-side="top"}

Security and regulation compliance

{: #en-sec-and-reg-compliance}

{{site.data.keyword.IBM_notm}} is responsible for the security and compliance of {{site.data.keyword.en_full_notm}}.

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

Task	{{site.data.keyword.IBM_notm}} Responsibilities	Your Responsibilities
Encryption	* Automatically apply security fix updates for infrastructure. \n * Enable security settings, such as encrypted disks. \n * Disable insecure actions, such as user SSH access to the host. \n * Encrypt communication with TLS. \n * Continuously monitor {{site.data.keyword.en_full_notm}} entities to detect vulnerability and security compliance issues. \n * Integrate {{site.data.keyword.en_full_notm}} with {{site.data.keyword.IBM_notm}} {{site.data.keyword.iamshort}} (IAM).	Manage {{site.data.keyword.cloud_notm}} credentials, and keep credentials secure.
{: caption="Responsibilities for security and regulation compliance" caption-side="top"}

Disaster recovery

{: #en-disaster-recovery}

{{site.data.keyword.IBM_notm}} is responsible for the recovery of {{site.data.keyword.en_full_notm}} components if there is a disaster.

You are responsible for the recovery of the workloads that run {{site.data.keyword.en_full_notm}} and your application and application data.

Task	{{site.data.keyword.IBM_notm}} Responsibilities	Your Responsibilities
Availability	* Provide high availability capabilities, such as {{site.data.keyword.IBM_notm}}-owned infrastructure in multizone regions, to meet local access, and low latency requirements for each supported region. \n * Run {{site.data.keyword.en_full_notm}} deployments with three replicas in the same region for high availability. \n Continuously monitor {{site.data.keyword.en_full_notm}} infrastructure to ensure the reliability and availability of the service environment by site reliability engineers. \n 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 {{site.data.keyword.IBM_notm}}. \n * Set up more {{site.data.keyword.en_full_notm}} instances across zones and regions to increase disaster recovery tolerance that exceeds the default that is provided by {{site.data.keyword.IBM_notm}}.
{: caption="Responsibilities for disaster recovery" caption-side="top"}

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:

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
{: caption="Example API endpoints" caption-side="top"}

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.