ssm-doctor 0.1.0

Diagnose why an EC2 instance is not reachable via AWS Systems Manager

ssm-doctor

Diagnose why an EC2 instance is not reachable via AWS Systems Manager (SSM).

Install

pip install ssm-doctor

From source:

pip install -e .

60-second demo

# Text report (exit 0 if PingStatus is Online, else 1)
ssm-doctor i-0123456789abcdef0 --profile myprofile --region us-east-1

# Machine-readable output
ssm-doctor i-0123456789abcdef0 --json --region us-east-1

Example output:

ssm-doctor: i-0123456789abcdef0
  [PASS] ec2_state: Instance state is 'running'.
           state=running
           vpc_id=vpc-abc
           subnet_id=subnet-xyz
  [PASS] iam_instance_profile: IAM instance profile is attached.
  [PASS] ssm_ping: SSM PingStatus is 'Online'.
           ping_status=Online
           agent_version=3.2.0
Next steps: none — instance appears reachable via SSM.
Result: REACHABLE (Online)

What it checks

Read-only boto3 calls (graceful errors if permissions are missing):

Check	Source
Instance state, VPC, subnet	ec2:DescribeInstances
IAM instance profile present	ec2:DescribeInstances
SSM registration / PingStatus / AgentVersion / LastPingDateTime	ssm:DescribeInstanceInformation

Publishing to PyPI

pip install build twine
python -m build
twine upload dist/*

Or push a v* tag; GitHub Actions can publish via trusted publishing (see .github/workflows/publish.yml).

License

MIT