A town council asks whether every municipal app should run on AWS Outposts 'to be modern.' Which cost-aware recommendation is appropriate?
Select an answer to reveal the explanation.
Short Explanation
Outposts is a specialty tool, not a fashion statement. If residency or on-site latency doesn't force it, the standard AWS Region is usually cheaper and simpler for city apps.
Full Explanation
Using AWS Outposts only when data residency, local latency, or on-premises adjacency requirements justify it—and otherwise preferring Regional AWS—is the correct cost-aware recommendation when a town council asks whether every municipal app should run on Outposts to appear modern. Outposts extends AWS on premises at a premium; fashion is not a requirements statement. Deploying Outposts for all workloads because Region pricing is always higher fails factually and economically: Regional deployments are typically more cost-effective for ordinary apps without locality constraints. Replacing all VPCs with Outposts racks and disabling Cost Explorer fails by maximizing footprint while removing the visibility needed to manage spend. Claiming Outposts is required for any Amazon S3 usage fails conceptually: S3 is a Regional object service and does not mandate Outposts for municipal object storage. Exam caveat: justify Outposts with concrete residency/latency/adjacency needs; do not treat it as a default modernization badge or an S3 prerequisite. Operational check: list apps with true on-prem latency or residency constraints; keep the rest in Region; price Outposts only for justified slices; keep Cost Explorer enabled; and brief council with a requirements-versus-cost matrix rather than a blanket Outposts mandate.