AWS transform documentation change
Summary
Removed 'Limitations' section and an 'Important' note about reviewing security configurations
Security assessment
The removed 'Important' note emphasized reviewing configurations for security compliance. While this deletion reduces security guidance, there's no evidence it addresses a specific vulnerability. The change appears to be general documentation cleanup.
Diff
diff --git a/transform/latest/userguide/transform-app-vmware.md b/transform/latest/userguide/transform-app-vmware.md index 01f7f6795..9ab699f8d 100644 --- a//transform/latest/userguide/transform-app-vmware.md +++ b//transform/latest/userguide/transform-app-vmware.md @@ -7 +7 @@ -Capabilities and key featuresArchitectureLimitations +Capabilities and key featuresArchitecture @@ -42,17 +41,0 @@ This diagram displays an overview of AWS Transform VMware migration architecture -## Limitations - -AWS Transform has the following limitations: - - * If you stop a running migration job, and then ask the agent to restart it, the job will start again from the beginning and you will lose any progress you have made in the job. However, artifacts created in the job before restarting it will still be available. - - * You can specify one target AWS Region per VMware migration job. To migrate applications to different target Regions, create multiple VMware migration jobs. - - * NSX imports are only supported for end-to-end migration jobs. - - - - -###### Important - -AWS Transform generates network configurations and migration strategies based on your environment assessment. Review these configurations with stakeholders to ensure that they meet your organization's security, compliance, and business requirements. While AWS Transform provides automated configuration recommendations, you are responsible for validating and adjusting the settings to match your security and compliance needs before proceeding with migration. -