Systems Manager

From Kautepedia
Revision as of 03:57, 23 April 2025 by Solomon.pidoke (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

AWS Systems Manager is used to manage instances remotely, run commands, and automate administration tasks across EC2 and hybrid environments.

Managed Instances[edit | edit source]

The following instances are currently managed by AWS Systems Manager:

  • media wiki
  • bastion host

Activation Details[edit | edit source]

  • Activation Code: ajRacuSc5O0Ff+FxAtI5
  • Activation ID: 77fa3be7-fd52-4987-97b4-dbb785621366

Unmanaged Instances[edit | edit source]

  • neo4j (Not managed due to missing IPv6 address)

Resource scheduler[edit | edit source]

Used to automate start/stop of EC2 instances on a schedule.

Affected resources[edit | edit source]

Configuration EC2ScheduleManager is used for the resource scheduler.

Instances with tag key/pair ResourceGroup = On are affected. As at March 2025 this encompasses:

  • Mediawiki
  • Bastion Host

Bastion host instance is excluded for ingestion/ETL purposes overnight, and IDE access during business hours.

Schedule[edit | edit source]

Schedule is:

  • START 0730
  • STOP 1930.[1]

Notes[edit | edit source]

  • Ensure that all managed instances have the **AmazonSSMManagedInstanceCore** IAM role attached.
  • The SSM Agent must be installed and running for instances to remain in Systems Manager.
  • IPv6 connectivity is required for instances that rely on IPv6 networking.

References[edit | edit source]

  1. Pacific/Auckland timezone.