For Firehose, the fact whether the current cluster is running in AWS or not is very important as it changes the cost profile of the integration.
For this reason, it would be helpful to show the user a clear indication in the onboarding flow so the user can make an informed choice.
It looks like this information is currently not available to other plugins. This likely requires changes outside of Kibana, starting here with the general requirement.
For https://github.com/elastic/observability-dev/issues/3808 , a dedicated AWS Firehose onboarding flow will be made available on stateful cloud deployments.
For Firehose, the fact whether the current cluster is running in AWS or not is very important as it changes the cost profile of the integration.
For this reason, it would be helpful to show the user a clear indication in the onboarding flow so the user can make an informed choice.
It looks like this information is currently not available to other plugins. This likely requires changes outside of Kibana, starting here with the general requirement.