- Mais recentes
- Mais votos
- Mais comentários
Hello,
Please refer the below AWS documentation [+]https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect-internet-access.html
If your connector for Amazon MSK Connect needs access to the internet, we recommend that you use the following Amazon Virtual Private Cloud (VPC) settings to enable that access.
-
Configure your connector with private subnets.
-
Create a public NAT gateway or NAT instance for your VPC in a public subnet. For more information, see the Connect subnets to the internet or other VPCs using NAT devices page in the Amazon Virtual Private Cloud User Guide.
-
Allow outbound traffic from your private subnets to your NAT gateway or instance.
Workaround for public subnets- If you configure your cluster to use public subnets, you can attach an Elastic IP address (EIP) to the elastic network interface (ENI) that Amazon MSK Connect creates in your VPC. We don't recommend this method, because ENI attachments are not permanent, and the service may create or remove ENIs during maintenance or scaling operations.
For a deeper analysis into the issue and gain more insights tailored to your MSK resources, I request you to please reach out to AWS Premium Support team via a support case.
Hope the above information and documentation helps!
Reference
https://clickhouse.com/docs/en/integrations/kafka/cloud/amazon-msk
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há um ano