AWS lambda medium security documentation change
Summary
Identical security group configuration updates as in Kafka documentation - cluster port references and outbound rule modifications
Security assessment
Same security-focused updates as Kafka counterpart, aligning MSK configuration with improved security practices for network access controls.
Diff
diff --git a/lambda/latest/dg/with-msk-configure.md b/lambda/latest/dg/with-msk-configure.md index 0603d5acc..67f18bfde 100644 --- a/lambda/latest/dg/with-msk-configure.md +++ b/lambda/latest/dg/with-msk-configure.md @@ -383 +383 @@ Configure the security groups for the Amazon VPC containing your cluster. By def - * Inbound rules – Allow all traffic on the default broker port for the security group associated with your event source. Alternatively, you can use a self-referencing security group rule to allow access from instances within the same security group. + * Inbound rules – Allow all traffic on the default cluster port for the security group associated with your event source. @@ -385 +385 @@ Configure the security groups for the Amazon VPC containing your cluster. By def - * Outbound rules – Allow all traffic on port `443` for external destinations if your function needs to communicate with AWS services. Alternatively, you can also use a self-referencing security group rule to limit access to the broker if you don't need to communicate with other AWS services. + * Outbound rules – Allow all traffic on port `443` for all destinations. Allow all traffic on the default cluster port for the security group associated with your event source.