diff --git a/content/integrate/redis-data-integration/data-pipelines/data-pipelines.md b/content/integrate/redis-data-integration/data-pipelines/data-pipelines.md
index b5d15e7a30..547f7860e4 100644
--- a/content/integrate/redis-data-integration/data-pipelines/data-pipelines.md
+++ b/content/integrate/redis-data-integration/data-pipelines/data-pipelines.md
@@ -158,11 +158,9 @@ configuration contains the following data:
     (the default is to include all tables if you don't specify a query here).
   - `columns`: A list of the columns you are interested in (the default is to
     include all columns if you don't supply a list)
-  - `keys`: A list of primary keys, one for each table. If the table doesn't
-    have a column with a
-    [`PRIMARY KEY`](https://www.w3schools.com/sql/sql_primarykey.asp) or
-    [`UNIQUE`](https://www.w3schools.com/sql/sql_unique.asp) constraint then you can
-    supply a unique composite key.
+  - `keys`: A list of columns to create a composite key if your table
+    doesn't already have a [`PRIMARY KEY`](https://www.w3schools.com/sql/sql_primarykey.asp) or
+    [`UNIQUE`](https://www.w3schools.com/sql/sql_unique.asp) constraint.
 - `advanced`: These optional properties configure other Debezium-specific features.
   The available sub-sections are:
   - `sink`: All advanced properties for writing to RDI (TLS, memory threshold, etc).
diff --git a/content/integrate/redis-data-integration/installation/install-vm.md b/content/integrate/redis-data-integration/installation/install-vm.md
index 2b8caa7f43..5287619c2b 100644
--- a/content/integrate/redis-data-integration/installation/install-vm.md
+++ b/content/integrate/redis-data-integration/installation/install-vm.md
@@ -210,6 +210,31 @@ sudo service k3s restart
 
 After the installation is finished, RDI is ready for use.
 
+## Supply cloud DNS information
+
+{{< note >}}This section is only relevant if you are installing RDI
+on VMs in a cloud environment.
+{{< /note >}}
+
+If you are using [Amazon Route 53](https://aws.amazon.com/route53/),
+[Google Cloud DNS](https://cloud.google.com/dns?hl=en), or
+[Azure DNS](https://azure.microsoft.com/en-gb/products/dns)
+then you must supply the installer with the nameserver IP address
+during installation (or with the `nameservers` property if you are
+using [Silent installation](#silent-installation)). The table below
+shows the appropriate IP address for each platform:
+
+| Platform | Nameserver IP |
+| :-- | :-- |
+| [Amazon Route 53](https://aws.amazon.com/route53/) | 169.254.169.253 |
+| [Google Cloud DNS](https://cloud.google.com/dns?hl=en) | 169.254.169.254 |
+| [Azure DNS](https://azure.microsoft.com/en-gb/products/dns) | 168.63.129.16 |
+
+If you are planning to use Route 53, you should first check that your VPC
+allows it. See
+[DNS attributes in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/AmazonDNS-concepts.html#vpc-dns-support)
+in the Amazon docs for more information.
+
 ## "Silent" installation
 
 You can use the