Which solution will meet these requirements?
Download the Lambda function deployment package from the Source account. Use the deployment package and create new Lambda functions in the Target account. Share the automated Aurora DB cluster snapshot with the Target account.
Download the Lambda function deployment package from the Source account. Use the deployment package and create new Lambda functions in the Target account. Share the Aurora DB cluster with the Target account by using AWS Resource Access Manager {AWS RAM). Grant the Target account permission to clone the Aurora DB cluster.
Use AWS Resource Access Manager (AWS RAM) to share the Lambda functions and the Aurora DB cluster with the Target account. Grant the Target account permission to clone the Aurora DB cluster.
Use AWS Resource Access Manager (AWS RAM) to share the Lambda functions with the Target account. Share the automated Aurora DB cluster snapshot with the Target account.
Explanations:
While this option allows for creating new Lambda functions in the Target account and sharing the Aurora DB cluster snapshot, it does not address sharing the actual DB instance for minimal downtime. The application may experience some downtime during the transition.
This solution allows for creating new Lambda functions using the deployment package in the Target account and enables sharing the Aurora DB cluster via AWS RAM. Cloning the DB cluster ensures that minimal downtime is achieved since the Target account can create its own instance based on the shared cluster.
AWS RAM does not support sharing Lambda functions directly; this option is not viable. While sharing the Aurora DB cluster is correctly described, the inability to share Lambda functions directly means that this option cannot fulfill the requirement for minimal downtime.
This option allows sharing the Lambda functions and Aurora snapshot, but it doesn’t provide a means to minimize downtime effectively. The Lambda functions would need to be recreated in the Target account, and the snapshot sharing doesn’t allow for immediate access to a live database instance during migration.
I assess that the answer is:
Download the Lambda function deployment package from the Source account. Use the deployment package and create new Lambda functions in the Target account. Share the Aurora DB cluster with the Target account by using AWS Resource Access Manager {AWS RAM). Grant the Target account permission to clone the Aurora DB cluster.