Residents and clerks need ranked full-text search across municipal code, ordinances, and permit conditions, currently implemented as slow SQL LIKE queries on the permitting RDS database that also serves OLTP. Which architecture should replace that search path?
Select an answer to reveal the explanation.
Short Explanation
LIKE '%plumbing%' on the billing database is a flashlight in a warehouse. OpenSearch is the card catalog built for ranked full-text search, and it keeps those queries off the OLTP box. Replicas of the same SQL habit still aren't a search engine.
Full Explanation
Search-centric workloads such as municipal code and permit-condition retrieval belong on Amazon OpenSearch Service, not on SQL LIKE against the OLTP RDS instance. Offloading search protects transactional SLAs and enables relevance ranking, facets, and text analysis. Extra RDS replicas, CloudWatch Logs Insights, and grepping EBS snapshots do not constitute a search platform.