Skip to content

Commit 3cc2149

Browse files
committed
Add VPC endpoint for Secrets Manager if authentication is required
1 parent 3cf6c95 commit 3cc2149

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc_source/services-msk-topic-add.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This section describes how to add your Kafka cluster and topic as a function tri
1212

1313
To get Apache Kafka records from Amazon MSK brokers, Lambda must have access to the Amazon Virtual Private Cloud \(Amazon VPC\) resources associated with your MSK cluster\. To meet Amazon VPC access requirements, we recommend:
1414
+ Configuring one NAT gateway per public subnet\. For more information, see [Internet and service access for VPC\-connected functions](configuration-vpc.md#vpc-internet)\.
15-
+ Alternatively, instead of NAT gateway, deploy VPC Endpoints (PrivateLink) for Lambda and STS services.
15+
+ Alternatively, instead of NAT gateway, deploy VPC Endpoints (PrivateLink) for Lambda and STS services\. If authentication is required, then deploy also VPC Endpoint for Secrets Manager\.
1616

1717
Your Amazon VPC security groups must be configured with the following rules \(at minimum\):
1818
+ Inbound rules – Allow all traffic on all ports for the security group specified as your event source\.

0 commit comments

Comments
 (0)