aws_role_arn
<deployment_name>:<base64_info>
. Once decoded, the base64_info
string has the format <deployment_region>lt;elasticsearch_hostname>lt;kibana_hostname>
.The parameters index and type can be confusing if you are new to Elastic, if you have used a common relational database before, they can be compared to the database and table concepts. Also see the FAQ below​
Id_Key
or Generate_ID
is required in update, and upsert scenario.Rejecting mapping update to [search] as the final mapping would have more than 1 type
flb_type
to _doc
, which matches the recommendation from Elasticsearch from version 6.2 forwards (see commit with rationale). This doesn't work in Elasticsearch versions 5.6 through 6.1 (see Elasticsearch discussion and fix). Ensure you set an explicit map (such as doc
or flb_type
) in the configuration, as seen on the last line:Port
is set to 443
, tls
is enabled, and AWS_Region
is set.cloud_id
and the cloud_auth
settings. cloud_auth
uses the elastic
user and password provided when the cluster was created, for details refer to the Cloud ID usage page.create
method (instead of index
) for data submission. This makes Fluent Bit compatible with Datastream introduced in Elasticsearch 7.9.action_request_validation_exception
errors on your pipeline with Fluent Bit >= v1.8.2, you can fix it up by turning on Generate_ID
as follows:Suppress_Type_Name On
as indicated above.