AWS solutions documentation change
Summary
Added platform selection criteria and SSM Automation Document execution details
Security assessment
While mentioning authentication mechanisms and execution environments, the changes focus on operational characteristics rather than specific security controls or vulnerabilities. No security hardening guidance or vulnerability mitigation is introduced.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/run-automation-from-console.md b/solutions/latest/cloud-migration-factory-on-aws/run-automation-from-console.md index ec0f8b211..056251cfc 100644 --- a//solutions/latest/cloud-migration-factory-on-aws/run-automation-from-console.md +++ b//solutions/latest/cloud-migration-factory-on-aws/run-automation-from-console.md @@ -4,0 +5,2 @@ +When to Use Each PlatformScript Execution Platforms + @@ -9 +11,29 @@ The Cloud Migration Factory on AWS solution provides an automation engine allowi -Jobs initiated from AWS CMF are run on automation servers that can be hosted in the AWS Cloud or on-premise. These servers need to run Windows with the AWS SSM agent installed, along with Python and Microsoft PowerShell. You can also install other frameworks as required for custom automations. Refer to [Step 6. Build a migration automation server](./step6.html) for details of the automation server build. At least one automation server is required to run jobs from the AWS CMF console. +Jobs initiated from AWS CMF can be run either via SSM Automation Document or an automation server that can be hosted in the AWS Cloud or on-premise. These servers need to run Windows with the AWS SSM agent installed, along with Python and Microsoft PowerShell. You can also install other frameworks as required for custom automations. Refer to [Step 6. Build a migration automation server](./step6.html) for details of the automation server build. At least one automation server is required to run jobs from the AWS CMF console. + +## When to Use Each Platform + +### Use Traditional Automation Server when: + + * Scripts require direct network connectivity to on-premises systems + + * Custom software installations or dependencies are needed + + * Consistent Windows-based execution environment is required + + * Complex authentication mechanisms with on-premises systems are involved + + + + +### Use SSM Automation Document when: + + * Performing AWS-native operations + + * No special software dependencies are required + + * Scalability and parallel execution are important + + * Minimal maintenance overhead is desired + + + @@ -66,0 +97,30 @@ When you submit the automation job, the following process is initiated: +## Script Execution Platforms + +The Cloud Migration Factory supports two compute platforms for executing automation scripts: + +### Traditional Automation Server + +The default execution method using a Windows-based automation server. This requires maintaining a dedicated server with the required software installations and configurations as detailed in the "Build a Migration Automation Server" section. + +### SSM Automation Document + +Scripts can be executed directly through AWS Systems Manager Automation Documents by specifying "SSM Automation Document" as the Compute Platform in the Package-Structure.yaml file. This option: + + * Eliminates the need for a dedicated automation server + + * Leverages AWS Systems Manager’s native automation capabilities + + * Reduces maintenance overhead + + * Provides better scalability and reliability + + + + +To use the SSM Automation Document platform: + + 1. In your script package’s Package-Structure.yaml file, set: ` `yaml ComputePlatform: "SSM Automation Document" ` ` + + + +