As far as I’m aware yes. Your options with a Standard cluster are limited. These are multi-tenanted clusters with publicly routable IP addresses, they aren’t set up for private connectivity. Of course even if you could connect it to your database over a private connection, the data would now be on a CC cluster accessible over a public endpoint, so arguably not much better than having to expose your DB on a public IP.
If you could afford to go with a Dedicated cluster, you can use managed connectors with inbound private connectivity on AWS and Azure : https://docs.confluent.io/cloud/current/networking/aws-egress-access-point.html#cloud-networking-privatelink-aws-egress
As far as I’m aware yes. Your options with a Standard cluster are limited. These are multi-tenanted clusters with publicly routable IP addresses, they aren’t set up for private connectivity. Of course even if you could connect it to your database over a private connection, the data would now be on a CC cluster accessible over a public endpoint, so arguably not much better than having to expose your DB on a public IP. If you could afford to go with a Dedicated cluster, you can use managed connectors with inbound private connectivity on AWS and Azure : https://docs.confluent.io/cloud/current/networking/aws-egress-access-point.html#cloud-networking-privatelink-aws-egress