Operations staff need a place in AWS to keep operational parameters and credential-style values that automation and instances can look up, alongside related Systems Manager capabilities. Which service family fits that pattern at foundational depth?
Select an answer to reveal the explanation.
Short Explanation
Systems Manager is the ops toolbox — Parameter Store is the labeled drawer where configs and secrets-style values live so scripts and instances can pull them instead of hard-wiring them. Same family that helps you run and manage fleets without reinventing a config server.
Full Explanation
AWS Systems Manager, including Parameter Store, fits the foundational pattern for keeping operational parameters and credential-style values that automation and instances can look up alongside related Systems Manager capabilities. Systems Manager is the ops toolbox; Parameter Store is the labeled drawer for configs and secure parameters so scripts and instances pull values instead of hard-wiring them. Amazon QuickSight is analytics/BI, not the parameter store. Amazon Polly reads text aloud; it is not an ops parameter service. AWS Certificate Manager manages TLS certificates and is not the only place to store database passwords. Distractors fail by pointing at BI, speech, and certificate services instead of Systems Manager Parameter Store patterns. Exam caveat: distinguish standard versus secure parameters, prefer Secrets Manager when rich rotation for secrets is the focus, and still apply IAM least privilege to who can GetParameter. Operational check: move operational endpoints, feature flags, and approved secure parameters into Parameter Store paths by environment, encrypt sensitive parameters with KMS, update instance profiles and automation roles to read only their paths, and retire hardcoded values from user-data scripts.