The architecture and data flow across components within Druva’s Infrastructure and the customer’s environment is illustrated below:
Customer infrastructure
CloudFormation Template: The CloudFormation template defines the AWS resources you want to create, update, or delete as part of a stack. The CloudFormation creates the required roles and grants permissions to your AWS account.
Installed EC2 Role: Grants the required access permissions to perform backup and restore operations on the customer’s EC2 resources.
Installed Orchestration Role: Grants Druva permissions to perform orchestration operations on the customer's AWS account.
Druva Infrastructure
Customer Key: AWS-managed customer encryption key to secure your data.
Deduplication Engine: The data proxy uses deduplication APIs to determine which data is to be transferred to the assigned Druva storage.
The costs for data transfer within Druva infrastructure are incurred by Druva.Customer IAM Role: The IAM access role that grants our data protection solution access to your AWS account using an IAM Access Role.
Customer installed block storage: Block storage to store data that enables application consistent data backup and low latency.