clickpipes imgs

Author: gingerwizard

docs/integrations/data-ingestion/clickpipes/kinesis.md

@@ -18,6 +18,8 @@ import cp_success from '@site/static/images/integrations/data-ingestion/clickpip
 import cp_remove from '@site/static/images/integrations/data-ingestion/clickpipes/cp_remove.png';
 import cp_destination from '@site/static/images/integrations/data-ingestion/clickpipes/cp_destination.png';
 import cp_overview from '@site/static/images/integrations/data-ingestion/clickpipes/cp_overview.png';
+import Image from '@theme/IdealImage';
+
 
 # Integrating Amazon Kinesis with ClickHouse Cloud
 ## Prerequisite {#prerequisite}
@@ -27,57 +29,57 @@ You have familiarized yourself with the [ClickPipes intro](./index.md) and setup
 
 1. Access the SQL Console for your ClickHouse Cloud Service.
 
-<img src={cp_service} alt="ClickPipes service" />
+<Image img={cp_service} alt="ClickPipes service" size="lg"/>
 
 2. Select the `Data Sources` button on the left-side menu and click on "Set up a ClickPipe"
 
-<img src={cp_step0} alt="Select imports" />
+<Image img={cp_step0} alt="Select imports" size="lg" />
 
 3. Select your data source.
 
-<img src={cp_step1} alt="Select data source type" />
+<Image img={cp_step1} alt="Select data source type" size="lg" />
 
 4. Fill out the form by providing your ClickPipe with a name, a description (optional), your IAM role or credentials, and other connection details.
 
