Uninstall the solution

This section describes how to completely remove the Spatial Data Management Application from your AWS account.

Prerequisites

Configure AWS CLI

Before running any commands, configure your AWS CLI with the appropriate region and profile:

# Set your AWS Region (replace with your deployment region)
export AWS_REGION=<your-region>

# Set your AWS CLI profile (if using named profiles)
export AWS_PROFILE=<your-profile-name>

# Verify configuration
aws sts get-caller-identity

All subsequent commands in this guide use these environment variables. You can also specify --region and --profile flags directly in each command.

Before You Uninstall

Important Warnings

Backup Critical Data

Before uninstalling, backup any data you want to keep:

1. Export DynamoDB Tables

# Create on-demand backups (replace <resource-prefix> with your resource naming prefix)
for table in $(aws dynamodb list-tables --query 'TableNames[?contains(@, `<resource-prefix>`)]' --output text); do
  aws dynamodb create-backup \
    --table-name $table \
    --backup-name "${table}-final-backup-$(date +%Y%m%d)"
done

2. Download S3 Assets

# Get asset bucket name (replace <stack-name> with your CloudFormation stack name)
ASSET_BUCKET=$(aws cloudformation describe-stacks \
  --stack-name <stack-name> \
  --query 'Stacks[0].Outputs[?OutputKey==`AssetBucketName`].OutputValue' \
  --output text)

# Sync to local directory
aws s3 sync s3://$ASSET_BUCKET ./backup/assets/

3. Export CloudWatch Logs

# Export logs to S3 for archival (replace <log-group-name> and <backup-bucket> with your values)
aws logs create-export-task \
  --log-group-name <log-group-name> \
  --from $(date -d '30 days ago' +%s)000 \
  --to $(date +%s)000 \
  --destination <backup-bucket> \
  --destination-prefix cloudwatch-logs/

Uninstallation Methods

Method 1: CloudFormation Stack Deletion (Recommended)

This method deletes all resources except S3 buckets (which are retained by default).

Option A: Using AWS Console

Expected time: 10-15 minutes

Option B: Using AWS CLI

Step 1: Delete the Stack

# Replace <stack-name> with your CloudFormation stack name
aws cloudformation delete-stack \
  --stack-name <stack-name>

Step 2: Monitor Deletion Progress

# Replace <stack-name> with your CloudFormation stack name
aws cloudformation describe-stack-events \
  --stack-name <stack-name> \
  --query 'StackEvents[*].[Timestamp,ResourceStatus,ResourceType,LogicalResourceId]' \
  --output table

Step 3: Wait for Completion

# Replace <stack-name> with your CloudFormation stack name
aws cloudformation wait stack-delete-complete \
  --stack-name <stack-name>

Expected time: 10-15 minutes

Method 2: Force Delete (If Stack Deletion Fails)

If stack deletion fails due to resource dependencies:

Step 1: Identify Stuck Resources

# Replace <stack-name> with your CloudFormation stack name
aws cloudformation describe-stack-events \
  --stack-name <stack-name> \
  --query 'StackEvents[?ResourceStatus==`DELETE_FAILED`].[LogicalResourceId,ResourceStatusReason]' \
  --output table

Step 2: Manually Delete Stuck Resources

Common stuck resources and solutions:

Lambda ENIs (Elastic Network Interfaces):

# List ENIs (replace <resource-prefix> with your resource naming prefix)
aws ec2 describe-network-interfaces \
  --filters "Name=description,Values=*<resource-prefix>*" \
  --query 'NetworkInterfaces[*].[NetworkInterfaceId,Status]'

# Wait for ENIs to be released (automatic, takes 5-10 minutes)

S3 Buckets with Objects:

# Empty bucket before deletion (replace <bucket-name> with your bucket name)
aws s3 rm s3://<bucket-name> --recursive

# Delete bucket
aws s3 rb s3://<bucket-name>

VPC Endpoints:

# Delete VPC endpoints (replace <vpc-endpoint-id> with your VPC endpoint ID)
aws ec2 delete-vpc-endpoints \
  --vpc-endpoint-ids <vpc-endpoint-id>

Step 3: Retry Stack Deletion

# Replace <stack-name> with your CloudFormation stack name
aws cloudformation delete-stack \
  --stack-name <stack-name>

Post-Deletion Cleanup

After stack deletion completes, manually clean up retained resources.

1. Delete S3 Buckets

# List retained buckets
aws s3 ls | grep spatial-data-management

# Empty and delete each bucket
for bucket in $(aws s3 ls | grep spatial-data-management | awk '{print $3}'); do
  echo "Deleting bucket: $bucket"
  aws s3 rm s3://$bucket --recursive
  aws s3 rb s3://$bucket
done

2. Delete CloudWatch Log Groups

# List log groups (replace <log-group-prefix> with your log group prefix)
aws logs describe-log-groups \
  --log-group-name-prefix <log-group-prefix> \
  --query 'logGroups[*].logGroupName'

# Delete each log group
for log_group in $(aws logs describe-log-groups --log-group-name-prefix <log-group-prefix> --query 'logGroups[*].logGroupName' --output text); do
  aws logs delete-log-group --log-group-name $log_group
done

3. Delete KMS Keys

KMS keys enter a pending deletion state (7-30 days) and cannot be immediately deleted.

# List KMS keys
aws kms list-aliases \
  --query 'Aliases[?contains(AliasName, `spatial-data-management`)]'

# Schedule key deletion (minimum 7 days)
aws kms schedule-key-deletion \
  --key-id <key-id> \
  --pending-window-in-days 7

4. Delete Secrets Manager Secrets

# List secrets (replace <resource-prefix> with your resource naming prefix)
aws secretsmanager list-secrets \
  --query 'SecretList[?contains(Name, `<resource-prefix>`)]'

# Delete secrets (with recovery window, replace <secret-id> with your secret ID)
aws secretsmanager delete-secret \
  --secret-id <secret-id> \
  --recovery-window-in-days 7

5. Delete Cognito User Pool

If not automatically deleted:

# Get user pool ID (replace <user-pool-name> with your user pool name)
USER_POOL_ID=$(aws cognito-idp list-user-pools \
  --max-results 60 \
  --query 'UserPools[?contains(Name, `<user-pool-name>`)].Id' \
  --output text)

# Delete user pool
aws cognito-idp delete-user-pool \
  --user-pool-id $USER_POOL_ID

Verification

Verify Stack Deletion

# Check stack status (should return error if deleted, replace <stack-name> with your stack name)
aws cloudformation describe-stacks \
  --stack-name <stack-name>

Expected: Stack with id <stack-name> does not exist

Verify Resource Cleanup

# Check for remaining Lambda functions (replace <resource-prefix> with your resource naming prefix)
aws lambda list-functions \
  --query 'Functions[?contains(FunctionName, `<resource-prefix>`)]'

# Check for remaining DynamoDB tables
aws dynamodb list-tables \
  --query 'TableNames[?contains(@, `<resource-prefix>`)]'

# Check for remaining S3 buckets (replace <bucket-prefix> with your bucket naming prefix)
aws s3 ls | grep <bucket-prefix>

# Check for remaining CloudWatch log groups (replace <log-group-prefix> with your log group prefix)
aws logs describe-log-groups \
  --log-group-name-prefix <log-group-prefix>

Cost Impact After Uninstallation

Immediate Cost Reduction

Ongoing Costs (If Not Cleaned Up)

Complete Cleanup Cost

After manual cleanup of all retained resources: $0