Systems Manager connects managed nodes to configuration, patching and remote-access tools. Use Run Command for a document execution, State Manager for recurring configuration, and Automation for coordinated maintenance actions. Parameter Store holds named application configuration values.
Maintenance windows
A maintenance window defines when Systems Manager should schedule maintenance that could disrupt a workload. It separates the allowed execution period from the document that performs the work.
How it works
- Set the schedule, duration and cutoffThe time before a maintenance window ends when scheduling of new tasks stops.. Cutoff is the number of hours before the end when new tasks stop being scheduled.
- Register targets and tasks. A patching task can run
AWS-RunPatchBaselineagainst managed nodes. - Assign task priorities. Tasks sharing a priority run in parallel; the next priority waits for earlier tasks to reach a final state.
- Choose cutoff behavior.
CONTINUE_TASKis the default.CANCEL_TASKhas different behavior for Run Command and the other task types.
| Task type | Executes |
|---|---|
| Run Command | A command document on managed nodes |
| Automation | An Automation runbookAn ordered set of maintenance or deployment actions executed by Systems Manager Automation. |
| Lambda | A function |
| Step Functions | A Standard workflow, not Express |
Exam cues
- If the question says patch only in an approved maintenance period, think a maintenance window, because its schedule controls task start times.
- If the question says run tasks in an ordered sequence, think task priorities, because later priorities wait for earlier tasks to finish.
- If the question says one patch configuration must span accounts and Regions, think a Quick Setup patch policy, because a maintenance window has one account-Region scope.
Remember
- Cutoff stops new task scheduling; running tasks continue by default.
- Same priority means parallel execution.
- A final state includes failure, so priority alone does not make success conditional.
- For Run Command,
CANCEL_TASKattempts cancellation but cannot guarantee the underlying process stops.
Trap: A window end time is not a guarantee that every process has stopped. Account for duration and cutoff behavior.
Da documentação da AWS (8)
- Maintenance Windows schedules potentially disruptive maintenance on selected resources.
- A maintenance window defines a schedule, duration, targets and registered tasks.
- Cutoff specifies how many hours before the window ends Systems Manager stops scheduling new tasks.
- At cutoff, CANCEL_TASK stops new invocations for Automation, Lambda and Step Functions; for Run Command it attempts cancellation without guaranteeing the underlying process stops.
- AWS-RunPatchBaseline can run as a maintenance-window task to patch managed nodes.
- A maintenance window targets nodes in one account-Region pair; Quick Setup patch policies support multiple account-Region pairs.
- A patch baseline defines the approval rules used to select patches for an operation.
- The AWS-owned Automation runbook AWSEC2-PatchLoadBalancerInstance removes an instance from its Classic Load Balancer, ALB or NLB target group, waits for connection draining, installs OS updates, and registers the instance again.
Session Manager
Session Manager opens remote sessions to managed nodes through the agent connection. Native sessions remove the need for an inbound SSH port, SSH keys or a bastionA separate host used to reach machines in a private network., a separate host used to reach private machines.
How it works
- Use IAM policies to authorize the user and target node. IAM is the permissions system that controls AWS actions.
- Open a browser or CLI session. The channel uses TLSA protocol that encrypts data exchanged over a network connection. 1.2, encryption for data in transit, with optional additional KMS encryption.
- Configure S3 or CloudWatch Logs for native session data. CloudTrail captures session API calls; EventBridge can respond to those API events.
Exam cues
- If the question says shell access without inbound ports, think native Session Manager, because the session uses the managed-node channel.
Remember
- Linux and macOS default to
ssm-user, which is added tosudoers, the configuration granting privileged command access. - CloudTrail API records and session content logs are different outputs.
- A bastion host (jump box) is a single, internet-exposed access point to a private network; Session Manager removes the need for it.
Trap: SSH and port-forwarding session content cannot be logged by Session Manager. Use native sessions when a command transcript is required.
Da documentação da AWS (15)
- Session Manager provides browser or CLI access to managed nodes without opening inbound ports, maintaining bastions or managing SSH keys for its native sessions.
- IAM policies control which users may start sessions and which managed nodes they can access.
- Session Manager encrypts the client-to-node channel with TLS 1.2 and can add KMS encryption.
- Native session data can be logged to S3 or CloudWatch Logs, with optional KMS encryption.
- CloudTrail records Session Manager API calls.
- Session content logging is unavailable for Session Manager port-forwarding and SSH sessions.
- EventBridge can use CloudTrail StartSession, ResumeSession and TerminateSession API events; an exit command inside a session does not itself produce a detected API event.
- A maintenance window can schedule AWS-RunPatchBaseline for managed nodes outside business hours.
- Bastion: A separate host used to reach machines in a private network.
- TLS: A protocol that encrypts data exchanged over a network connection.
- sudoers: The operating-system configuration that grants users permission to run privileged commands.
- A bastion host, or jump box, is a server that is the single access point from an external network to resources in a private network, and its exposure to the internet is a security risk.
- Default Host Management Configuration supplies node permissions without individual instance profiles in each account and Region where enabled.
- DHMC requires EC2 instances to use IMDSv2.
- DHMC requires SSM Agent 3.2.582.0 or later.
Parameter Store tiers and policies
Parameter Store keeps applicationA logical group of AWS resources operated together as one workload. configuration as named values. The tier determines storage limits and policy support; the parameter type determines how the value is represented.
How it works
- Choose
Stringfor text,StringListfor a comma-separated list, orSecureStringfor an encrypted value. - Choose the standard or advanced tier. Upgrade a standard parameter if its size, policy or sharing needs require advanced.
- Update the value to create a numbered version. Request a specific version when a deployment must retain a reviewed value.
- Attach parameter policies to an advanced parameter when needed.
| Property | Standard | Advanced |
|---|---|---|
| Value size | 4 KB | 8 KB |
| Parameters per account and Region | 10000 | 100000 |
| Storage charge | No additional charge | Charged |
| Parameter policies | Unsupported | Supported |
| Cross-account AWS RAM sharing | Unsupported | Supported |
Exam cues
- If the question says configuration needs parameter policies, think the advanced tier, because standard parameters do not support policies.
- If the question says credentials require automatic rotation, think Secrets Manager, because AWS recommends it for that requirement.
- If the question says reuse configuration across accounts, think advanced parameters with AWS RAM, because standard parameters cannot use that sharing feature.
- If the question says an AMIA template used to launch an EC2 instance with its operating system and software. parameter is needed in multiple Regions, think a parameter in each Region, because parameters belong to one account and Region.
- If the question says heavy parameter reads are throttled, think higher throughput, because it raises the API transaction quota at extra charge.
Remember
- Version one is initial; edits increment it.
- No version specified means latest; a nonexistent version causes an error.
- Private subnets reach Systems Manager through interface VPC endpointsA private network entry point for connecting to a supported service through AWS PrivateLink..
- Hierarchies: up to 15 levels; GetParametersByPath reads everything under a level.
Trap: Shrinking an advanced value does not permit downgrading the parameter.
Da documentação da AWS (20)
- Parameter Store supports String, comma-separated StringList and encrypted SecureString values.
- Standard parameter values can be up to 4 KB.
- The standard tier supports 10000 parameters per account and Region.
- Standard parameters have no additional storage charge.
- Standard parameters do not support parameter policies.
- Advanced parameter values can be up to 8 KB.
- The advanced tier supports 100000 parameters per account and Region.
- Advanced parameters incur charges.
- Advanced parameters support parameter policies.
- A standard parameter can become advanced; an advanced parameter cannot be changed back to standard.
- Cross-account sharing through AWS RAM requires advanced parameters.
- Parameter values begin at version one.
- Each parameter value edit increments the version.
- Requests without a parameter version use the latest version.
- Requesting a nonexistent parameter version fails rather than falling back to latest.
- AWS recommends Secrets Manager for credentials requiring automatic rotation.
- Parameter Store parameters belong to one account and Region, so each Region needs its own parameter, for example with that Region's AMI ID.
- Parameter Store has a default throughput quota for API transactions per second; higher throughput can be turned on for heavier workloads, at extra charge.
- Systems Manager can be reached through interface VPC endpoints (AWS PrivateLink), so managed nodes and applications in a VPC need no public endpoint access.
- Parameter Store names can form hierarchies of up to 15 levels separated by forward slashes, and GetParametersByPath returns all parameters under a chosen level.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 16 flashcards em lista
A team needs Systems Manager patch installation only during an approved maintenance period. Which feature controls execution time?
A maintenance window with a schedule, duration, cutoff, targets and a task such as AWS-RunPatchBaseline. The baseline controls approved patches.
A team must patch EC2 and registered on-premises nodes outside business hours. How can Systems Manager select patches and execution time?
Use Patch Manager baselines to select approved patches, then schedule AWS-RunPatchBaseline in a maintenance window.
Instances behind an ALB must be patched without receiving traffic while they patch, within a defined window. What fits with the least custom work?
Run the AWSEC2-PatchLoadBalancerInstance Automation runbook from a Systems Manager maintenance window. It deregisters each instance, waits for draining, patches it and registers it again.
Engineers need Systems Manager shell access without inbound SSH and with an audit trail. What should be configured?
Use native Session Manager access with IAM authorization. Send session data to S3 or CloudWatch Logs; CloudTrail records session API calls.
Does Systems Manager Session Manager record typed commands in SSH or port-forwarding sessions?
No. Session content logging is unavailable for those sessions. CloudTrail still records Session Manager API calls.
A hybrid fleet needs access without inbound SSH and scheduled patching outside business hours. Which Systems Manager features fit?
Session Manager for native remote access and Patch Manager through a maintenance window for scheduled patching.
Administrators reach private EC2 instances through a public bastion host with SSH open. Which AWS feature removes the inbound port and the bastion?
AWS Systems Manager Session Manager, with sessions authorized by IAM and logged.
An EC2 fleet needs Systems Manager permissions without individual instance profiles. What must be enabled and installed?
Enable Default Host Management Configuration in each account and Region. Instances must use IMDSv2 and SSM Agent 3.2.582.0 or later.
How do Systems Manager Parameter Store standard and advanced parameters differ?
Standard: 4 KB values, 10000 parameters per account and Region, no additional storage charge and no policies. Advanced: 8 KB, 100000 parameters, charges, policies and AWS RAM sharing. Advanced parameters cannot be downgraded.
A deployment must keep using a reviewed Systems Manager parameter value after later edits. How should it retrieve the value?
Specify the parameter version. Value changes create numbered versions; omitting a version retrieves the latest, and requesting a nonexistent version fails.
A deployment needs to store an encrypted credential in AWS Systems Manager Parameter Store. Which parameter type should it use?
SecureString. Parameter Store supports encrypted SecureString values.
Which Systems Manager Parameter Store types represent text, a comma-separated list and an encrypted value?
String for text, StringList for a comma-separated list, and SecureString for an encrypted value.
A template reads a golden AMI ID from Parameter Store and must deploy in three Regions. What is needed?
A parameter in each Region holding that Region's AMI ID; parameters are Regional.
An application reading parameters heavily gets ThrottlingException from Parameter Store. What setting helps?
Turn on higher throughput for Parameter Store (extra charge), or cache the values in the application.
Applications in private subnets with no NAT gateway must read AWS Systems Manager Parameter Store values. What should the VPC add?
An interface VPC endpoint for Systems Manager (AWS PrivateLink).
An application must load every AWS Systems Manager Parameter Store value for /prod/payments/ at startup. Which naming and API fit?
Hierarchical names such as /prod/payments/db-url, read with GetParametersByPath (recursively if needed).