Business Continuity or Disaster Recovery Guidelines

Version 2023-d

Overview: Kitepipe Managed Cloud Solution Services (MCSS) offers Boomi Hosting of the runtime in a dedicated virtual environment hosted within the Amazon Web Services (AWS) cloud. Business Continuity and Disaster Recovery are connected but have slightly different goals. This framework document focusses on Business Continuity, or the goal of keeping business operational during an outage.

The Boomi JVM runtime operating in AWS, is accessed and configured via the Boomi iPaaS or AtomSphere platform, which provides a browser-based application allowing users to design, build and deploy Boomi integrations. The Boomi AtomSphere SLA and related availability services are managed by Boomi and detailed in Boomi specific documents and agreements.

High Availability and Business Continuity: Kitepipe MCSS utilizes Amazon Web Services (AWS) to provide highly available infrastructure to support the Client’s Boomi services. The Kitepipe SLA specifies a Service Availability of 99.99% for all Boomi hosted configurations, which matches the Boomi AtomSphere SLA, referenced in the Boomi MSA documents.

All Kitepipe MCSS services for the Client reside in one AWS Region, with Molecule services operating across two AWS Availability Zones (AZ) distributing those Molecule operations in two physical data centers improving resilience to localized failures.

AWS data centers are physical locations with UPS (Uninterruptable Power Supply), backup power generators and dedicated cooling equipment. The physical separated Availability Zones are organized to be at least 60 miles apart inside a region and are isolated from other AZ data centers, to mitigate localized weather and other force majeure events. AWS datacenters use a four layer data security framework: Perimeter, Infrastructure, Data and Environment. Additional detail is available on the AWS web site.

Boomi Configurations: The impact of an event that may disrupt Business Continuity of MCSS services depends on which Boomi configuration is deployed; a Boomi Atom or a Boomi Molecule. See below for details of each.

1. Boomi Molecule (i.e., clustered Boomi runtime) A Boomi Molecule is a cluster of Boomi runtimes providing the high availability you expect from a cluster. As already stated, MCSS deploys all Molecules across at least two AZs mitigating common Business Continuity disruptions such as a failed Boomi node or server, events requiring server restarts, or more serious events such as an AZ failure. These risks are all mitigated by a Molecule since processes would continue to execute within any remaining nodes of the Molecule as long as the AWS Region and at least one of the AZ’s in which its resides is operational. Shared network storage is utilized with the AWS EFS service to mitigate data loss. Once the event has passed, the failed Molecule nodes will come back online bringing the capacity back to normal.
2. Boomi Atom (i.e., single Boomi runtime, not clustered) A Boomi Atom is a single Boomi runtime supported by highly available AWS data center. Kitepipe and Boomi recommend Atoms for non-critical applications as the one Atom node is technically a single point of failure. Atom or AZ failure is rare, and in short outages, Boomi processing can normally resume without special efforts once the Atom is operating again and connectivity is restored. If the Client requires resumption of services during an AZ failure or Boomi must always be up and running for business reasons, then the Client should consider utilizing a Molecule, which by design mitigates these issues.

Data Backup: MCSS will perform system backups every 24 hours for the purposes of meeting the service agreements as stated in the Kitepipe MCSS SLA. It should be noted that system backups are for Kitepipe MCSS use only and are not made available to the Client.

Additional Items to Know:

• The Client may select the Region that their Boomi services will execute within.
• MCSS does not offer cold stand-bys in alternative regions or AZ’s that are pre-configured.
• Business Continuity rehersals. are not included in Kitepipe baseline MCSS offers
• Business Continuity rehersals may be separately requested by the Client for the Molecule runtime configurations, which will be estimated by Kitepipe as an add-on service, once the MCSS Molecule environment is onboarded and workloads are deployed.
• Note: Business Continuity rehearsals or compliance initiatives are based on specific requirements generated by the Client, which may be supported by Kitepipe as a separate project. Project scope and estimated hours would include both AWS infrastructure costs and Kitepipe team hours as required.
• Business Continuity rehersals are not provided for an Atom configuration.

Business Continuity Summary

The Kitepipe SLA for Service Availability for the AWS Managed Cloud Solution Services (MCSS) is 99.99% for all Boomi configurations (Atom or Molecule), excluding the exceptions detailed in the Kitepipe MCSS SLA.

An Atom may be confidently deployed in AWS for Boomi integrations, as many Atom use cases are batch-oriented workflows, or listener based, which can be rescheduled and/or re-run after the Atom is restored, in case of a failure. If there was a sustained failure in an AZ, Kitepipe and the Client can determine the best path to restore the Atom, potentially in another AZ. The load balanced Molecule is by design a high availability configuration and will meet most Clients requirements for Business Continuity without special intervention or planning.

Clients who have concerns or specific compliance requirements for Business Continuity, or potential future state high availability requirements for integrations and workloads are encouraged to work with their Boomi team to specify that Molecule licenses are included in their managed services solution.