I think you might be misunderstanding the two types of connectors, in relation to Confluent Cloud, or maybe I’m misunderstanding you, but in any event…
With Confluent Cloud you can use fully-managed connectors, which run in Confluent Cloud, and self-managed connectors which run on a connect worker that you are hosting, either locally, or in a self-managed cloud environment (eg. on an EC2 instance).
The two connectors you are referring to are both self-managed, at least for now. So you will need to run a Connect cluster and configure workers for these connectors. The two easiest ways to do this are Docker, which Robin shows, or Confluent Platform. But however you do it, you do need to have Kafka Connect running somewhere and that’s where you’d configure your workers.
The S3 sink connector is fairly well documented at: Amazon S3 Sink Connector for Confluent Platform | Confluent Documentation
There is a section on that page that links to the full set of config settings, but here’s the link to save some time: Amazon S3 Sink Connector Configuration Properties | Confluent Documentation
The settings and other information on using the New Relic connector can be found on github. It’s a bit tricky since it’s not in the main readme for the repo, but down a level. Here’s the link:
Let me know if that clears things up at all.