Merge pull request #279788 from zioproto/fix/deploy-edw-workload

Fix deploy instructions

Author: prmerger-automator[bot]

articles/aks/eks-edw-deploy.md

@@ -33,7 +33,9 @@ In this article, you will deploy an [AWS EDW workload][eks-edw-overview] to Azur
 
 ## EDW workload deployment script
 
-You use the `deploy.sh` script in the `deployment` directory of the [GitHub repository][github-repo] to deploy the application to Azure.
+Review the environment variables in the file `deployment/environmentVariables.sh` and then you use the
+`deploy.sh` script in the `deployment/infra/` directory of the [GitHub repository][github-repo] to deploy
+the application to Azure.
 
 The script first checks that all of the [prerequisite tools][prerequisites] are installed. If not, the script terminates and displays an error message letting you know which prerequisites are missing. If this happens, review the prerequisites, install any missing tools, and then run the script again. The [Node autoprovisioning (NAP) for AKS][nap-aks] feature flag must be registered on your Azure subscription. If it isn't already registered, the script executes an Azure CLI command to register the feature flag.
 
@@ -68,15 +70,6 @@ The deployment script creates the following Azure resources:
 - **Workload identity**: The script assigns the **Storage Queue Data Contributor** and **Storage Table Data Contributor** roles to provide role-based access control (RBAC) access to this managed identity, which is associated with the Kubernetes service account used as the identity for pods on which the consumer app containers are deployed.
 - **Two federated credentials**:  One credential enables the managed identity to implement pod identity, and the other credential is used for the KEDA operator service account to provide access to the KEDA scaler to gather the metrics needed to control pod autoscaling.
 
-## Deploy the EDW workload to Azure
-
-- Make sure you're in the `deployment` directory of the project and deploy the workload using the following commands:
-
-    ```bash
-    cd deployment
-    ./deploy.sh
-    ```
-
 ## Validate deployment and run the workload
 
 Once the deployment script completes, you can deploy the workload on the AKS cluster.
@@ -239,7 +232,7 @@ You can use various tools to verify the operation of apps deployed to AKS, inclu
       minReplicaCount: 0  # We don't want pods if the queue is empty nginx-deployment
       maxReplicaCount: 15 # We don't want to have more than 15 replicas
       pollingInterval: 30 # How frequently we should go for metrics (in seconds)
-      cooldownPeriod:  10 # How many seconds should we wait for downscale  
+      cooldownPeriod:  10 # How many seconds should we wait for downscale
       triggers:
       - type: azure-queue
         authenticationRef: