Changed path templating

otterize · Mar 19, 2024 · 5fc1d78 · 5fc1d78
1 parent c6b210b
commit 5fc1d78
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/features/aws-iam/tutorials/aws-visibility.mdx b/docs/features/aws-iam/tutorials/aws-visibility.mdx
@@ -72,7 +72,7 @@ First, we will deploy two Lambda functions (`DadJokeLambdaFunction` and `Feed
 
 We can deploy the lambda functions and their required roles with the following command:
 ```bash
-curl http://localhost:3003/code-examples/aws-visibility/cloudformation.yaml -o template.yaml && \
+curl ${ABSOLUTE_URL}/code-examples/aws-visibility/cloudformation.yaml -o template.yaml && \
 aws cloudformation deploy --template-file template.yaml --stack-name OtterizeTutorialJokeTrainingStack --capabilities CAPABILITY_IAM --region 'us-west-2'
 ```
 <details>
@@ -83,7 +83,7 @@ aws cloudformation deploy --template-file template.yaml --stack-name OtterizeTut
 ```
 </details>
 
-### Deploy clusters with access to Lambda functions
+### Deploy server with access to Lambda functions
 
 Now that our Lambdas are deployed, we want to deploy our server pod within our cluster and point it to our two Lambda functions. In the commands below, we will create a configmap to hold our functions ARNs and pass the map into our deployment YAML.