diff --git a/manifests/modules/automation/controlplanes/ack/.workshop/cleanup.sh b/manifests/modules/automation/controlplanes/ack/.workshop/cleanup.sh
index 71a768043..80a5d5576 100755
--- a/manifests/modules/automation/controlplanes/ack/.workshop/cleanup.sh
+++ b/manifests/modules/automation/controlplanes/ack/.workshop/cleanup.sh
@@ -4,4 +4,4 @@ logmessage "Deleting resources created by ACK..."
 
 delete-all-if-crd-exists tables.dynamodb.services.k8s.aws
 
-uninstall-helm-chart ack-dynamodb ack-dynamodb-dynamodb-chart
\ No newline at end of file
+uninstall-helm-chart ack-dynamodb ack-dynamodb-chart
\ No newline at end of file
diff --git a/website/docs/automation/controlplanes/ack/introduction.md b/website/docs/automation/controlplanes/ack/introduction.md
index 0cfd7b9b5..89ce62ca6 100644
--- a/website/docs/automation/controlplanes/ack/introduction.md
+++ b/website/docs/automation/controlplanes/ack/introduction.md
@@ -7,6 +7,7 @@ Each ACK service controller is packaged into a separate container image that is
 
 In this section, since we will be working with Amazon DynamoDB ACK, we first need to install the ACK controller by using the Helm chart. As we ran the prepare-environment earlier, a role with proper permision is created for the ACK controller. Now let's create a service account and associate it with that role.
 ```bash
+$ kubectl create ns ack-dynamodb
 $ kubectl create sa ack-ddb-sa --namespace ack-dynamodb
 $ kubectl annotate serviceaccount -n  ack-dynamodb ack-ddb-sa \
   eks.amazonaws.com/role-arn=$ACK_IAM_ROLE --overwrite
@@ -16,7 +17,7 @@ Next, let us install the DynamoDB ACK controller by using the following commends
 ```bash
 $ aws ecr-public get-login-password --region us-east-1 | \
 helm registry login --username AWS --password-stdin public.ecr.aws
-$ helm install -n ack-dynamodb ack-dynamodb --create-namespace \
+$ helm install -n ack-dynamodb ack  \
   oci://public.ecr.aws/aws-controllers-k8s/dynamodb-chart \
   --version=1.1.1  \
   --set=aws.region=$AWS_REGION \