Understanding your responsibilities when using IBM Analytics Engine serverless instances

Learn about the management responsibilities and terms and conditions that you have when you use IBM Analytics Engine serverless instances. 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 the specific responsibilities for you and for IBM when you use IBM Analytics Engine serverless instances. For the overall terms of use, see IBM Cloud® Terms and Notices.

Incident and operations management

Incident and operations management includes tasks such as monitoring, event management, high availability, problem determination, recovery, and full state backup and recovery.

Responsibilities for incident and operations
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.
Task	IBM responsibilities	Your responsibilities
IBM Analytics Engine instance administration	Provide infrastructure operating system (OS), version, and security updates. Clean up all instance resources. Track hardware issues on running cluster.	Create an instance using the provided API, CLI or console tools. Delete a service instance using the provided API, CLI or console tools. Customize a service instance using the provided API or CLI. View or change the instance configuration using the provided API, CLI or console tools.
Application administration	Monitor Spark application for any failures due to infrastructure provided by IBM.	Run Spark applications on the cluster using the provided CLI or API. Tune the Spark instance for your application requirements using the provided CLI or API.
Observability	Provide Log Analysis to enable observability of your IBM Analytics Engine service logs. Provide integration with Activity Tracker to send IBM Analytics Engine events for auditability.	Set up Activity Tracker and send events to monitor the health of your IBM Analytics Engine instances. Set up and send logs to Log Analysis.

Change management

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.

Responsibilities for change management
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.
Task	IBM Responsibilities	Your Responsibilities
Instance provisioning	Order hardware (data plane in the IBM services account). Open the Spark cluster to the internet (data plane in the IBM Services account). Ensure network isolation of the Spark cluster nodes from other clusters (data plane in the IBM Services account). Patch the cluster hosts (data plane in the IBM Services account). Ensure safe erasure of data from removed node or deleted cluster nodes. Delete hardware (data plane in the IBM Services account)	No change management responsibilities

Identity and access management

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.

Responsibilities for identity and access management
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.
Task	IBM Responsibilities	Your Responsibilities
Access control of the service instance through IAM	Verify the user's permissions on the service instance before allowing access.	Maintain responsibility for any service roles that you create for your instances.

Security and regulation compliance

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.

Responsibilities for security and regulation compliance
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.
Task	IBM Responsibilities	Your Responsibilities
General	Maintain controls commensurate to various industry compliance standards. Monitor, isolate, and recover instances. Monitor and report the health of instances in the various interfaces. Secure cluster access through TLS (data plane in the IBM Services account). Integrate IBM Analytics Engine with IBM Cloud Identity and Access Management (IAM).	Set up and maintain security and regulation compliance for the IBM Analytics Engine instances.

High availability and Disaster recovery

High availability (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure.

Disaster recovery includes tasks such as providing dependencies on disaster recovery sites, provision disaster recovery environments, data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events.

Responsibilities for disaster recovery
The rows are read from left to right. The first column describes the task that a the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.
Task	IBM Responsibilities	Your Responsibilities
High availability	IBM ensures that the control plane is deployed on multi zone regions. When a zone becomes unavailable in a multi zone region, the workloads are automatically scheduled on the remaining available zones. Maintain service replicas to ensure service availability on Pod failure.	No action required
General	Restore or rebuild the provisioning environments in the affected regions. Rebuild the existing Spark instance, where possible.	Track instance state and application state. Provision a new service instance and re-submit the application in an alternatively available region if the current instances can't be accessed. Create backup for all Spark instance configuration data and validate the information. Make sure that all data, metadata and applications reside outside of the cluster. This activity must be completed before disaster recovery can be initiated.

Locations

Frankfurt
Dallas