-<img src={cp_step2_kinesis} alt="Fill out connection details" />
+<Image img={cp_step2_kinesis} alt="Fill out connection details" size="lg" />
 
 5. Select Kinesis Stream and starting offset. The UI will display a sample document from the selected source (Kafka topic, etc). You can also enable Enhanced Fan-out for Kinesis streams to improve the performance and stability of your ClickPipe (More information on Enhanced Fan-out can be found [here](https://aws.amazon.com/blogs/aws/kds-enhanced-fanout))
 
-<img src={cp_step3_kinesis} alt="Set data format and topic" />
+<Image img={cp_step3_kinesis} alt="Set data format and topic" size="lg" />
 
 6. In the next step, you can select whether you want to ingest data into a new ClickHouse table or reuse an existing one. Follow the instructions in the screen to modify your table name, schema, and settings. You can see a real-time preview of your changes in the sample table at the top.
 
-<img src={cp_step4a} alt="Set table, schema, and settings" />
+<Image img={cp_step4a} alt="Set table, schema, and settings" size="lg" />
 
   You can also customize the advanced settings using the controls provided
 
-<img src={cp_step4a3} alt="Set advanced controls" />
+<Image img={cp_step4a3} alt="Set advanced controls" size="lg" />
 
 7. Alternatively, you can decide to ingest your data in an existing ClickHouse table. In that case, the UI will allow you to map fields from the source to the ClickHouse fields in the selected destination table.
 
-<img src={cp_step4b} alt="Use an existing table" />
+<Image img={cp_step4b} alt="Use an existing table" size="lg" />
 
 8. Finally, you can configure permissions for the internal ClickPipes user.
 
   **Permissions:** ClickPipes will create a dedicated user for writing data into a destination table. You can select a role for this internal user using a custom role or one of the predefined role:
     - `Full access`: with the full access to the cluster. It might be useful if you use Materialized View or Dictionary with the destination table.
     - `Only destination table`: with the `INSERT` permissions to the destination table only.
 
-<img src={cp_step5} alt="Permissions" />
+<Image img={cp_step5} alt="Permissions" />
 
 9. By clicking on "Complete Setup", the system will register you ClickPipe, and you'll be able to see it listed in the summary table.
 
-<img src={cp_success} alt="Success notice" />
+<Image img={cp_success} alt="Success notice" size="sm" />
 
-<img src={cp_remove} alt="Remove notice" />
+<Image img={cp_remove} alt="Remove notice" size="lg" />
 
   The summary table provides controls to display sample data from the source or the destination table in ClickHouse
 
-<img src={cp_destination} alt="View destination" />
+<Image img={cp_destination} alt="View destination" size="lg" />
 
   As well as controls to remove the ClickPipe and display a summary of the ingest job.
 
-<img src={cp_overview} alt="View overview" />
+<Image img={cp_overview} alt="View overview" size="lg" />
 
 10. **Congratulations!** you have successfully set up your first ClickPipe. If this is a streaming ClickPipe it will be continuously running, ingesting data in real-time from your remote data source. Otherwise it will ingest the batch and complete.
 

docs/integrations/data-ingestion/clickpipes/postgres/index.md

@@ -14,6 +14,7 @@ import ssh_tunnel from '@site/static/images/integrations/data-ingestion/clickpip
 import select_replication_slot from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/select-replication-slot.jpg'
 import select_destination_db from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/select-destination-db.jpg'
 import ch_permissions from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/ch-permissions.jpg'
+import Image from '@theme/IdealImage';
 
 # Ingesting Data from Postgres to ClickHouse (using CDC)
 
@@ -61,15 +62,15 @@ Make sure you are logged in to your ClickHouse Cloud account. If you don't have
 [//]: # (   TODO update image here)
 1. In the ClickHouse Cloud Console, navigate to your ClickHouse Cloud Service.
 
-<img src={cp_service} alt="ClickPipes service" />
+<Image img={cp_service} alt="ClickPipes service" size="lg"/>
 
 2. Select the `Data Sources` button on the left-side menu and click on "Set up a ClickPipe"
 
-<img src={cp_step0} alt="Select imports" />
+<Image img={cp_step0} alt="Select imports" size="lg"/>
 
 3. Select the `Postgres CDC` tile
 
-   <img src={postgres_tile} alt="Select Postgres" />
+   <Image img={postgres_tile} alt="Select Postgres" size="lg"/>
 
 ### Adding your source Postgres database connection {#adding-your-source-postgres-database-connection}
 
@@ -82,7 +83,7 @@ Make sure you are logged in to your ClickHouse Cloud account. If you don't have
 
    :::
 
-   <img src={postgres_connection_details} alt="Fill in connection details" />
+   <Image img={postgres_connection_details} alt="Fill in connection details" size="lg"/>
 
 #### (Optional) Setting up SSH Tunneling {#optional-setting-up-ssh-tunneling}
 
@@ -92,7 +93,7 @@ You can specify SSH tunneling details if your source Postgres database is not pu
 1. Enable the "Use SSH Tunnelling" toggle.
 2. Fill in the SSH connection details.
 
-   <img src={ssh_tunnel} alt="SSH tunneling" />
+   <Image img={ssh_tunnel} alt="SSH tunneling" size="lg"/>
 
 3. To use Key-based authentication, click on "Revoke and generate key pair" to generate a new key pair and copy the generated public key to your SSH server under `~/.ssh/authorized_keys`.
 4. Click on "Verify Connection" to verify the connection.
@@ -109,7 +110,7 @@ Once the connection details are filled in, click on "Next".
 
 5. Make sure to select the replication slot from the dropdown list you created in the prerequisites step.
 
-   <img src={select_replication_slot} alt="Select replication slot" />
+   <Image img={select_replication_slot} alt="Select replication slot" size="lg"/>
 
 #### Advanced Settings {#advanced-settings}
 
@@ -126,21 +127,21 @@ You can configure the Advanced settings if needed. A brief description of each s
 
 6. Here you can select the destination database for your ClickPipe. You can either select an existing database or create a new one.
 
-   <img src={select_destination_db} alt="Select destination database" />
-   
+   <Image img={select_destination_db} alt="Select destination database" size="lg"/>
+
 7. You can select the tables you want to replicate from the source Postgres database. While selecting the tables, you can also choose to rename the tables in the destination ClickHouse database as well as exclude specific columns.
 
    :::warning
 
    If you are defining a Ordering Key in ClickHouse differently from the Primary Key in Postgres, please don’t forget to read all the [considerations](https://docs.peerdb.io/mirror/ordering-key-different) around it!
-   
+
    :::
 
 ### Review permissions and start the ClickPipe {#review-permissions-and-start-the-clickpipe}
 
 8. Select the "Full access" role from the permissions dropdown and click "Complete Setup".
 
-   <img src={ch_permissions} alt="Review permissions" />
+   <Image img={ch_permissions} alt="Review permissions" size="lg"/>
 
 ## What's next? {#whats-next}
 
@@ -153,4 +154,3 @@ Also, please refer to the [ClickPipes for Postgres FAQ](./postgres/faq) for more
 [This](https://docs.peerdb.io/bestpractices/clickhouse_datamodeling) is especially important as ClickHouse differs from Postgres, and you might encounter some surprises. This guide helps address potential pitfalls and ensures you can take full advantage of ClickHouse.
 
 :::
-

docs/integrations/data-ingestion/clickpipes/postgres/source/azure-flexible-server-postgres.md

@@ -9,6 +9,7 @@ import server_parameters from '@site/static/images/integrations/data-ingestion/c
 import wal_level from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/azure-flexible-server-postgres/wal_level.png';
 import restart from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/azure-flexible-server-postgres/restart.png';
 import firewall from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/azure-flexible-server-postgres/firewall.png';
+import Image from '@theme/IdealImage';
 
 # Azure Flexible Server for Postgres Source Setup Guide
 
@@ -20,15 +21,15 @@ ClickPipes supports Postgres version 12 and later.
 
 1. Click on the **Server parameters** section
 
-<img src={server_parameters} alt="Server Parameters in Azure Flexible Server for Postgres" />
+<Image img={server_parameters} alt="Server Parameters in Azure Flexible Server for Postgres" size="lg"/>
 
 2. Edit the `wal_level` to `logical`
 
-<img src={wal_level} alt="Change wal_level to logical in Azure Flexible Server for Postgres" />
+<Image img={wal_level} alt="Change wal_level to logical in Azure Flexible Server for Postgres" size="lg"/>
 
 3. This change would require a server restart. So restart when requested.
 
-<img src={restart} alt="Restart server after changing wal_level" />
+<Image img={restart} alt="Restart server after changing wal_level" size="lg"/>
 
 ## Creating ClickPipes User and Granting permissions {#creating-clickpipes-user-and-granting-permissions}
 
@@ -74,7 +75,7 @@ Please follow the below steps to add [ClickPipes IPs](../../index.md#list-of-sta
 1. Go to the **Networking** tab and add the [ClickPipes IPs](../../index.md#list-of-static-ips) to the Firewall
    of your Azure Flexible Server Postgres OR the Jump Server/Bastion if you are using SSH tunneling.
 
-<img src={firewall} alt="Add ClickPipes IPs to Firewall in Azure Flexible Server for Postgres" />
+<Image img={firewall} alt="Add ClickPipes IPs to Firewall in Azure Flexible Server for Postgres" size="lg"/>
 
 
 ## What's next? {#whats-next}

docs/integrations/data-ingestion/clickpipes/postgres/source/crunchy-postgres.md

@@ -7,6 +7,7 @@ title: 'Crunchy Bridge Postgres Source Setup Guide'
 
 import firewall_rules_crunchy_bridge from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/crunchy-postgres/firewall_rules_crunchy_bridge.png'
 import add_firewall_rules_crunchy_bridge from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/crunchy-postgres/add_firewall_rules_crunchy_bridge.png'
+import Image from '@theme/IdealImage';
 
 # Crunchy Bridge Postgres Source Setup Guide
 
@@ -57,9 +58,9 @@ Connect to your Crunchy Bridge Postgres through the `postgres` user and run the
 
 Safelist [ClickPipes IPs](../../index.md#list-of-static-ips) by adding the Firewall Rules in Crunchy Bridge.
 
-<img src={firewall_rules_crunchy_bridge} alt="Where to find Firewall Rules in Crunchy Bridge?"/>
+<Image size="lg" img={firewall_rules_crunchy_bridge} alt="Where to find Firewall Rules in Crunchy Bridge?"/>
 
-<img src={add_firewall_rules_crunchy_bridge} alt="Add the Firewall Rules for ClickPipes"/>
+<Image size="lg" img={add_firewall_rules_crunchy_bridge} alt="Add the Firewall Rules for ClickPipes"/>
 
 
 

docs/integrations/data-ingestion/clickpipes/postgres/source/google-cloudsql.md

@@ -13,6 +13,7 @@ import connections from '@site/static/images/integrations/data-ingestion/clickpi
 import connections_networking from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/google-cloudsql/connections_networking.png';
 import firewall1 from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/google-cloudsql/firewall1.png';
 import firewall2 from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/google-cloudsql/firewall2.png';
+import Image from '@theme/IdealImage';
 
 # Google Cloud SQL Postgres Source Setup Guide
 
@@ -33,13 +34,13 @@ Anything on or after Postgres 12
 
 1. Click on **Edit** button on the Overview page.
 
-<img src={edit_button} alt="Edit Button in Cloud SQL Postgres" />
+<Image img={edit_button} alt="Edit Button in Cloud SQL Postgres" size="lg"/>
 
 2. Go to Flags and change `cloudsql.logical_decoding` to on and `wal_sender_timeout` to 0. These changes will need restarting your Postgres server.
 
-<img src={cloudsql_logical_decoding1} alt="Change cloudsql.logical_decoding to on" />
-<img src={cloudsql_logical_decoding2} alt="Changed cloudsql.logical_decoding and wal_sender_timeout" />
-<img src={cloudsql_logical_decoding3} alt="Restart Server" />
+<Image img={cloudsql_logical_decoding1} alt="Change cloudsql.logical_decoding to on" size="lg"/>
+<Image img={cloudsql_logical_decoding2} alt="Changed cloudsql.logical_decoding and wal_sender_timeout" size="lg"/>
+<Image img={cloudsql_logical_decoding3} alt="Restart Server" size="lg"/>
 
 
 ## Creating ClickPipes User and Granting permissions {#creating-clickpipes-user-and-granting-permissions}
@@ -87,16 +88,16 @@ If your are using SSH Tunneling, then you need to add the [ClickPipes IPs](../..
 
 1. Go to **Connections** section
 
-<img src={connections} alt="Connections Section in Cloud SQL" />
+<Image img={connections} alt="Connections Section in Cloud SQL" size="lg"/>
 
 2. Go to the Networking subsection
 
-<img src={connections_networking} alt="Networking Subsection in Cloud SQL" />
+<Image img={connections_networking} alt="Networking Subsection in Cloud SQL" size="lg"/>
 
 3. Add the [public IPs of ClickPipes](../../index.md#list-of-static-ips)
 
-<img src={firewall1} alt="Add ClickPipes Networks to Firewall" />
-<img src={firewall2} alt="ClickPipes Networks Added to Firewall" />
+<Image img={firewall1} alt="Add ClickPipes Networks to Firewall" size="lg"/>
+<Image img={firewall2} alt="ClickPipes Networks Added to Firewall" size="lg"/>
 
 
 ## What's next? {#whats-next}

docs/integrations/data-ingestion/clickpipes/postgres/source/neon-postgres.md

@@ -10,6 +10,7 @@ import neon_enable_replication from '@site/static/images/integrations/data-inges
 import neon_enabled_replication from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-enabled-replication.png'
 import neon_ip_allow from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-ip-allow.png'
 import neon_conn_details from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-conn-details.png'
+import Image from '@theme/IdealImage';
 
 # Neon Postgres Source Setup Guide
 
@@ -37,19 +38,19 @@ Here, we can run the following SQL commands:
   CREATE PUBLICATION clickpipes_publication FOR ALL TABLES;
 ```
 
-<img src={neon_commands} alt="User and publication commands"/>
+<Image size="lg" img={neon_commands} alt="User and publication commands"/>
 
 Click on **Run** to have a publication and a user ready.
 
 ## Enable Logical Replication {#enable-logical-replication}
 In Neon, you can enable logical replication through the UI. This is necessary for ClickPipes's CDC to replicate data.
 Head over to the **Settings** tab and then to the **Logical Replication** section.
 
-<img src={neon_enable_replication} alt="Enable logical replication"/>
+<Image size="lg" img={neon_enable_replication} alt="Enable logical replication"/>
 
 Click on **Enable** to be all set here. You should see the below success message once you enable it.
 
-<img src={neon_enabled_replication} alt="Logical replication enabled"/>
+<Image size="lg" img={neon_enabled_replication} alt="Logical replication enabled"/>
 
 Let's verify the below settings in your Neon Postgres instance:
 ```sql
@@ -62,14 +63,14 @@ SHOW max_replication_slots; -- should be 10
 If you have Neon Enterprise plan, you can whitelist the [ClickPipes IPs](../../index.md#list-of-static-ips) to allow replication from ClickPipes to your Neon Postgres instance.
 To do this you can click on the **Settings** tab and go to the **IP Allow** section.
 
-<img src={neon_ip_allow} alt="Allow IPs screen"/>
+<Image size="lg" img={neon_ip_allow} alt="Allow IPs screen"/>
 
 ## Copy Connection Details {#copy-connection-details}
 Now that we have the user, publication ready and replication enabled, we can copy the connection details to create a new ClickPipe.
 Head over to the **Dashboard** and at the text box where it shows the connection string,
 change the view to **Parameters Only**. We will need these parameters for our next step.
 
-<img src={neon_conn_details} alt="Connection details"/>
+<Image size="lg" img={neon_conn_details} alt="Connection details"/>
 
 ## What's next? {#whats-next}
 

docs/integrations/data-ingestion/clickpipes/postgres/source/rds.md

@@ -12,6 +12,7 @@ import modify_parameter_group from '@site/static/images/integrations/data-ingest
 import reboot_rds from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/rds/reboot_rds.png';
 import security_group_in_rds_postgres from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/rds/security_group_in_rds_postgres.png';
 import edit_inbound_rules from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/rds/edit_inbound_rules.png';
+import Image from '@theme/IdealImage';
 
 # RDS Postgres Source Setup Guide
 
@@ -47,19 +48,19 @@ If not already configured, follow these steps:
     - Set `rds.logical_replication` to 1
     - Set `wal_sender_timeout` to 0
 
-<img src={parameter_group_in_blade} alt="Where to find Parameter groups in RDS?" />
+<Image img={parameter_group_in_blade} alt="Where to find Parameter groups in RDS?" size="lg" />
 
-<img src={change_rds_logical_replication} alt="Changing rds.logical_replication" />
+<Image img={change_rds_logical_replication} alt="Changing rds.logical_replication" size="lg"/>
 
-<img src={change_wal_sender_timeout} alt="Changing wal_sender_timeout" />
+<Image img={change_wal_sender_timeout} alt="Changing wal_sender_timeout" size="lg"/>
 
 2. Apply the new parameter group to your RDS Postgres database
 
-<img src={modify_parameter_group} alt="Modifying RDS Postgres with new parameter group" />
+<Image img={modify_parameter_group} alt="Modifying RDS Postgres with new parameter group" size="lg"/>
 
 3. Reboot your RDS instance to apply the changes
 
-<img src={reboot_rds} alt="Reboot RDS Postgres" />
+<Image img={reboot_rds} alt="Reboot RDS Postgres" size="lg"/>
 
 ## Configure Database User {#configure-database-user}
 
@@ -98,9 +99,9 @@ Connect to your RDS Postgres instance as an admin user and execute the following
 
 If you want to restrict traffic to your RDS instance, please add the [documented static NAT IPs](../../index.md#list-of-static-ips) to the `Inbound rules` of your RDS security group.
 
-<img src={security_group_in_rds_postgres} alt="Where to find security group in RDS Postgres?" />
+<Image img={security_group_in_rds_postgres} alt="Where to find security group in RDS Postgres?" size="lg"/>
 
-<img src={edit_inbound_rules} alt="Edit inbound rules for the above security group" />
+<Image img={edit_inbound_rules} alt="Edit inbound rules for the above security group" size="lg"/>
 
 ### Private Access via AWS PrivateLink {#private-access-via-aws-privatelink}