AWS elasticbeanstalk documentation change
Summary
Updated migration process steps and added workflow execution options including remote execution via bastion host
Security assessment
Added documentation about using a bastion host for remote migration execution, which is a security best practice for accessing protected resources. However, there is no evidence this addresses a specific security vulnerability.
Diff
diff --git a/elasticbeanstalk/latest/dg/dotnet-migrating-applications.md b/elasticbeanstalk/latest/dg/dotnet-migrating-applications.md index b23f2dbdc..1ee8c57f2 100644 --- a//elasticbeanstalk/latest/dg/dotnet-migrating-applications.md +++ b//elasticbeanstalk/latest/dg/dotnet-migrating-applications.md @@ -13 +13 @@ Use the **eb migrate** command in the Elastic Beanstalk Command Line Interface ( -The following steps summarize the process that the **eb migrate** operation performs to transition your application to the AWS Cloud: +The following steps summarize the process that the `eb migrate` operation performs to transition your application to the AWS Cloud: @@ -15 +15 @@ The following steps summarize the process that the **eb migrate** operation perf - 1. Automatically detect IIS sites, applications, and virtual directories. + 1. Discover IIS sites and their configurations. @@ -17 +17 @@ The following steps summarize the process that the **eb migrate** operation perf - 2. Package application content and dependencies. + 2. Package application content and configuration. @@ -19 +19 @@ The following steps summarize the process that the **eb migrate** operation perf - 3. Create and configure an Elastic Beanstalk environment with the required resources. + 3. Create Elastic Beanstalk environment and application. @@ -21 +21 @@ The following steps summarize the process that the **eb migrate** operation perf - 4. Deploy your application with minimal downtime. + 4. Deploy the application with preserved settings. @@ -25,0 +26,4 @@ The following steps summarize the process that the **eb migrate** operation perf +###### Workflow and location execution options + +The **eb migrate** command provides options for flexible migration workflows and execution locations. By default, run the command on the target server that contains the application you want to migrate to Elastic Beanstalk. If you can't run commands directly on the application server, use the `remote` option to run the command from a bastion host that connects to the target server containing your application and configurations. To complete the migration in two steps, you can also generate the migration package without deploying it using the `archive-only` option and then deploy it later at your convenience using the `archive` option. +