Merge pull request #2730 from madeline-underwood/rabbit3

Rabbit3_next_iteration

Author: jasonrandrews

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/_index.md

@@ -15,12 +15,13 @@ prerequisites:
   - A [Google Cloud Platform (GCP)](https://cloud.google.com/free) account with billing enabled
   - Basic understanding of message queues and messaging concepts (publishers, consumers)
   - Familiarity with Linux command-line operations
+  - Basic knowledge of Python for the use case examples
 
 author: Pareena Verma
 
 ##### Tags
 skilllevels: Introductory
-subjects: Databases
+subjects: Containers and Virtualization
 cloud_service_providers: Google Cloud
 
 armips:

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/background.md

@@ -1,5 +1,5 @@
 ---
-title: Get started with RabbitMQ on Google Axion C4A
+title: Learn about RabbitMQ and Google Axion C4A
 
 weight: 2
 
@@ -22,4 +22,4 @@ RabbitMQ helps decouple application components, improve scalability, and increas
 
 RabbitMQ is widely used for **event-driven architectures**, **background job processing**, **microservices communication**, and **notification systems**. It integrates easily with many programming languages and platforms.
 
-Learn more from the [RabbitMQ official website](https://www.rabbitmq.com/) and the [official documentation](https://www.rabbitmq.com/documentation.html).
+Learn more from the [RabbitMQ website](https://www.rabbitmq.com/) and the [RabbitMQ documentation](https://www.rabbitmq.com/documentation.html).

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/baseline.md

@@ -1,14 +1,13 @@
 ---
-title: RabbitMQ Baseline Testing on Google Axion C4A Arm Virtual Machine
+title: Validate RabbitMQ installation
 weight: 6
 
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
 
 ## RabbitMQ baseline validation on GCP SUSE Arm64 VM
-This document defines a **baseline validation procedure** for RabbitMQ installed on a **Google Cloud SUSE Linux Arm64 virtual machine**.  
-The purpose of this baseline is to confirm:
+This section validates your RabbitMQ installation on the Google Cloud SUSE Linux Arm64 virtual machine by confirming:
 
 - RabbitMQ service health
 - Management plugin availability

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/firewall_setup.md

@@ -1,5 +1,5 @@
 ---
-title: Create a Firewall Rule on GCP
+title: Create a firewall rule on GCP
 weight: 3
 
 ### FIXED, DO NOT MODIFY
@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## Overview
 
-In this section, you create a Firewall Rule within Google Cloud Console to expose TCP port 15672.
+In this section, you create a firewall rule within Google Cloud Console to expose TCP port 15672.
 
 {{% notice Note %}}
 For support on GCP setup, see the Learning Path [Getting started with Google Cloud Platform](/learning-paths/servers-and-cloud-computing/csp/google/).
@@ -20,18 +20,18 @@ To expose TCP port 15672, create a firewall rule.
 
 Navigate to the [Google Cloud Console](https://console.cloud.google.com/), go to **VPC Network > Firewall**, and select **Create firewall rule**.
 
-![Screenshot of Google Cloud Console VPC Network Firewall page with Create firewall rule button highlighted alt-txt#center](images/firewall-rule.png "Create a firewall rule")
+![Screenshot showing the VPC Network Firewall page in Google Cloud Console with the Create firewall rule button highlighted alt-txt#center](images/firewall-rule.png "Create a firewall rule")
 
 Next, create the firewall rule that exposes TCP port 15672.
 Set the **Name** of the new rule to "allow-tcp-15672". Select your network that you intend to bind to your VM (default is "autoscaling-net" but your organization might have others).
 
 Set **Direction of traffic** to "Ingress". Set **Allow on match** to "Allow" and **Targets** to "Specified target tags". Enter "allow-tcp-15672" in the **Target tags** text field. Set **Source IPv4 ranges** to your IP address so that only you can access the application.
 
-![Screenshot of firewall rule configuration showing TCP port 15672 settings with allow-tcp-15672 as target tag alt-txt#center](images/network-rule.png "Creating the TCP/15672 firewall rule")
+![Screenshot showing the firewall rule configuration interface with target tag set to allow-tcp-15672 and TCP port 15672 specified in the protocols and ports section alt-txt#center](images/network-rule.png "Creating the TCP/15672 firewall rule")
 
 Finally, select **Specified protocols and ports** under the **Protocols and ports** section. Select the **TCP** checkbox, enter "15672" in the **Ports** text field, and select **Create**.
 
-![Specifying the TCP port to expose alt-txt#center](images/network-port.png "Specifying the TCP port to expose")
+![Screenshot showing the Protocols and ports section with TCP checkbox selected and port 15672 entered in the ports field alt-txt#center](images/network-port.png "Specifying the TCP port to expose")
 
 ## What you've accomplished and what's next
 

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/installation.md

@@ -7,7 +7,7 @@ layout: learningpathall
 ---
 
 ## Install RabbitMQ on GCP SUSE Arm64 VM
-This guide describes a **step-by-step installation of RabbitMQ** on a **Google Cloud Platform SUSE Linux Arm64 virtual machine**, using **RPM packages** for both **Erlang** and **RabbitMQ Server**.
+This guide describes the installation of RabbitMQ on a Google Cloud Platform SUSE Linux Arm64 virtual machine using RPM packages for both Erlang and RabbitMQ Server.
 
 RabbitMQ needs Erlang to be installed before setting up the server.
 
@@ -19,14 +19,14 @@ RabbitMQ needs Erlang to be installed before setting up the server.
 - Outbound internet access
 
 ### Refresh system repositories
-This step updates the system’s package list so the operating system knows about the latest software available from its repositories.
+Update the system's package list to get the latest available software from repositories.
 
 ```console
 sudo zypper refresh
 ```
 
 ### Install required system utilities
-You can install the basic tools needed to download and manage packages.
+Install the basic tools needed to download and manage packages.
 
 ```console
 sudo zypper install -y curl wget gnupg tar socat logrotate
@@ -123,6 +123,10 @@ sudo rabbitmqctl set_user_tags admin administrator
 sudo rabbitmqctl set_permissions -p / admin ".*" ".*" ".*"
 ```
 
+{{% notice Warning %}}
+Replace `StrongPassword123` with a strong, unique password. For production environments, use environment variables or a secrets management system instead of hardcoding passwords.
+{{% /notice %}}
+
 **Log in to Management UI**
 
 Now, test it from outside the VM. Open a web browser on your local machine (Chrome, Firefox, Edge, etc.) and enter the following URL and credentials in the address bar:
@@ -135,7 +139,7 @@ Replace `<VM_IP>` with the public IP of your GCP VM.
 
 If everything is configured correctly, you see a RabbitMQ login page in your browser that looks like this:
 
-![Screenshot of RabbitMQ management UI login page showing username and password fields alt-txt#center](images/rabbitmq.png "RabbitMQ Login page")
+![Screenshot showing the RabbitMQ management UI login interface with username and password input fields and a login button alt-txt#center](images/rabbitmq.png "RabbitMQ Login page")
 
 This confirms that your RabbitMQ management dashboard is operational.
 

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/instance.md

@@ -20,21 +20,21 @@ To create a virtual machine based on the C4A instance type, navigate to the [Goo
 
 Under **Machine configuration**, populate fields such as **Instance name**, **Region**, and **Zone**. Set **Series** to `C4A` and select `c4a-standard-4` for machine type.
 
-   ![Screenshot of Google Cloud Console machine configuration page showing C4A series selected with c4a-standard-4 machine type alt-txt#center](images/gcp-vm.png "Creating a Google Axion C4A Arm virtual machine in Google Cloud Console")
+   ![Screenshot showing the machine configuration interface in Google Cloud Console with C4A series selected and c4a-standard-4 machine type highlighted, displaying 4 vCPUs and 16 GB memory specifications alt-txt#center](images/gcp-vm.png "Creating a Google Axion C4A Arm virtual machine in Google Cloud Console")
 
 Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image. For this Learning Path, use **SUSE Linux Enterprise Server**. Select "Pay As You Go" for the license type and press **Select**.
 
 Under **Networking**, enable **Allow HTTP traffic** and add "allow-tcp-15672" as a network tag in the **Network tags** text field.
 
-![Screenshot of Google Cloud Console network configuration showing allow-tcp-15672 network tag field alt-txt#center](images/network-config.png "Adding the TCP/15672 firewall rule to the VM")
+![Screenshot showing the Networking section of the VM configuration with allow-tcp-15672 entered in the Network tags field alt-txt#center](images/network-config.png "Adding the TCP/15672 firewall rule to the VM")
 
 Select **Create** to launch the instance. Once created, you see an **SSH** option and the public IP address for your VM in the list of VM instances. Save the public IP address as you need it in the next step. Select the **SSH** option to launch an SSH shell into your VM instance.
 
-![Screenshot of Google Cloud Console VM instances list showing SSH button and external IP address column alt-txt#center](images/gcp-pubip-ssh.png "Invoke an SSH session into your running VM instance")
+![Screenshot showing the VM instances list with columns for name, zone, machine type, internal IP, external IP, and an SSH button for each instance alt-txt#center](images/gcp-pubip-ssh.png "Invoke an SSH session into your running VM instance")
 
 A window opens from your browser and you see a shell into your VM instance.
 
-![Screenshot of browser-based SSH terminal window connected to Google Cloud VM instance alt-txt#center](images/gcp-shell.png "Terminal shell in your VM instance")
+![Screenshot showing a browser-based terminal window with a command prompt connected to the Google Cloud VM via SSH alt-txt#center](images/gcp-shell.png "Terminal shell in your VM instance")
 
 ## What you've accomplished and what's next
 

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/use-case1.md

@@ -8,16 +8,16 @@ layout: learningpathall
 
 ## Event processing with topic-based routing
 
-In this use case, you implement an event-driven workflow using RabbitMQ with a **topic exchange**, a durable queue, and a Python worker consumer. You publish order events (for example, `order.created`, `order.updated`) and process them asynchronously.
+In this use case, you implement an event-driven workflow using RabbitMQ with a topic exchange, a durable queue, and a Python worker consumer. You publish order events (for example, `order.created`, `order.updated`) and process them asynchronously.
 
-This pattern is useful when you need **flexible, wildcard-based routing** (such as `order.*`) where multiple event types route to the same queue and you want producers and consumers to evolve independently.
+This pattern is useful when you need flexible, wildcard-based routing (such as `order.*`) where multiple event types route to the same queue and producers and consumers evolve independently.
 
 ### Use case overview
 
 **Scenario:**  
 An application publishes order-related events (`order.created`, `order.updated`, etc.) to RabbitMQ. A background worker consumes these events from a queue and processes them independently.
 
-The goal of this use case is to showcase how order-related events can be published to RabbitMQ and processed asynchronously by background workers without tightly coupling producers and consumers.
+This use case shows how order-related events can be published to RabbitMQ and processed asynchronously by background workers without tightly coupling producers and consumers.
 
 **Typical events include:**
 
@@ -45,7 +45,7 @@ Create a durable topic exchange to route events based on routing keys:
 
 This creates a durable topic exchange named `events` that routes messages using wildcard-based routing keys (for example, `order.*`) and survives broker restarts.
 
-The output is similar to:
+You should see:
 ```output
 exchange declared
 ```
@@ -60,7 +60,7 @@ Create a durable queue to store order-related events.
 
 This creates a durable queue for order events that guarantees messages are persisted until consumed, ensuring reliability in case of worker or broker restarts.
 
-The output is similar to:
+You should see:
 ```output
 queue declared
 ```

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/use-case2.md

@@ -1,5 +1,5 @@
 ---
-title: "RabbitMQ use case 2: WhatsApp Notification"
+title: "RabbitMQ use case 2: WhatsApp notification"
 weight: 8 
 
 ### FIXED, DO NOT MODIFY
@@ -44,7 +44,7 @@ Create the required exchange, queue, and binding for WhatsApp notifications.
 
 This creates a durable direct exchange named `notifications` that routes messages using exact routing keys.
 
-The output is similar to:
+You should see:
 ```output
 exchange declared
 ```
@@ -59,7 +59,7 @@ exchange declared
 
 This creates a durable queue to persist WhatsApp notification messages until consumed.
 
-The output is similar to:
+You should see:
 ```output
 queue declared
 ```
@@ -75,7 +75,7 @@ queue declared
 
 This links the exchange to the queue using the `whatsapp` routing key.
 
-The output is similar to:
+Expected output:
 ```output
 binding declared
 ```
@@ -265,3 +265,28 @@ You've implemented an asynchronous notification system using RabbitMQ with direc
 This pattern works well for targeted notifications (email, SMS, WhatsApp, push notifications) where routing needs to be simple and predictable. Each notification type routes to a dedicated queue using an exact-match routing key, providing reliable, guaranteed delivery.
 
 The key difference from Use Case 1 is the routing approach: Use Case 1 uses topic exchange with wildcard routing (`order.*`) for flexible event streams, while Use Case 2 uses direct exchange with exact routing (`whatsapp`) for targeted notifications.
+
+## Cleanup resources
+
+When you're finished with this Learning Path, clean up your resources to avoid unnecessary charges:
+
+**Stop RabbitMQ workers:**
+Press Ctrl+C in each terminal running a Python worker.
+
+**Delete RabbitMQ resources:**
+
+```console
+./rabbitmqadmin delete queue name=order.events
+./rabbitmqadmin delete queue name=whatsapp.notifications
+./rabbitmqadmin delete queue name=testqueue
+./rabbitmqadmin delete exchange name=events
+./rabbitmqadmin delete exchange name=notifications
+```
+
+**Delete the Google Cloud VM:**
+
+Navigate to **Compute Engine > VM Instances** in the Google Cloud Console, select your VM, and select **Delete**.
+
+**Delete the firewall rule:**
+
+Navigate to **VPC Network > Firewall**, find the `allow-tcp-15672` rule, and select **Delete**.