AWS Systems Manager Automation Builder

MonitoringAWS

Build SSM Automation document configurations with multi-step workflows, branching logic, and approval gates.

AWS Systems Manager Configuration

Build SSM Automation document configurations with multi-step workflows, branching logic, and approval gates.

Required Fields

SchemaVersionMainSteps

{
  "Description": "Automated EC2 instance remediation - restart unhealthy instances",
  "SchemaVersion": "0.3",
  "AssumeRole": "arn:aws:iam::123456789012:role/SSMAutomationRole",
  "Parameters": {
    "InstanceId": {
      "Type": "String",
      "Description": "The ID of the EC2 instance to remediate"
    },
    "AutomationAssumeRole": {
      "Type": "String",
      "Default": "arn:aws:iam::123456789012:role/SSMAutomationRole",
      "Description": "IAM role for automation execution"
    },
    "ApproverArn": {
      "Type": "String",
      "Default": "",
      "Description": "ARN of the approver for manual approval step"
    }
  },
  "MainSteps": [
    {
      "Name": "describeInstance",
      "Action": "aws:executeAwsApi",
      "Inputs": {
        "Service": "ec2",
        "Api": "DescribeInstances",
        "InstanceIds": ["{{InstanceId}}"]
      },
      "Outputs": [
        {
          "Name": "InstanceState",
          "Selector": "$.Reservations[0].Instances[0].State.Name",
          "Type": "String"
        }
      ]
    },
    {
      "Name": "checkInstanceState",
      "Action": "aws:branch",
      "Inputs": {
        "Choices": [
          {
            "NextStep": "stopInstance",
            "Variable": "{{describeInstance.InstanceState}}",
            "StringEquals": "running"
          }
        ],
        "Default": "startInstance"
      }
    },
    {
      "Name": "stopInstance",
      "Action": "aws:changeInstanceState",
      "Inputs": {
        "InstanceIds": ["{{InstanceId}}"],
        "DesiredState": "stopped"
      }
    },
    {
      "Name": "startInstance",
      "Action": "aws:changeInstanceState",
      "Inputs": {
        "InstanceIds": ["{{InstanceId}}"],
        "DesiredState": "running"
      }
    },
    {
      "Name": "verifyInstance",
      "Action": "aws:waitForAwsResourceProperty",
      "TimeoutSeconds": 300,
      "Inputs": {
        "Service": "ec2",
        "Api": "DescribeInstanceStatus",
        "InstanceIds": ["{{InstanceId}}"],
        "PropertySelector": "$.InstanceStatuses[0].InstanceStatus.Status",
        "DesiredValues": ["ok"]
      },
      "IsEnd": true
    }
  ]
}

Generated Output

Output will appear here...

Overview

Build SSM Automation document configurations with multi-step workflows, branching logic, and approval gates. This tool helps AWS engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

How Engineers Use This

•Designing a Systems Manager Automation configuration for a new AWS workload where the team wants the spec reviewed before any console click happens.
•Producing a Systems Manager Automation snapshot for a security audit where the auditor wants the canonical config alongside the rendered policy.
•Comparing two candidate Systems Manager Automation layouts side by side to choose the one with the cleaner blast radius.
•Building a Systems Manager Automation reference implementation for a customer integration where you cannot rely on their AWS console access.

Questions & Answers

Does this Systems Manager Automation builder consider IAM permissions needed to apply the configuration?

No — generating a Systems Manager Automation configuration is independent of the IAM permissions required to apply it. Apply the output with a principal that has the documented privileges for that service. If you want a least-privilege starting point, the AWS Managed Policy generator and IAM Access Analyzer can produce an action list scoped to what your apply needs.

How does this Systems Manager Automation builder keep up with new AWS features?

The Systems Manager Automation options surface what is currently documented in the AWS reference for that service. When AWS adds a new property or value, it is added here after we have verified the schema in a real account. If a brand-new feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.

Related Learning Guides

DynamoDB Data Modeling28 min read
Cost Optimization Strategies26 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

AWS Systems Manager Automation Builder

MonitoringAWS

Build SSM Automation document configurations with multi-step workflows, branching logic, and approval gates.

AWS Systems Manager Configuration

Build SSM Automation document configurations with multi-step workflows, branching logic, and approval gates.

Required Fields

SchemaVersionMainSteps

Generated Output

Output will appear here...

Overview

How Engineers Use This

•Designing a Systems Manager Automation configuration for a new AWS workload where the team wants the spec reviewed before any console click happens.
•Producing a Systems Manager Automation snapshot for a security audit where the auditor wants the canonical config alongside the rendered policy.
•Comparing two candidate Systems Manager Automation layouts side by side to choose the one with the cleaner blast radius.
•Building a Systems Manager Automation reference implementation for a customer integration where you cannot rely on their AWS console access.

Questions & Answers

Does this Systems Manager Automation builder consider IAM permissions needed to apply the configuration?

How does this Systems Manager Automation builder keep up with new AWS features?

Related Learning Guides

DynamoDB Data Modeling28 min read
Cost Optimization Strategies26 min read

Was this tool helpful?