This article describes the various components deployed as part of the CloudFormation stack and their approximate costs per month.
Overview
The cost will depend on your usage of Druva Cloud DR and the AWS components used. It is recommended that you review the AWS pricing documentation and consult with Druva or AWS representatives for a more detailed cost analysis based on your component requirements.
Druva Cloud DR for VMware incurs the following types of AWS costs:
Fixed Costs: Fixed costs are for the AWS resources deployed as part of CloudFormation Deployment.
Variable Costs: Variable costs are for the AWS resources created and used as a part of DR operations like Update DR Copy, DR Failover, and DR Failback.
Fixed Costs
The Druva AWS proxy for Cloud DR deploys the following components as part of CloudFormation stack deployment:
Amazon EC2 instance:The Druva AWS proxy, also referred to as DR proxy, is an EC2 instance that runs in the customer’s AWS account. The Druva AWS proxy runs the Druva Disaster Recovery service and is responsible for orchestrating the DR Restore, DR failback, and DR failover.
VPC endpoints: A VPC endpoint enables private connections between the customer VPC and supported AWS services and VPC endpoint services using AWS PrivateLink.
Route-53Hosted zone: Druva uses Amazon Route 53 to perform DNS resolution between the Druva AWS proxy and the various AWS components in the customer VPC via the Amazon PrivateLink service. To route traffic to the various AWS components, you create records, also known as resource record sets, in your hosted zone.
Each of these components is billable, and the associated costs are to be paid to AWS.
❗ Important
The AWS component pricing can vary depending upon the options you select. AWS can also change the component pricing at any time. We advise you to check the AWS website for the most current component costs.
Refer to the following AWS pricing pages for the most current prices of the components.
The following example demonstrates how to calculate AWS component costs.
Druva AWS Proxy costs
The Druva AWS Proxy costs depends on how many Druva AWS proxies you choose to deploy, and the instance type per deployment. For more information about the costs depending on the instance type you select, see Amazon EC2 pricing.
For example, let's say you select one Amazon EC2 instance of type c5.xlarge.
AWS Service | Price | Quantity | Cost |
Instance-type | 0.17/hour for c5.xlarge | 24 hours for 30 days | 0.17 * 24 * 30 = 122.4 |
EBS Volume-type | 0.08-GB/month for GP3 (with default IOPS and Throughput) | 32 GB | 0.08 * 32 = 2.56 |
Cost for 1 AWS Proxy | 124.96 |
AWS PrivateLink VPC Endpoint pricing
The VPC endpoint price varies from AWS region to region. Druva deploys 6 VPC endpoints in all regions except us-east-1 where Druva deploys 10 VPC endpoints. Druva deploys the following VPC endpoints:
AWS S3 VPC Endpoint.
AWS SQS VPC Endpoint
AWS EC2 VPC Endpoint.
AWS CloudFormation VPC Endpoint.
Druva Service Endpoint
AWS Logs VPC Endpoint
AWS EBS Interface VPC Endpoint
AWS Lambda Interface VPC Endpoint
The example in the following screenshot uses the US East (Ohio) region (us-east-2) to compute VPC endpoint costs. It assumes that we deploy 9 VPC endpoints, 1 availability zone, and that the endpoints will process around 100 GB of data between the Druva AWS proxy and Druva Cloud DR services per month.
Cost of AWS VPC-Endpoints : $65.70 / Month for all the endpoints.
Use the AWS PrivateLink pricing calculator to compute costs as per your requirements.
Route-53 Hosted zone pricing
AWS Route-53 Component | Cost |
Cost per hosted zone / month | $0.50 |
Cost per million queries – first 1 Billion queries / month | $0.60 |
Cost per month for Route-53 hosted zone resources | $1.1 |
Variable Costs
DR Replication Costs
The Amazon EBS pricing depends on how many VMware VMs you configure for DR. For more information about the costs of various EBS Volume Types, see Amazon EBS pricing. When the VMs are configured, then the first DR Replication is FULL and the subsequent DR replication is Incremental. As part of the DR Replication job for DR configured VM, AWS Proxy creates Transient EBS Volumes and EBS recovery points.
For example, let's assume that 1 VM of size 100 GB is configured for DR. The DR Replication policy for this VM is Daily once and daily change-rate is 5%. Use the Amazon Pricing Calculator to calculate the EBS costs as per your requirements.
Druva uses AWS PrivateLink for data-transfer from S3 bucket to AWS Proxy.
Cost for 1 VM of size 100 GB for FULL Replication
AWS Service | Price | Quantity | Frequency | Cost |
Lambda cost | 0.0000167/GB-sec | 40 sec | 1/month | 0.0000167*40*100*8 = 0.5344 |
PutSnapshotBlock | 0.006 /1000 requests | 2 * 1024 * 100 requests | 1/month | (0.006*2*1024*100)/1000 = 1.2288 |
EBS recovery point for 24 hours till the Incremental Replication Starts | 0.05/GB-month | 100 | 1/month | (0.05 * 100)/(30) = 0.167 |
Data Transfer Inbound from Druva-S3 | 0.01/GB | 100 | 1/month | 0.01 * 100 = 1 |
Cost of FULL DR Replication for 1 VM of size 100 GB | 1/month | 2.93 |
Cost for 1 VM of size 100 GB for Incremental Replication
AWS Service | Price | Quantity | Frequency | Cost |
Lambda cost | 0.0000167/GB-sec | 40 sec | 30 days | 0.0000167*40*5*8*30=0.8016 |
PutSnapshotBlock | 0.006 / 1000 requests | 2 * 1024 * 5 requests | 30 days | (0.006*2*1024*5*30)/1000=1.8432 |
EBS recovery point (previous recovery point gets deleted and gets consolidated with new recovery point) | 0.05/GB-month | 100 GB | 30 days | (0.05 * 100) = 5 |
Data Transfer Inbound from Druva S3 via VPC-Endpoint | 0.01/GB | 5 | 30 days | 0.01 * 5 * 30 = 1.5 |
Cost of Incremental DR Replication for 1 VM of size 100 GB and 5% change rate | 9.14 |
Failover Costs
DR Failover costs per VM depends on the following settings:
Instance type selected for the VM in the Failover Settings
Total size of the VM disks
Type of EBS volume
SQS cost
S3 cost
Following is the cost of DR Failover job for bringing the VMware VM into AWS EC2 instance, assuming it takes 1 hour for the entire operation.
📝 Note
Failover cost does not include the cost incurred for the EC2 instance and associated EBS volumes after the DR Failover job is completed. If you use the Failover EC2 instance for additional hours, the total cost will increase.
AWS Service | Price | Quantity | Cost |
Instance-type | 0.17 per hour for c5.xlarge | 1 hour | 0.17 * 1 = $0.17 |
EBS Volume-type | 0.08-GB/month for GP3 (with default IOPS and Throughput) | 100 GB | (0.08 * 100) / (24 * 30) = 0.01 |
SQS | Standard SQS | less than 100 messages | Free |
S3 | Storage: 0.023 per GB per month
GET = 0.0004 per 1000 requests | Storage: 50 MB
Requests:
less than 10 GETs and PUTs | Free |
Cost of DR Failover job for 1 VM | 0.18 |
Failback Costs
DR Failback costs per VM depends on the following settings:
Instance type present for the Failover EC2 Instance
Total size of the EBS volumes attached to Failover EC2 Instance
Type of EBS volume
Following is the cost of DR Failback job for bringing the AWS EC2 Instance into VMware VM, assuming it takes 3 hours for the entire operation.
📝 Note
Failback cost does not include the cost incurred for the EC2 Instance and associated EBS volumes before the DR Failback is triggered or after the DR Failback job is completed. If you use the Failover EC2 instance for additional hours, the total cost will increase.
AWS Service | Price | Quantity | Cost |
Instance-type | 0.17 per hour for c5.xlarge | 3 hours | 0.17 * 3 = 0.51 |
EBS Volume-type | 0.08-GB/month for GP3 (with default IOPS and Throughput) | 100 GB | (0.08 * 100 * 3)/ (24 * 30) = 0.03 |
Data Transfer Outbound via Internet | 0.09 per GB | 100 GB | 0.09 * 100 = 9 |
Cost of DR Failback job for 1 VM | 9.54 |
📝 Notes
Druva has considered On-Demand pricing for AWS Compute. You can optionally use AWS offerings like AWS Compute Savings plan, etc.
If you select an EC2 Instance Savings Plan, pick a 3-year reservation with no upfront payments, and select 30 GB of EBS volume storage (General Purpose SSB(gp2), the total monthly cost comes up to $112.65. Use the Amazon EC2 pricing calculator to calculate the EC2 instance costs as per your requirements.
SQS cost : Data transferred between Amazon SQS and Amazon EC2 or Amazon SQS and AWS Lambda within a single region is free of charge (that is, $0.00 per GB). Data transferred between Amazon SQS and Amazon EC2 or Amazon SQS and AWS Lambda in different regions is charged at Internet Data Transfer rates on both sides of the transfer.
S3 Cost: Data transferred from an Amazon S3 bucket to any AWS service(s) within the same AWS Region as the S3 bucket (including to a different account in the same AWS Region).
The resources that are created by Druva during DR operations but not mentioned above like security groups, IAM Role, etc. are not chargeable by AWS. For more information, see AWS Identity and Access Management (IAM) FAQs andAmazon VPC FAQs.
As a part of CF Template Deployment, Druva launches one AWS Lambda and is approximately free.