From 4e7982a5b707c1b1bce59a84f249ef454bb952d0 Mon Sep 17 00:00:00 2001 From: aahel Date: Tue, 5 Mar 2024 22:53:50 +0530 Subject: [PATCH] fix lambda registrator module doc link (#20796) --- website/content/docs/lambda/registration/automate.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/lambda/registration/automate.mdx b/website/content/docs/lambda/registration/automate.mdx index 781d37318a..62f4aa700d 100644 --- a/website/content/docs/lambda/registration/automate.mdx +++ b/website/content/docs/lambda/registration/automate.mdx @@ -134,7 +134,7 @@ The registrator also requires the following IAM permissions to access the parame ## Deploy the Lambda registrator -1. Create a Terraform configuration and specify the `lambda-registrator` module. In the following example, the Lambda registrator is deployed to `https://consul.example.com:8501`. Refer to [the Lambda registrator module documentation](https://registry.terraform.io/modules/hashicorp/consul-lambda-registrator/aws/0.1.0-beta1/submodules/lambda-registrator) for additional usage information: +1. Create a Terraform configuration and specify the `lambda-registrator` module. In the following example, the Lambda registrator is deployed to `https://consul.example.com:8501`. Refer to [the Lambda registrator module documentation](https://registry.terraform.io/modules/hashicorp/consul-lambda-registrator/aws/0.1.0-beta5/submodules/lambda-registrator) for additional usage information: ```hcl module "lambda-registrator" { source = "hashicorp/consul-lambda/consul-lambda-registrator"