Error in connecting Filebeat oss 7.7.0 to S3

Hi All,

I am having a big issue on configuring filebeat with S3 logs as type.

Let me explain our Flow.
I am not using Logstash.

I am using Filebeat oss-7.x version in elastic.repo ( 7.7.0 version is installed)
Elastic search and Kibana is installed in AWS - Version is 7.4.2

When i install filebeat (7.7.0 version) with oss version and configure the type as s3 i get the following error :

-- instance/beat.go:932 Exiting: Error while initializing input: Error creating input. **No such input type exist: 's3'**

But when i install same filebeat (7.7.0) without oss version and configire type s3 i do not get any error.. i cannot use the licensed one hence i have to use the oss version.
I want to connect the beats to my s3. i have followed the elastic website to configure s3.

Below i have put my filebeat.yml file and also elastic.repo file which is configured .
Please help me if there is any error in the yml file or repo file which is not allowing the connection to s3

filebeat.yml
###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

#=========================== Filebeat inputs =============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

- type: s3
  enabled: true
  queue_url: https://sqs.ap-south-1.amazonaws.com/xxxx/xxxx
  access_key_id: A-----------XXX----------D
  secret_access_key: H----xxx-x-x---------------G

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  #exclude_lines: ['^DBG']

  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  #include_lines: ['^ERR', '^WARN']

  # Exclude files. A list of regular expressions to match. Filebeat drops the files that
  # are matching any regular expression from the list. By default, no files are dropped.
  #exclude_files: ['.gz$']

  # Optional additional fields. These fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

  ### Multiline options

  # Multiline can be used for log messages spanning multiple lines. This is common
  # for Java Stack Traces or C-Line Continuation

  # The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
  #multiline.pattern: ^\[

  # Defines if the pattern set under pattern should be negated or not. Default is false.
  #multiline.negate: false

  # Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
  # that was (not) matched before or after or as long as a pattern is not matched based on negate.
  # Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
  #multiline.match: after


#============================= Filebeat modules ===============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false
setup.template.name: "webanddevicelogstemplate"
setup.template.pattern: "weblogs*"

#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging


#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  #host: "localhost:5601"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

#============================= Elastic Cloud ==================================

# These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

#================================ Outputs =====================================

# Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["https://vpc-XXX-south-1.es.amazonaws.com:443"]
  index: "%{[fields.logtype]}-%{[agent.version]}-%{+yyyy.MM.dd}"
  #pipeline: "catalinaPipeline"

  # Protocol - either `http` (default) or `https`.
  protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - decode_json_fields:
     fields: ["data"]
#================================ Logging =====================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]

#============================== X-Pack Monitoring ===============================
# filebeat can export internal metrics to a central Elasticsearch monitoring
# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
setup.ilm.enabled: false

#================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

elastic.repo

[elasticsearch-7.x]
name=Elasticsearch repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/oss-7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

@AbhilashPurohit

Welcome to the community!

the OSS version of Filebeat doesn't include the S3 input
(reference: https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-s3.html).
The X-Pack tag indicates this feature is not included in the OSS version.

If the OSS version is an absolute requirement I suspect using Logstash or copying the files locally for Filebeat to pickup might work.

Thanks
/d

Thank you so much for the quick reply.

But when I don't use the oss version there is an error called could not get license of elastic search. Backoff connection failed to my elastic search vpc of aws.

So I think I need to purchase the elastic search license to connect to my filebeat in order to use the aws services right.

I have one more problem.
I have these log files in local but there is a huge memory leak when I am using it from local that is when my architect suggested to push logs to S3 and get it from there.
What are ur suggestions and answers for this.?

You will need to use the default distribution of Elasticsearch instead of the OSS one, but this by default comes with a free Basic license that is sufficient.

Thanks for the reply.
But why am I getting the error in my file beat when it's running that unable to get the license. Unable to verify the license. Etc.. It's not able to connect to elastic search through default filebeat.

Or do you mean I have to change the elastic search in aws to default distribution from oss? Is that what you mean?

Could you please clear it for me?

Yes, you need to upgrade to the default distribution.

Is it free or does it cost anything to make my filebeat with s3 work?

The default distribution by default has a free basic license level that will be sufficient.

Thanks for the info.. I will check with our cloud team about the free basic license. :blush:

If you are running in cloud, I'd look at https://www.elastic.co/cloud.

hi @Christian_Dahlqvist,

could you please share with us the document for upgrade default distribution ?
thank you,

Hey @Christian_Dahlqvist .
Need you support here .
My cloud team needs to know how to upgrade to default distribution from oss in elastic search.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.