linode · jddocs · Oct 2, 2023 · Oct 2, 2023
diff --git a/docs/products/compute/compute-instances/guides/failover/index.md b/docs/products/compute/compute-instances/guides/failover/index.md
@@ -30,6 +30,7 @@ Within Linode's platform, failover is configured by first enabling [IP Sharing](
 | Data center | IP Sharing support | Failover method | Software | ID |
 | -- | -- | -- | -- | -- |
 | Atlanta, GA (USA) | *Undergoing network upgrades* | - | - | 4 |
+| Chennai (India) | **Supported** | BGP-based (new) | [lelastic](/docs/products/compute/compute-instances/guides/failover/#configure-failover) / [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) | 25 |
 | Chicago, IL (USA) | **Supported** | BGP-based (new) | [lelastic](/docs/products/compute/compute-instances/guides/failover/#configure-failover) / [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) | 18 |
 | Dallas, TX (USA) | **Supported** | BGP-based (new) | [lelastic](/docs/products/compute/compute-instances/guides/failover/#configure-failover) / [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) | 2 |
 | Frankfurt (Germany) | **Supported** | BGP-based (new) | [lelastic](/docs/products/compute/compute-instances/guides/failover/#configure-failover) / [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) | 10 |

diff --git a/docs/products/compute/compute-instances/guides/lish/index.md b/docs/products/compute/compute-instances/guides/lish/index.md
@@ -208,6 +208,20 @@ If you are having issues accessing Lish, Weblish, or Glish, you may be blocked b
 
 -   **Weblish/Glish Gateway:** `us-southeast.webconsole.linode.com`
 
+#### Chennai (India)
+
+-   **Lish SSH Gateway:** `lish-in-maa.linode.com`
+
+    {{< note type="secondary" title="Lish SSH Gateway Fingerprints" isCollapsible=true >}}
+    ```command
+    RSA 3072 SHA256:kXCaKnn1nVlVEC5SCuez6FApcXr/2UUiaSANUy0rlLI lish-in-maa.linode.com
+    ECDSA 256 SHA256:Jj+pb1AkDdKs77o6ozgkOk83rg7auLSOQrnebE8n91o lish-in-maa.linode.com
+    ED25519 256 SHA256:v1KaIB0togivalP7OVvlrLpu/y80qsm5cj50qclTWc0 lish-in-maa.linode.com
+    ```
+    {{< /note >}}
+
+-   **Weblish/Glish Gateway:** `in-maa.webconsole.linode.com`
+
 #### Chicago, IL (USA)
 
 -   **Lish SSH Gateway:** `lish-us-ord.linode.com`

diff --git a/docs/products/compute/compute-instances/guides/metadata/index.md b/docs/products/compute/compute-instances/guides/metadata/index.md
@@ -3,7 +3,7 @@ title: "Overview of the Metadata Service"
 description: "Learn how to automate server provisioning on the Linode platform through the new Metadata service and cloud-init."
 keywords: ["user data", "metadata", "cloud-init", "cloudinit"]
 published: 2023-07-25
-modified: 2023-09-26
+modified: 2023-09-29
 modified_by:
   name: Linode
 authors: ["Linode"]
@@ -34,7 +34,7 @@ Similar to Metadata, Linode's [StackScripts](/docs/products/tools/stackscripts/)
 
 Akamai's Metadata service is available in select data centers. Additionally, user data and cloud-init integration is currently only supported in a few distribution images. Supported data centers and distributions are listed below:
 
--   **Data centers:** Chicago (USA), Milan (Italy), Osaka (Japan), Paris (France), Seattle (USA), Stockholm (Sweden), and Washington DC (USA)
+-   **Data centers:** Chennai (India), Chicago (USA), Milan (Italy), Osaka (Japan), Paris (France), Seattle (USA), Stockholm (Sweden), and Washington DC (USA)
 
 -   **Distributions:** Ubuntu 22.04 LTS, Ubuntu 20.04 LTS, Debian 11
 

diff --git a/docs/products/compute/compute-instances/plans/premium/index.md b/docs/products/compute/compute-instances/plans/premium/index.md
@@ -39,6 +39,7 @@ Premium Compute Instances are currently available in select data centers.
 | Data center | Status |
 | -- | -- |
 | Atlanta (Georgia, USA) | *Not available* |
+| **Chennai (India)** | **Available** |
 | **Chicago (Illinois, USA)** | **Available** |
 | Dallas (Texas, USA) | *Not available* |
 | Frankfurt (Germany) | *Not available* |

diff --git a/docs/products/networking/vlans/_index.md b/docs/products/networking/vlans/_index.md
@@ -40,6 +40,7 @@ Since VLANs operate on layer 2 of the OSI networking stack, you can use is as pa
 | Data center | Status |
 | -- | -- |
 | **Atlanta (Georgia, USA)** | **Available** |
+| **Chennai (India)** | **Available** |
 | **Chicago (Illinois, USA)** | **Available** |
 | Dallas (Texas, USA) | Not yet available |
 | **Frankfurt (Germany)** | **Available** |

diff --git a/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md b/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md
@@ -24,7 +24,7 @@ Capacity in beta data centers may be limited as we continue to scale up resource
 | Data Center | Status | Region ID |
 | -- | -- | -- |
 | Amsterdam, Netherlands | *Limited beta* | `nl-ams` |
-| Chennai, India | *Limited beta* | `in-maa` |
+| Chennai, India | **Now available to all customers** | `in-maa` |
 | Chicago, IL, USA | **Now available to all customers** | `us-ord` |
 | Jakarta, Indonesia | *Limited beta* | `id-cgk` |
 | Los Angeles, CA, USA | *Limited beta* | `us-lax` |

diff --git a/docs/products/platform/get-started/guides/choose-a-data-center/index.md b/docs/products/platform/get-started/guides/choose-a-data-center/index.md
@@ -11,6 +11,10 @@ aliases: ['/platform/how-to-choose-a-data-center/','/guides/how-to-choose-a-data
 authors: ["Linode"]
 ---
 
+{{< note >}}
+Our **Chennai** and **Mumbai** core sites are optimized for the India market. For workloads that currently serve or intend to serve the wider Asia-Pacific region and for communication with Akamai core sites outside of India, we recommend deploying resources in our Singapore or Sydney data centers.
+{{< /note >}}
+
 Deploying your Compute Instance to a geographically advantageous data center can make a big difference in connection speeds to your server. Ideally, your site or application should be served from multiple points around the world, with requests sent to the appropriate region based on client geolocation. On a smaller scale, deploying a Compute Instance in the data center nearest to you will make it easier to work with than one in a different region or continent.
 
 There are many things that can affect network congestion, connection speeds, and throughput, so you should never interpret one reading as the sole data point. Always perform tests in multiples of three or five for an average, and on both weekend and weekdays for the most accurate information.
@@ -25,6 +29,7 @@ An important consideration when choosing a data center is the availability of sp
 | Region | [Dedicated Compute](/docs/products/compute/compute-instances/plans/dedicated-cpu/) | [Shared Compute](/docs/products/compute/compute-instances/plans/shared-cpu/) | [GPUs](/docs/products/compute/compute-instances/plans/gpu/) | [Premium Compute](/docs/products/compute/compute-instances/plans/premium/) | [Kubernetes](/docs/products/compute/kubernetes/) | [Managed DB](/docs/products/databases/managed-databases/) | [Cloud Firewall](/docs/products/networking/cloud-firewall/) | [DDoS Protection](/docs/products/networking/ddos-protection/) | [NodeBalancers](/docs/products/networking/nodebalancers/) | [VLANs](/docs/products/networking/vlans/) | [Backups](/docs/products/storage/backups/) | [Block Storage](/docs/products/storage/block-storage/) | [Object Storage](/docs/products/storage/object-storage/) | [Images](/docs/products/tools/images/) |
 | --- | :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:| :---:|
 | Atlanta        | ✔ | ✔ | ✔ |   | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
+| Chennai        | ✔ | ✔ |   | ✔ | ✔ |   | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔† | ✔ |
 | Chicago        | ✔ | ✔ |   | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔† | ✔ |
 | Dallas         | ✔ | ✔ |   |   | ✔ | ✔ | ✔ | ✔ | ✔ |   | ✔ | ✔ |   | ✔ |
 | Frankfurt      | ✔ | ✔ | ✔ |   | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |

diff --git a/docs/products/storage/object-storage/_index.md b/docs/products/storage/object-storage/_index.md
@@ -38,6 +38,7 @@ Object Storage is available within the following data centers. For a full list o
 | Data Center | Cluster ID |
 | -- | -- | -- | -- |
 | Atlanta, GA (USA) | `us-southeast-1` |
+| Chennai (India)\* | `in-maa-1` |
 | Chicago, IL (USA)\* | `us-ord-1` |
 | Frankfurt (Germany) | `eu-central-1` |
 | Milan (Italy)\* | `it-mil-1` |
@@ -77,6 +78,7 @@ The tables below outline Object Storage limits. Most of the limits apply **per r
 | Data Center | Max Storage<br><small>per account, per region</small> | Max # of objects<br><small>per account, per region</small> |
 | -- | -- | -- |
 | Atlanta, GA (USA) | 5 TB | 50 million |
+| Chennai (India) | 5 TB<br><small>Up to 1,000 TB by request</small> | 50 million<br><small>Up to 1 billion by request</small> |
 | Chicago, IL (USA) | 5 TB<br><small>Up to 1,000 TB by request</small> | 50 million<br><small>Up to 1 billion by request</small> |
 | Frankfurt (Germany) | 5 TB | 50 million |
 | Milan (Italy) | 5 TB<br><small>Up to 1,000 TB by request</small> | 50 million<br><small>Up to 1 billion by request</small> |

diff --git a/docs/products/storage/object-storage/guides/urls/index.md b/docs/products/storage/object-storage/guides/urls/index.md
@@ -34,6 +34,7 @@ The cluster URL for Object Storage is unique to each data center. This URL can b
 | Data Center | Cluster ID | Cluster URL |
 | -- | -- | -- |
 | Atlanta, GA (USA) | `us-southeast-1` | `https://us-southeast-1.linodeobjects.com` |
+| Chennai (India) | `in-maa-1` | `https://in-maa-1.linodeobjects.com` |
 | Chicago, IL (USA) | `us-ord-1` | `https://us-ord-1.linodeobjects.com` |
 | Frankfurt (Germany) | `eu-central-1` | `https://eu-central-1.linodeobjects.com` |
 | Milan (Italy) | `it-mil-1` | `https://it-mil-1.linodeobjects.com` |