ssm-patch-quicksetup-prod

Runs scan-first AWS SSM Patch Manager Quick Setup workflows for PROD instances with TRUST baselines.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill ssm-patch-quicksetup-prod-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ssm-patch-quicksetup-prod
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/ssm-patch-quicksetup-prod
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill ssm-patch-quicksetup-prod-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PROD patching with AWS SSM Patch Manager and Quick Setup often fails through baseline drift, accidental reboots, oversized evidence dumps, and vague install approvals. This Skill enforces a repeatable scan-first workflow that proves patch compliance safely against TRUST AL2/AL2023 baselines. ## Core Features & Use Cases - Baseline Drift Detection and Repair: Verifies Quick Setup selects the TRUST baselines (AL2-TRUST, AL2023-TRUST) instead of AWS predefined baselines before any scan. - Safe Execution Pattern: Runs scan-only validation first, then gated install pilots with RebootOption=NoReboot, explicit target guards, and reboot as a separate approval decision. - Compact Evidence Discipline: Records command ids, target counts, and before/after missing/failed/pending-reboot counts, uploading only compact summaries to S3 instead of raw command output. - Worker Delegation: Delegates patching tasks to PAT-style tmux workers using short prompt files with concrete approval boundaries. - Use Case: An operator needs to close VA findings on PROD Amazon Linux hosts. The Skill repairs Quick Setup baseline selection, runs a scan-only pass, executes a small NoReboot install pilot, then plans a reboot/rescan closure with compact S3 evidence. ## Quick Start Use the ssm-patch-quicksetup-prod skill to run a scan-only patch validation across all PROD EC2 instances against the TRUST baselines and summarize missing and failed patches.

Frequently Asked Questions about ssm-patch-quicksetup-prod

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a scan-only patch validation with SSM Patch Manager?▼

Run AWS-RunPatchBaseline with Operation=Scan against running, SSM-online EC2 instances tagged env=prod after confirming the correct baseline selection. Summarize results by target count, success/failed invocations, missing patches, failed patches, and installed-pending-reboot counts.

How do I install patches with SSM without rebooting servers?▼

Use AWS-RunPatchBaseline with Operation=Install and RebootOption=NoReboot after explicit approval naming the exact target scope. Treat reboot as a separate approval decision and run a reboot/rescan pass afterward to close the loop.

Why does Quick Setup use AWS predefined baselines instead of custom baselines?▼

Quick Setup patch policies can select AWS predefined baselines even when account defaults point to custom baselines like AL2-TRUST or AL2023-TRUST. Treat this as drift: repair the Quick Setup baseline selection first, then rerun scan-only validation before trusting compliance state.

Does InstalledPendingRebootCount mean patching is complete?▼

No. InstalledPendingRebootCount greater than zero means a reboot is required to finish the host state, but it does not grant permission to reboot. MissingCount=0 and FailedCount=0 only means patch-closed for the selected baseline at scan time.

When should raw SSM command output go to S3?▼

Keep raw command stdout and stderr local by default and upload only compact RESULT.md files, command ids, target guards, and invocation summaries to S3. Set OutputS3BucketName on send-command only when raw S3 output is explicitly requested or required for audit.