From 5fc1d78fd220156866b1e7f9cccc647a7f15598e Mon Sep 17 00:00:00 2001 From: Tomer Greenwald Date: Tue, 19 Mar 2024 15:41:26 +0100 Subject: [PATCH] Changed path templating --- docs/features/aws-iam/tutorials/aws-visibility.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/aws-iam/tutorials/aws-visibility.mdx b/docs/features/aws-iam/tutorials/aws-visibility.mdx index a33b85ba8..bd47882af 100644 --- 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' ```
@@ -83,7 +83,7 @@ aws cloudformation deploy --template-file template.yaml --stack-name OtterizeTut ```
-### 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.