AWS Security ChangesHomeSearch

AWS elasticbeanstalk documentation change

Service: elasticbeanstalk · 2025-06-28 · Documentation medium

File: elasticbeanstalk/latest/dg/dotnet-migrating-applications-prerequisites.md

Summary

Added requirements for remote migration using bastion hosts including network security configurations

Security assessment

Detailed security group rules, SSH configuration, and firewall requirements for bastion host usage enhance documentation about secure migration patterns but don't indicate resolution of a specific security flaw.

Diff

diff --git a/elasticbeanstalk/latest/dg/dotnet-migrating-applications-prerequisites.md b/elasticbeanstalk/latest/dg/dotnet-migrating-applications-prerequisites.md
index af7541184..aa52e1b15 100644
--- a//elasticbeanstalk/latest/dg/dotnet-migrating-applications-prerequisites.md
+++ b//elasticbeanstalk/latest/dg/dotnet-migrating-applications-prerequisites.md
@@ -12 +12 @@ Before using the **eb migrate** command, ensure your environment meets these req
-Your server must run Internet Information Services (IIS) version 7.0 or later. IIS 10.0 on Windows Server 2016 or later provides the most compatible environment for migration.
+The server that you're migrating from must run Internet Information Services (IIS) version 7.0 or later. IIS 10.0 on Windows Server 2016 or later provides the most compatible environment for migration.
@@ -42 +42,10 @@ Your source environment should run Windows Server 2016 or later for optimal comp
-Python and the Elastic Beanstalk Command Line Interface (EB CLI) must be installed on your source server. While it is not required, we recommend installing the EB CLI inside a `virtualenv` sandbox as described in [Install the EB CLI in a virtual environment](./eb-cli3.html#eb-cli3-install-virtualenv).
+  * _Default workflow (without the`--remote` option)_:
+
+    * Python and the Elastic Beanstalk Command Line Interface (EB CLI) must be installed on the server that contains the application that you want to migrate to Elastic Beanstalk. While it is not required, we recommend installing the EB CLI inside a `virtualenv` sandbox as described in [Install the EB CLI in a virtual environment](./eb-cli3.html#eb-cli3-install-virtualenv).
+
+  * _Using the`--remote` option_:
+
+    * Python and the Elastic Beanstalk Command Line Interface (EB CLI) must be installed on your bastion host. While it is not required, we recommend installing the EB CLI inside a `virtualenv` sandbox as described in [Install the EB CLI in a virtual environment](./eb-cli3.html#eb-cli3-install-virtualenv).
+
+
+
@@ -49 +58 @@ You need the following credentials and permissions:
-  * Administrator privileges on the source IIS server
+  * Administrator privileges on the source IIS server or on the bastion host (if using the `--remote` option).
@@ -59 +68 @@ You need the following credentials and permissions:
-Microsoft Web Deploy tool (version 3.6 or later) must be installed on your source server. This tool is used by **eb migrate** to package your applications.
+Microsoft Web Deploy tool (version 3.6 or later) must be installed on your source server or on the bastion host (if using the `--remote` option). This tool is used by **eb migrate** to package your applications.
@@ -76 +85,18 @@ For installation instructions, see [Installing and Configuring Web Deploy on IIS
-Your source server must have outbound internet access to AWS services.
+  * _Default workflow (without the`--remote` option)_:
+
+    * Your source server must have outbound internet access to AWS services.
+
+  * _Using the`--remote` option_:
+
+    * Your source server must have outbound internet access to AWS services.
+
+    * Configure the proper security group ingress rules that allow for an outgoing network connection from your bastion host and an incoming connection into the remote machine. Ensure the IP of the bastion host is allow-listed via TCP on port 22 to access the remote machine.
+
+    * Ensure your SSH client is installed and running on your remote machine as well as your bastion host.
+
+    * Ensure that your firewall configuration contains the appropriate rules that open up port 22 or allow connection to the client.
+
+    * Test your connection by manually SSH-ing into the remote host from the bastion host before attempting migration.
+
+
+