Versions Compared

Old Version 1

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

compared with

New Version Current

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added RTO/RPO links and table.

...

Integrate 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 athe 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

Application

12h

1h

(lightbulb) 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

(tick) The app’s serverless infrastructure provides automatic cross-zone resiliency.

Region

–

–

(info) The app does not yet support automatic cross-region DR, pending data residency support of the Forge platform:

Customer responsibility “Resiliency in the Cloud”

...