updating links and images in readme guides

Author: yashgulati-sudo

OnCloud/AWS/README.adoc

@@ -1,4 +1,7 @@
 = Cloudera OnCloud: AutoClouderaDeploy Provisioner
+
+:imagesdir: ../../images
+
 :toc:
 
 Author: **Kuldeep Sahu**
@@ -25,7 +28,7 @@ Infrastructure components are important and play a vital role in achieving the g
 4. `Keycloak` Server
 5. Users 
 
-image::build/images/Components.png[Components,600,400]
+image::Components.png[Components,600,400]
 
 [NOTE]
 ====
@@ -116,17 +119,17 @@ cdp configure
 
 * On the CDP Portal, click at the left bottom corner and click on Profile as shown below. 
 
-image::build/images/profile.png[profile, 120, 120]
+image::profile.png[profile, 120, 120]
 
-image::build/images/profile_1.png[profile1, 370, 193]
+image::profile_1.png[profile1, 370, 193]
 
 * Click on Generate Access Key as shown below.
 
-image::build/images/gen_access_key.png[access_key, 460, 150]
+image::gen_access_key.png[access_key, 460, 150]
 
 * Copy the values of Access Key ID and Private Key separately and keep it in a note. Or download the keys by pressing the Blue Button.
 
-image::build/images/gen_access_key_1.png[access_key1, 360, 240]
+image::gen_access_key_1.png[access_key1, 360, 240]
 
 * On your Laptop, Login to `cdp cli` as below (if not already).
 
@@ -297,7 +300,7 @@ The private key file is automatically downloaded by your browser. The base file
 
 == How To Use
 
-image::build/images/HowToUse.png[HowToUse,600,400]
+image::HowToUse.png[HowToUse,600,400]
 
 === Step 1: Get the Docker Image
 The Docker image is available at Docker Hub. Once the `Docker` is installed and ready to use, pull the **cdp-public-cloud-hol-provisioner:latest** image by executing below command.
@@ -318,7 +321,7 @@ step of this section.
 [NOTE]
 ====
 To complete this setup, you must have a registered domain on `Route53` and a corresponding `Hosted Zone` linked to it.
-If you are unsure about the steps or don’t have a registered domain or hosted zone set up on `AWS Route53`, refer to the guide link:https://github.com/cloudera/cloudera-partners/blob/main/ClouderaSetup/OnCloud/AWS/Route53.adoc[**here**] for detailed instructions.
+If you are unsure about the steps or don’t have a registered domain or hosted zone set up on `AWS Route53`, refer to the guide link:Route53.adoc[**here**] for detailed instructions.
 ====
 
 ==== A): 
@@ -691,7 +694,7 @@ e.g : If in the `configfile` the value of WORKSHOP_NAME is **accn-wrkshp** the o
 
 This file contains details about the provisioned `Keycloak` Server and the SSO URL which will be used for participants for login. It will look similar like below
 
-image::build/images/out_put_kc.png[during_process,650,300]
+image::out_put_kc.png[during_process,650,300]
 
 
 ---
@@ -881,7 +884,7 @@ The same details can be found in `<workshop_name>.txt` file present under `userc
 
 ====
 
-image::build/images/keycloak_login.png[keycloak_login,600,400]
+image::keycloak_login.png[keycloak_login,600,400]
 
 [NOTE]
 ====

OnCloud/AWS/Route53.adoc

@@ -1,4 +1,6 @@
 = Domain registration and Hosted Zone setup in AWS Route 53
+:imagesdir: ../../images
+:toc:
 
 == Prerequisites
 - An AWS account with necessary permissions to manage Route 53.
@@ -59,39 +61,39 @@ Before proceeding with domain setup in Route 53, determine which of the followin
 == Step 1: Register a New Domain in Route 53
 1. Open the **AWS Management Console** and navigate to **Route 53**.
 +
-image::build/images/image_1.png[AWS Route 53 Dashboard,550,300]
+image::image_1.png[AWS Route 53 Dashboard,550,300]
 2. In the left navigation pane, click on **Registered Domains**.
 +
-image::build/images/image_2.png[Registered Domains,250,150]
+image::image_2.png[Registered Domains,250,150]
 3. Click **Register Domain**.
 +
-image::build/images/image_3.png[Register Domain,820,180]
+image::image_3.png[Register Domain,820,180]
 4. Enter the domain name you wish to register and select a top-level domain (TLD).
 5. Click **Check** to verify availability.
 +
-image::build/images/image_4.png[Check & Select,650,420]
+image::image_4.png[Check & Select,650,420]
 6. If available, select the domain and click **Add to cart**.
 +
-image::build/images/image_5.png[Proceed to Checkout,420,400]
+image::image_5.png[Proceed to Checkout,420,400]
 7. Complete the registration details:
    - Enter contact information.
    - Select whether to enable **privacy protection**.
 8. Review the details and click **Purchase and Register**.
 +
-image::build/images/image_6.png[Purchase and Register,840,340]
+image::image_6.png[Purchase and Register,840,340]
 9. Wait for the domain registration to complete (can take a few minutes to hours).
 
 == Step 2: Create a Hosted Zone in Route 53
 1. In the Route 53 console, navigate to **Hosted Zones**.
 +
-image::build/images/image_7.png[Hosted Zones,280,200]
+image::image_7.png[Hosted Zones,280,200]
 2. Click **Create Hosted Zone**.
 +
-image::build/images/image_8.png[Create Hosted Zone,840,180]
+image::image_8.png[Create Hosted Zone,840,180]
 3. Enter your domain name in the **Domain Name** field.
 4. Set the **Type** to **Public Hosted Zone**.
 +
-image::build/images/image_9.png[Public Hosted Zone,840,550]
+image::image_9.png[Public Hosted Zone,840,550]
 5. Click **Create Hosted Zone**.
 6. Note the NS (Name Server) records displayed in the hosted zone.
 
@@ -101,7 +103,7 @@ image::build/images/image_9.png[Public Hosted Zone,840,550]
 3. Locate the **Name Servers** section.
 4. Compare the NS records listed with those in the **Hosted Zone**.
 +
-image::build/images/image_10.png[Name Servers,800,240]
+image::image_10.png[Name Servers,800,240]
 5. If they do not match:
    - Click **Edit** in the domain's NS records section.
    - Update the Name Servers to match the ones in the Hosted Zone.
@@ -114,14 +116,14 @@ image::build/images/image_10.png[Name Servers,800,240]
    - **NS (Name Server) records** – Matches the domain's NS records.
    - **SOA (Start of Authority) record** – Default record created.
 +
-image::build/images/image_11.png[NS,SOA Record,220,130]
+image::image_11.png[NS,SOA Record,220,130]
 3. If additional records are needed (e.g., A, CNAME, TXT, MX):
    - Click **Create Record**.
    - Select the record type and enter required values.
    - Click on **Create Record** to confirm the creation.
    - Once record is created, you can see it like below in the screenshot.
 +
-image::build/images/image_12.png[NS,SOA Record,220,130]
+image::image_12.png[NS,SOA Record,220,130]
 
 4. To test the records:
    - For verifying the DNS resolution and propagation, use `nslookup <domain-name>` or `dig <domain-name>` in the terminal as shown below.