This section documents the resource teardown procedures, stack destruction workflow, cost management practices, and post-operational verification steps for the deployed AWS cloud infrastructure.
To prevent unnecessary billing and ensure total resource cleanup upon completion of project evaluation, the following teardown sequence was executed:
Storage Purging Phase: Prior to CloudFormation stack deletion, all persistent objects within private and public S3 buckets were purged:
aws s3 rm s3://<export-bucket-name> --recursive
CloudFormation Stack Destruction:
Executing the SAM CLI stack removal command deletes all provisioned resources defined within template.yaml:
cd infra
sam delete --no-prompts
The automated stack destruction process cleanly removed the following AWS cloud resources:
| AWS Resource | Resource Name / Pattern | Action Taken |
|---|---|---|
| API Gateway | HttpApi (chrome-flashcard-backend-*) |
Terminated and HTTP endpoints released |
| AWS Lambda | ApiFunction (chrome-flashcard-backend-*) |
Function, execution runtime, and IAM Execution Roles deleted |
| DynamoDB Tables | UsersTable, FlashcardsTable, CategoriesTable |
Tables destroyed & provisioned RCUs/WCUs released |
| Amazon S3 | ExportBucket |
Bucket policy and storage container removed |
| IAM Policies | Inline SAM policies (DynamoDBCrudPolicy, S3CrudPolicy) |
Role policies detached and deleted |
Completion of the teardown process was empirically verified using the AWS CLI:
CloudFormation Audit:
aws cloudformation describe-stacks --stack-name chrome-flashcard-backend
Result: Stack with id chrome-flashcard-backend does not exist (Status confirmed).
DynamoDB Audit:
aws dynamodb list-tables
Result: Verified zero remaining project-related table instances.
CloudWatch Log Audit:
aws logs describe-log-groups --log-group-name-prefix "/aws/lambda/chrome-flashcard"
Result: Log groups successfully purged or set to short retention windows, completing system decommissioning.
The project successfully demonstrated an offline-first Chrome Extension (MV3) combined with a scalable, secure AWS Serverless infrastructure (API Gateway, Lambda, DynamoDB, Amazon Translate, and S3). System verification confirms operational stability, robust data synchronization, and complete cloud resource lifecycle control.