Fixed GCP and AWS filename issues

Author: R-C-Stewart

…ents-defender/5-connect-aws-accounts.yml …s-defender/5-connect-amazon-accounts.ymllearn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/5-connect-aws-accounts.yml renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/5-connect-amazon-accounts.yml learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/5-connect-aws-accounts.yml renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/5-connect-amazon-accounts.yml

@@ -1,5 +1,5 @@
 ### YamlMime:ModuleUnit
-uid: learn.wwl.connect-hybrid-multicloud-environments-defender.connect-aws-accounts
+uid: learn.wwl.connect-hybrid-multicloud-environments-defender.connect-amazon-accounts
 metadata:
   title: Connect AWS accounts to Defender for Cloud
   description: Connect AWS accounts to Microsoft Defender for Cloud using the native cloud connector, configure Defender plans, deploy the CloudFormation template, and validate connector health.
@@ -11,4 +11,4 @@ metadata:
 title: Connect AWS accounts to Defender for Cloud
 durationInMinutes: 6
 content: |
-  [!include[](includes/5-connect-aws-accounts.md)]
+  [!include[](includes/5-connect-amazon-accounts.md)]

…ents-defender/6-connect-gcp-projects.yml …s-defender/6-connect-google-projects.ymllearn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/6-connect-gcp-projects.yml renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/6-connect-google-projects.yml learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/6-connect-gcp-projects.yml renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/6-connect-google-projects.yml

@@ -1,5 +1,5 @@
 ### YamlMime:ModuleUnit
-uid: learn.wwl.connect-hybrid-multicloud-environments-defender.connect-gcp-projects
+uid: learn.wwl.connect-hybrid-multicloud-environments-defender.connect-google-projects
 metadata:
   title: Connect GCP projects to Defender for Cloud
   description: Connect GCP projects and organizations to Microsoft Defender for Cloud using the native cloud connector, configure Defender plans, run the GCloud deployment script, and validate connector health.
@@ -11,4 +11,4 @@ metadata:
 title: Connect GCP projects to Defender for Cloud
 durationInMinutes: 8
 content: |
-  [!include[](includes/6-connect-gcp-projects.md)]
+  [!include[](includes/6-connect-google-projects.md)]

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/2-explore-multicloud-connectivity-model.md

@@ -38,7 +38,7 @@ The authentication flow works as follows. Defender for Cloud requests a token fr
 
 AWS performs audience, signature, thumbprint, and role-level checks before issuing credentials, ensuring only the specific Microsoft-managed application can assume the connector role.
 
-:::image type="content" source="../media/aws-auth-sequence.png" alt-text="Sequence diagram of the AWS federated auth flow: Defender for Cloud exchanges a Microsoft Entra token with AWS STS for temporary credentials, then calls AWS APIs. No credentials are stored.":::
+:::image type="content" source="../media/amazon-auth-sequence.png" alt-text="Sequence diagram of the AWS federated auth flow: Defender for Cloud exchanges a Microsoft Entra token with AWS STS for temporary credentials, then calls AWS APIs. No credentials are stored.":::
 
 This architecture means that even if an attacker gained access to the Azure environment, there are no stored AWS credentials to exfiltrate. The trust is used by the specific Microsoft-managed application, during a valid authentication transaction.
 

…ender/includes/5-connect-aws-accounts.md …er/includes/5-connect-amazon-accounts.mdlearn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/5-connect-aws-accounts.md renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/5-connect-amazon-accounts.md learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/5-connect-aws-accounts.md renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/5-connect-amazon-accounts.md

@@ -16,7 +16,7 @@ If your AWS account is already connected to **Microsoft Sentinel**, review the M
 
 ## Create the AWS connector
 
-:::image type="content" source="../media/add-aws-account-environment-settings.png" alt-text="Screenshot of the Environment Settings page in Microsoft Defender for Cloud showing the Add environment button with Amazon Web Services as an option.":::
+:::image type="content" source="../media/add-amazon-account-environment-settings.png" alt-text="Screenshot of the Environment Settings page in Microsoft Defender for Cloud showing the Add environment button with Amazon Web Services as an option.":::
 
 1. In the Azure portal, open **Microsoft Defender for Cloud** and select **Environment settings** from the left menu.
 2. Select **Add environment** > **Amazon Web Services**.
