DR Deployment Approach

Data Replication

The primary goal of the Amorphic DR deployment approach is to ensure that some import data and services from the primary region are replicated to a secondary region in real-time, allowing the secondary region to stay synchronized with the primary region. This process involves the real-time replication of specific resources.

Automated Processes

Amorphic employs various replication strategies for its different services, with some services undergoing real-time replication as outlined below detailed description

• Amorphic Application Service: Changes made to metadata in the primary region are automatically and instantly replicated to the secondary region. Users don't need to manually trigger this replication; it happens seamlessly and in the background.

• Amorphic Data Storage: Certain Amorphic data storages are configured for real-time replication, while others will undergo replication when the disaster recovery application is launched.

• Amorphic Parameter Store(Secrets):Amorphic Parameter Store is managed through an automated process. Any changes made by the user to Amorphic Parameter Store in the primary region will be replicated to the secondary.

DR Deployment

The Amorphic backup mechanism employs continuous synchronization. Critical resources, such as DynamoDB tables, S3 buckets, and SSM parameters, are continuously synchronized in real-time. This means that the secondary region remains up-to-date with changes made in the primary region without any user intervention.

In the event of a disaster or the need to deploy the DR application, users can approach Amorphic support team to get there DR application deployed. The support team will initiate an automate process to deploy the DR application in the secondary region.

The combination of real-time data replication, automated processes, and on-demand resource deployment ensures that the Amorphic DR deployment approach is efficient, reliable, and user-friendly.