Working on a task to setup Elastic Cloud on AWS and some of the beats (meticbeat, heartbeat, filebeat, and packetbeat) are on AWS some of the beats need to be on Azure and GCP. In this situation,should we put logstash on each cloud environment (AWS, Azure or GCP) and point it to Elastic Cloud on AWS while the beats on the local cloud to send data via the local logstash to Elasticsearch on Elastic Cloud or using on logstash on AWS and all beats in different clouds connect to the logstash on AWS?
I didn't understand you problem very well, but you can configure the beat's ouput do send directly to deployment on Elastic Cloud.
A doubt: Have you been trying to send the same beat's log to multiple environment? Is it?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.