From b97691dd9fd82c6e9b741ffb37f816fcb6d28b59 Mon Sep 17 00:00:00 2001 From: Piyush Gupta Date: Wed, 26 Nov 2025 22:47:01 +0530 Subject: [PATCH] fix: review comments --- docs/integrations/platforms/aws/lambda.mdx | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/integrations/platforms/aws/lambda.mdx b/docs/integrations/platforms/aws/lambda.mdx index 496527651..8376e98c2 100644 --- a/docs/integrations/platforms/aws/lambda.mdx +++ b/docs/integrations/platforms/aws/lambda.mdx @@ -4,8 +4,7 @@ sidebarTitle: "AWS Lambda" description: "How to use Infisical secrets in AWS Lambda" --- -Learn how to sync Infisical secrets to AWS Lambda regardless of how you deploy your function. -This guide covers the following strategies: +Learn how to sync Infisical secrets to AWS Lambda regardless of how you deploy your function. This guide covers the following strategies: - Infisical SDKs - AWS Secrets Manager integration @@ -86,10 +85,10 @@ On success, the updated `Environment.Variables` block will be returned. Verify the values in the Lambda console or by invoking the function. - Automate this step in CI/CD. Run `infisical export` using an Infisical API - Token scoped to your project and environment, and trigger the sync as part of - your deployment workflow. Learn more about the [Infisical API - Token](/cli/commands/login#user:plain-token-output-useful-for-scripting-and-ci-cd). + Automate this step in CI/CD. Run `infisical export` using an Infisical Token + scoped to your project and environment, and trigger the sync as part of your + deployment workflow. Learn more about the [Infisical + Token](/cli/commands/export#infisical-export:infisical-token).