diff --git a/website/content/docs/ecs/get-started/install.mdx b/website/content/docs/ecs/get-started/install.mdx
index a656f47dbd..b6d5230636 100644
--- a/website/content/docs/ecs/get-started/install.mdx
+++ b/website/content/docs/ecs/get-started/install.mdx
@@ -49,7 +49,7 @@ module "my_task" {
   ]
 
   port       = "9090"
-  retry_join = "<address of the Consul server>"
+  retry_join = ["<address of the Consul server>"]
 }
 ```
 
@@ -63,7 +63,7 @@ however there are some important inputs worth highlighting:
 - `port` is the port that your application listens on. This should be set to a
   string, not an integer, i.e. `port = "9090"`, not `port = 9090`.
 - `retry_join` is passed to the [`-retry-join`](/docs/agent/options#_retry_join) option for the Consul agent. This tells
-  the agent the location of your Consul server so that it can join the Consul cluster.
+  the agent the location of your Consul servers so that it can join the Consul cluster.
 
 -> **NOTE:** If your tasks run in a public subnet, they must have `assign_public_ip = true`
 in their [`network_configuration`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecs_service#network_configuration) block so that ECS can pull the Docker images.
diff --git a/website/content/docs/ecs/get-started/migrate-existing-tasks.mdx b/website/content/docs/ecs/get-started/migrate-existing-tasks.mdx
index 717cbed9c3..aedca03911 100644
--- a/website/content/docs/ecs/get-started/migrate-existing-tasks.mdx
+++ b/website/content/docs/ecs/get-started/migrate-existing-tasks.mdx
@@ -91,7 +91,7 @@ module "my_task" {
   ]
 
   port       = "9090"
-  retry_join = "<address of the Consul server>"
+  retry_join = ["<address of the Consul server>"]
 }
 ```
 
diff --git a/website/content/docs/ecs/index.mdx b/website/content/docs/ecs/index.mdx
index ee10784774..f0f483aefc 100644
--- a/website/content/docs/ecs/index.mdx
+++ b/website/content/docs/ecs/index.mdx
@@ -8,11 +8,7 @@ description: >-
 
 # AWS ECS
 
--> **Beta:** This functionality is currently in beta and is
-not recommended for use in production environments. Refer to the [consul-ecs project road map](https://github.com/hashicorp/consul-ecs/projects/1) for information about upcoming features and enhancements.
-
-Consul can be deployed on [AWS ECS](https://aws.amazon.com/ecs/) (Elastic Container Service) using our official
-Terraform modules.
+Consul can be deployed on [AWS ECS](https://aws.amazon.com/ecs/) (Elastic Container Service) using our official Terraform modules.
 
 ![Consul on ECS Architecture](/img/consul-ecs-arch.png)
 
@@ -22,12 +18,13 @@ Using Consul on AWS ECS enables you to add your ECS tasks to the service mesh an
 take advantage of features such as zero-trust-security, intentions, observability,
 traffic policy, and more.
 
-## Example Installation
+## Getting Started
 
-See our [Example Installation](https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/examples/dev-server-fargate)
-to learn how to install Consul on an example ECS cluster along with example service mesh applications.
+There are several ways to get started with Consul with ECS.
 
-## Install
+* The [Serverless Consul service mesh with ECS and HCP](https://learn.hashicorp.com/tutorials/cloud/consul-ecs-hcp?in=consul/cloud-integrations) learn guide shows how to use Terraform to run Consul service mesh applications on ECS with managed Consul servers running in HashiCorp Cloud Platform (HCP).
+* The [Service mesh with ECS and Consul on EC2](https://learn.hashicorp.com/tutorials/consul/consul-ecs-ec2?in=consul/cloud-integrations) learn guide shows shows how to use Terraform to run consul service mesh applications on ECS with Consul servers running on EC2 instances.
+* The [Consul With Dev Server on Fargate](https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/examples/dev-server-fargate) example installation deploys a sample service mesh application in ECS using the Fargate launch type.
+* The [Consul With Dev Server on EC2](https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/examples/dev-server-ec2) example installation deploys a sample service mesh applciation in ECS using the ECS launch type.
 
-See our full [Install Guide](/docs/ecs/get-started/install) when you're ready to install Consul
-on an existing ECS cluster and add existing tasks to the service mesh.
+See the [Requirements](/docs/ecs/get-started/requirements) and the full [Install Guide](/docs/ecs/get-started/install) when you're ready to install Consul on an existing ECS cluster and add existing tasks to the service mesh.
diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json
index 86e6efc0a5..b16146b73c 100644
--- a/website/data/docs-nav-data.json
+++ b/website/data/docs-nav-data.json
@@ -560,7 +560,7 @@
     ]
   },
   {
-    "title": "AWS ECS <sup>BETA</sup>",
+    "title": "AWS ECS",
     "routes": [
       {
         "title": "Overview",
@@ -569,14 +569,6 @@
       {
         "title": "Get Started",
         "routes": [
-          {
-            "title": "Example Installation on ECS Fargate",
-            "href": "https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/examples/dev-server-fargate"
-          },
-          {
-            "title": "Example Installation on ECS EC2",
-            "href": "https://registry.terraform.io/modules/hashicorp/consul-ecs/aws/latest/examples/dev-server-ec2"
-          },
           {
             "title": "Requirements",
             "path": "ecs/get-started/requirements"