How is disaster recovery handled for Develop with AWS?

Utoolity’s disaster recovery approach aligns with the Shared Responsibility Model for Resiliency - Disaster Recovery of Workloads on AWS: Recovery in the Cloud. Resiliency is a shared responsibility between AWS and us, as a service provider integrating Atlassian products with AWS, and you, the customer, using our integrations to support your workloads running on AWS. It is important that you understand how disaster recovery and availability, as part of resiliency, operate under this shared model, so please take the time to get familiar with the referenced AWS documentation so that you can gauge how this works in context of Integrate with AWS.

Utoolity responsibility “Resiliency of the Cloud”

Develop with AWS primarily uses an event-driven architecture to provide its capabilities, i.e. it ingest AWS service events into Atlassian products after mapping and transforming the AWS event schemas into applicable Atlassian object schemas. It does not store any data other than the required configuration for this ingestion. The configuration data is stored in a DynamoDB table with Point-in-time recovery (PITR). The infrastructure is managed via the AWS Cloud Development Kit (CDK).

This architecture allows us to provision a replica environment of the entire infrastructure based on the most recent backup data at any point. We regularly review our recovery time objective (RTO) and recovery point objective (RPO) and perform a resp. disaster recovery test to ensure we meet our objectives. Find below our current resiliency policies:

Type	RTO	RPO	Notes

Type	RTO	RPO	Notes
Application	12h	1h	While we strive to match our infrastructure RTO/RPO during office hours, our support team is not yet available 24/7, hence the lower RTO from a customer perspective.
Infrastructure	4h	1h
Availability Zone	4h	1h	The app’s serverless infrastructure provides automatic cross-zone resiliency.
Region	–	–	The app does not yet support automatic cross-region DR, pending data residency support of the Forge platform: Data Residency for Marketplace Apps Status Update

Customer responsibility “Resiliency in the Cloud”

Your responsibility will be determined by the AWS environments that you connect. You need to ensure that the required resources for the connection remain operational. Specifically this means that the resources provisioned via the CloudFormation stack in each environment (notably an IAM role and an EventBridge rule) are neither modified nor deleted as long as you wish to use that environment.