From 247bd576f3fe618f1b0b03fbc79a6655dabd4aed Mon Sep 17 00:00:00 2001 From: Philipp Muens Date: Fri, 15 Feb 2019 15:42:27 +0100 Subject: [PATCH] Fix path of link --- docs/providers/aws/events/s3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/providers/aws/events/s3.md b/docs/providers/aws/events/s3.md index f41869738..5eb8ea25d 100644 --- a/docs/providers/aws/events/s3.md +++ b/docs/providers/aws/events/s3.md @@ -77,7 +77,7 @@ functions: ## Custom bucket configuration If you need to configure the bucket itself, you'll need to create the bucket and the Lambda Permission manually in -the Resources section while paying attention to some of the logical IDs. This relies on the Serverless naming convention. See the [Serverless Resource Reference](../../guide/resources/#aws-cloudformation-resource-reference) for details. These are the logical IDs that require your attention: +the Resources section while paying attention to some of the logical IDs. This relies on the Serverless naming convention. See the [Serverless Resource Reference](../guide/resources/#aws-cloudformation-resource-reference) for details. These are the logical IDs that require your attention: - The logical ID of the custom bucket in the Resources section needs to match the bucket name in the S3 event after the Serverless naming convention is applied to it. - The Lambda Permission's logical ID needs to match the Serverless naming convention for Lambda Permissions for S3 events. - The `FunctionName` in the Lambda Permission configuration needs to match the logical ID generated for the target Lambda function as determined by the Serverless naming convention.