Amazon Web Services SOA-C02 Dumps Questions Answers

To delete the AWS CloudFormation stack without deleting the DynamoDB table, you need to apply a deletion policy to the DynamoDB resource. The Retain deletion policy ensures that the specified resource is not deleted when the stack is deleted. Instead, it is retained.

Steps:

Modify the CloudFormation Template:

Add a deletion policy to the DynamoDB table resource.

json

Copy code

{

"Resources": {

"MyDynamoDBTable": {

"Type": "AWS::DynamoDB::Table",

"DeletionPolicy": "Retain",

}

}

}

When attempting to deploy a CloudFormation template from one region (us-west-2) to another (eu-west-1), the deployment might fail due to region-specific resources and services.

Amazon Machine Image (AMI) Availability:

AMIs are region-specific. If the template references an AMI that is only available in us-west-2 and not in eu-west-1, the stack will fail to deploy in eu-west-1.

To resolve this, identify the AMI used in us-west-2 and find or create a similar AMI in eu-west-1.

Service Availability:

Some AWS services are not available in all regions. If the template includes resources or services that are not available in eu-west-1, the stack will fail.

Check the AWS Regional Services List to ensure all services and resource types in the template are available in eu-west-1.

References:

Copy an AMI

AWS Regional Services List

Aurora Global Databases are designed for cross-Region disaster recovery with very low RPO, meeting the 20-second requirement. Setting up Aurora as a global database with the correct configuration ensures low-latency replication and rapid failover, making it ideal for compliance with strict disaster recovery requirements.