AWS Service Scope Correction

# AWS Service Scope Correction

AI Summary

Purpose:

• Preserve the user's correction about the AWS services used in the LabradorLabs infrastructure and GS Retail application materials.

Key points:

• The verified AWS service scope is Amazon EC2 only.
• MySQL and the related application workloads were self-managed on EC2.
• Do not claim production use of Amazon RDS, Amazon S3, or Amazon EFS for this work.
• Describe the remaining production database as self-managed MySQL on AWS EC2, not as RDS.

Relevant when:

• Writing resumes, portfolio pages, reports, slides, or interview notes about the AWS-to-IDC migration.
• Mapping the user's experience to a job description that asks for AWS managed services.

Do not read full document unless:

• Exact correction provenance is required.

Linked documents:

• ../../wiki/people/hyunwook.md
• ../../wiki/people/career-timeline.md
• ../../worklog/2026/2026-W30.md
• ../../../human/portfolio/items/aws-to-idc-migration.html

Open Questions

• None for the AWS service boundary.

Details

On 2026-07-22, the user corrected the GS Retail application material: the actual AWS service used was EC2 only. References to RDS, S3, and EFS were incorrect and must not be reused.

Normalization rule:

• RDB or operating DB on AWS means the MySQL workload self-managed on EC2 in this context.
• It does not establish Amazon RDS usage.
• The verified migration result remains: the production DB EC2 instance stayed on AWS while other EC2 workloads were moved to IDC/In-house, reducing monthly AWS cost by about 94%.