Amazon Elasticsearch
Amazon Elasticsearch output plugin for Fluentd
Overview
More info at https://github.com/atomita/fluent-plugin-aws-elasticsearch-service
Example output configurations
spec:
awsElasticsearch:
logstash_format: true
include_tag_key: true
tag_key: "@log_name"
flush_interval: 1s
endpoint:
url: https://CLUSTER_ENDPOINT_URL
region: eu-west-1
access_key_id:
value: aws-key
secret_access_key:
value: aws_secret
Configuration
Amazon Elasticsearch
Send your logs to a Amazon Elasticsearch Service
flush_interval (string, optional)
flush_interval
Default: -
endpoint (*EndpointCredentials, optional)
AWS Endpoint Credentials
Default: -
format (*Format, optional)
Default: -
buffer (*Buffer, optional)
Default: -
(*ElasticsearchOutput, optional)
ElasticSearch
Default: -
Endpoint Credentials
endpoint
region (string, optional)
AWS region. It should be in form like us-east-1, us-west-2. Default nil, which means try to find from environment variable AWS_REGION.
Default: -
url (string, optional)
AWS connection url.
Default: -
access_key_id (*secret.Secret, optional)
AWS access key id. This parameter is required when your agent is not running on EC2 instance with an IAM Role.
Default: -
secret_access_key (*secret.Secret, optional)
AWS secret key. This parameter is required when your agent is not running on EC2 instance with an IAM Role.
Default: -
assume_role_arn (*secret.Secret, optional)
Typically, you can use AssumeRole for cross-account access or federation.
Default: -
ecs_container_credentials_relative_uri (*secret.Secret, optional)
Set with AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable value
Default: -
assume_role_session_name (*secret.Secret, optional)
AssumeRoleWithWebIdentity https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html
Default: -
assume_role_web_identity_token_file (*secret.Secret, optional)
AssumeRoleWithWebIdentity https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html
Default: -
sts_credentials_region (*secret.Secret, optional)
By default, the AWS Security Token Service (AWS STS) is available as a global service, and all AWS STS requests go to a single endpoint at https://sts.amazonaws.com. AWS recommends using Regional AWS STS endpoints instead of the global endpoint to reduce latency, build in redundancy, and increase session token validity. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html
Default: -