Lambda Workflow Steps:
AWS Proxy Trigger: The AWS proxy triggers the DR Restore Lambda function within the customer’s AWS account.
Data Retrieval from Druva Cloud: The Lambda function fetches the necessary data from the S3 bucket within Druva’s cloud storage.
Data Processing: The function then breaks down the retrieved data into fixed-size blocks for optimal processing.
EBS Snapshot Creation: The Lambda function writes an EBS snapshot in the customer’s AWS account using EBS direct APIs (PutSnapshotBlock).
Key Points:
Cloud Connections: The Lambda function connects to Druva cloud services only in steps 1 and 2, while step 4 (EBS snapshot creation) does not require a connection to Druva’s services.
IP Allocation and Control: The IPs involved in EBS services are dynamically allocated within the customer's AWS environment during execution, and Druva does not control or manage these IPs, so no fixed IP list can be provided.
Recommendations:
EBS Endpoint with Private DNS: Creating an EBS endpoint with private DNS is recommended to avoid exposing public IPs. Druva’s CloudFormation (CF) template includes a configuration to set up this EBS endpoint with private DNS.
Public IPs Option: For customers who prefer using public IPs, it is possible to obtain the IPs of the EBS service with which the DR Restore Lambda function may connect.
For further guidance, check Druva documentation on DRaaS