After ingest pipelines land municipal ordinances, meeting minutes, and permit PDFs into the analytics platform, clerks need full-text search across those documents. Which service best supports that search and log-analytics style access pattern?
Select an answer to reveal the explanation.
Short Explanation
Clerks need a search box over ordinances—not a video library of PDFs. OpenSearch is the full-text and search-analytics engine after your ingest pipelines land the docs. VPC Lattice, ACM, and Elastic Transcoder aren’t document search platforms.
Full Explanation
Amazon OpenSearch Service is the appropriate engine for full-text search and search-analytics style access once ingest pipelines have landed municipal ordinances, meeting minutes, and permit PDFs into the analytics platform. Clerks need inverted-index style retrieval and aggregations over document text—capabilities OpenSearch is designed to provide—rather than another network or media service. Amazon VPC Lattice is an application networking service for service-to-service connectivity; it is not a full-text index for PDF contents. AWS Certificate Manager private CAs issue and manage certificates; stuffing document text into certificates is not a search architecture. Amazon Elastic Transcoder converting every PDF into an HLS video library for keyword search misunderstands both document search and media transcoding and would be expensive and ineffective for ordinance lookup. Exam caveat: PDFs usually need extraction/indexing pipelines (text extraction, metadata mapping) before OpenSearch is useful; the service choice assumes that ingest path exists. Operational check: index a sample set of ordinances and permits, validate clerk queries return expected documents with acceptable latency, secure the domain (FGAC/IAM/VPC), and monitor storage and query error rates as the corpus grows.