AWS elasticbeanstalk documentation change
Summary
Added new command options for remote migration execution (--remote, --target-ip, --username, --password) and examples showing credential usage
Security assessment
Documents secure remote execution patterns using bastion hosts, reducing exposure of source servers. However, the inclusion of plaintext password parameters in command examples introduces a security risk if followed without proper credential handling, though this is not explicitly addressed as a vulnerability fix.
Diff
diff --git a/elasticbeanstalk/latest/dg/eb3-migrate.md b/elasticbeanstalk/latest/dg/eb3-migrate.md index f0d14c8b0..5e75de42a 100644 --- a//elasticbeanstalk/latest/dg/eb3-migrate.md +++ b//elasticbeanstalk/latest/dg/eb3-migrate.md @@ -176 +176 @@ Name | Description -`-ao` or `--archive-only` | Create only the destination archive directory without deployment. The resulting directory can be manually deployed using **eb create** or **eb deploy**. +`-ao` or `--archive-only` | Create only the destination archive directory without deployment. The resulting directory can be manually deployed using **eb migrate** with the `archive` option, or **eb deploy**. @@ -185,0 +186 @@ This is an account-wide setting that affects all future Amazon EBS volume creati +`--force` | Skip confirmation prompts during operations. When used with **cleanup** subcommand, removes migration artifacts without confirmation. @@ -190,0 +192,4 @@ This is an account-wide setting that affects all future Amazon EBS volume creati +`--remote` | Indicates to execute the migration in remote mode. This option allows execution from a bastion host, which connects to the target server that contains the application and configurations to be migrated to Elastic Beanstalk. Running from the bastion server, `eb migrate` discovers configurations, stages migration logic on the bastion host, then deploys your application to a new Elastic Beanstalk environment. This option eliminates the need to install the EB CLI and Python on the Windows server that you need to migrate. You install Python and the EB CLI on a bastion host instead, where you run the **eb migrate** command with the `--remote` option. Use the `--target-ip` option to specify the host with the IIS configurations to migrate. Must be used with `--target-ip`, `--username`, and `--password`. +`--target-ip` `ip-address` | Public IP address of the remote Windows machine that contains the IIS servers to be migrated. Required when using `--remote`. Can only be specified when using `--remote`. +`--username` `username` | Username of the user profile to access the remote Windows machine that contains the IIS servers to be migrated. Required when using `--remote`. Can only be specified when using `--remote`. +`--password` `password` | Password of the user profile to access the remote Windows machine that contains the IIS servers to be migrated. Required when using `--remote`. Can only be specified when using `--remote`. @@ -224 +228,0 @@ Specify only the role name, not the full ARN. Elastic Beanstalk automatically cr -`--force` | Skip confirmation prompts during operations. When used with **cleanup** subcommand, removes migration artifacts without confirmation. @@ -393,0 +398,45 @@ Migration with custom IAM roles: +### Remote Execution Examples + +Migrating IIS applications from a remote Windows server: + + + PS C:\migrations_workspace > eb migrate ` + --remote ` + --target-ip "192.0.2.10" ` + --username "administrator" ` + --password "YourPassword123" ` + --application-name "RemoteApp" ` + --environment-name "RemoteEnv" + INFO: Establishing SSH connection to remote host 192.0.2.10... + INFO: Connection established + INFO: Discovering IIS sites on remote host... + INFO: Found 2 sites: Default Web Site, API + INFO: Extracting site configurations... + INFO: Generating source bundle for sites, applications, and virtual directories... + Default Web Site/ -> .\migrations\latest\upload_target\DefaultWebSite.zip + API/ -> .\migrations\latest\upload_target\API.zip + + Creating application version + Creating environment + + Environment details for: RemoteEnv + Application name: RemoteAppstage mi + Region: us-west-2 + Deployed Version: app-230320_153045 + Environment ID: e-abcdef1234 + Platform: 64bit Windows Server 2019 v2.7.0 running IIS 10.0 + Tier: WebServer-Standard-1.0 + CNAME: remoteenv.us-west-2.elasticbeanstalk.com + Updated: 2023-03-20 15:30:45 + +Remote migration with specific site selection: + + + PS C:\migrations_workspace > eb migrate ` + --remote ` + --target-ip "192.0.2.10" ` + --username "administrator" ` + --password "YourPassword123" ` + --sites "API" ` + --instance-type "c5.large" +