A product currently runs in one region on EC2 Auto Scaling instances behind an ALB with all data in an Amazon Aurora database. When expanding to Europe and Asia, the company wants a single, global product catalog but must keep customer information and purchase records stored regionally for compliance. With minimal application changes, how should the company meet these requirements?

The correct option addresses both the global catalog and regional data requirements with minimal application changes. Aurora read replicas provide a globally consistent product catalog across regions without requiring application modifications to handle data synchronization. Deploying additional local Aurora instances in each region for customer information and purchases ensures data residency compliance. Incorrect options: Using Redshift for the catalog is overkill and introduces a new database type, increasing complexity. DynamoDB for regional data is plausible but Aurora is already in use. DynamoDB global tables for the catalog would work, but using separate regional DynamoDB tables for customer data would require application changes to manage two different database types. Using Aurora for the catalog and DynamoDB global tables for customer data would violate the regional data storage requirement for customer information.