Update wording on msk connect networking setup details

docs/en/integrations/data-ingestion/kafka/msk/index.md

@@ -64,7 +64,7 @@ You can find more details (both implementation and other considerations) in the
 
 ## Notes on Networking for MSK Connect
 
-In order for MSK Connect to connect to ClickHouse, your MSK cluster must be in a private subnet with a Private NAT connected for internet access. Instructions on how to set this up are provided below.
+In order for MSK Connect to connect to ClickHouse, we recommend your MSK cluster to be in a private subnet with a Private NAT connected for internet access. Instructions on how to set this up are provided below. Note that public subnets are supported but not recommended due to the need to constantly assign an Elastic IP address to your ENI, [AWS provides more details here](https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect-internet-access.html)
 
 1. **Create a Private Subnet:** Create a new subnet within your VPC, designating it as a private subnet. This subnet should not have direct access to the internet.
 1. **Create a NAT Gateway:** Create a NAT gateway in a public subnet of your VPC. The NAT gateway enables instances in your private subnet to connect to the internet or other AWS services, but prevents the internet from initiating a connection with those instances.