@@ -61,8 +61,6 @@ On the **Configure access** tab:
 2. Select the deployment method: **AWS CloudFormation** or **Terraform**. For most environments, CloudFormation is the standard path.
 3. Select **Download** to get the CloudFormation template. The template file is customized to the plans you selected.
 
-:::image type="content" source="../media/add-aws-account-configure-access.png" alt-text="Screenshot of the Configure access tab in the AWS connector wizard showing the CloudFormation template download option.":::
-
 ## Deploy the CloudFormation template
 
 The CloudFormation template creates the authentication resources required for Defender for Cloud to access your AWS account using federated credentials.

…ender/includes/6-connect-gcp-projects.md …er/includes/6-connect-google-projects.mdlearn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/6-connect-gcp-projects.md renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/6-connect-google-projects.md learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/6-connect-gcp-projects.md renamed to learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/6-connect-google-projects.md

@@ -19,7 +19,7 @@ Confirm these prerequisites:
 
 ## Create the GCP connector
 
-:::image type="content" source="../media/gcp-connector.png" alt-text="Screenshot of the Environment Settings Add environment menu in Microsoft Defender for Cloud with Google Cloud Platform highlighted as an option.":::
+:::image type="content" source="../media/google-connector.png" alt-text="Screenshot of the Environment Settings Add environment menu in Microsoft Defender for Cloud with Google Cloud Platform highlighted as an option.":::
 
 1. In the Azure portal, open **Microsoft Defender for Cloud** and select **Environment settings**.
 2. Select **Add environment** > **Google Cloud Platform**.
@@ -50,7 +50,7 @@ Available CWPP plans for GCP:
 | Defender for Containers | GKE clusters | No |
 | Defender for Databases | Cloud SQL instances | No |
 
-:::image type="content" source="../media/gcp-select-plans.png" alt-text="Screenshot of the Select plans tab for a GCP connector showing available Defender plan options.":::
+:::image type="content" source="../media/google-select-plans.png" alt-text="Screenshot of the Select plans tab for a GCP connector showing available Defender plan options.":::
 
 For Contoso's GCP environment, enable Defender for Servers to extend CWPP coverage to GCP Compute Engine VMs. The GCloud script generated includes Compute Engine management permissions and Google Cloud OS Config API access needed for Arc autoprovisioning.
 
@@ -65,7 +65,7 @@ For Contoso's GCP environment, enable Defender for Servers to extend CWPP covera
 > [!NOTE]
 > If this GCP connector already uses **Least privilege access** and you want to enable AI Security Posture Management (AI SPM) for AI workload visibility—including Google Vertex AI—the existing service account bindings don't include the required permissions. Rerun the updated GCloud script to add them.
 
-:::image type="content" source="../media/add-gcp-project-configure-access.png" alt-text="Screenshot of the Configure access tab for the GCP connector showing the GCloud script.":::
+:::image type="content" source="../media/add-google-project-configure-access.png" alt-text="Screenshot of the Configure access tab for the GCP connector showing the GCloud script.":::
 
 ## Run the GCloud script
 

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/index.yml

@@ -39,8 +39,8 @@ units:
 - learn.wwl.connect-hybrid-multicloud-environments-defender.explore-multicloud-connectivity-model
 - learn.wwl.connect-hybrid-multicloud-environments-defender.plan-connector-strategy
 - learn.wwl.connect-hybrid-multicloud-environments-defender.connect-on-premises-azure-arc
-- learn.wwl.connect-hybrid-multicloud-environments-defender.connect-aws-accounts
-- learn.wwl.connect-hybrid-multicloud-environments-defender.connect-gcp-projects
+- learn.wwl.connect-hybrid-multicloud-environments-defender.connect-amazon-accounts
+- learn.wwl.connect-hybrid-multicloud-environments-defender.connect-google-projects
 - learn.wwl.connect-hybrid-multicloud-environments-defender.verify-multicloud-coverage
 - learn.wwl.connect-hybrid-multicloud-environments-defender.knowledge-check
 - learn.wwl.connect-hybrid-multicloud-environments-defender.summary