# Filebeat: Exiting: Error while initializing input: Error creating input. No such input type exist: 'aws-cloudwatch'

**URL:** <https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [February 1, 2022, 11:28am UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942 "2022-02-01T11:28:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![h4rdl0ck](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@h4rdl0ck](https://discuss.elastic.co/u/h4rdl0ck)\
**Post date:** [February 1, 2022, 11:28am UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/1 "2022-02-01T11:28:51Z")

</div>

Hello everyone, filebeat stopped because it supposedly doesn't exist for the input type aws-cloudwatch.

That's the error-messsage:  
2022-02-01T11:02:36.673Z ERROR instance/beat.go:933 Exiting: Error while initializing input: Error creating input. No such input type exist: 'aws-cloudwatch'

And that's my filebeat-input-config:

```auto
filebeat.inputs:
- type: aws-cloudwatch
  role_arn: arn:aws:iam::######################-ecs-task-role
  log_group_arn: arn:aws:logs:eu-central-1:#######################:*
  start_position: beginning
  region_name: eu-central-1
  enabled: true

```

Filebeat Version is 7.16.3

Can someone help ?

---

<div class="post-metadata">

**Author:** ![marc.guasch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc.guasch/32/74642_2.png) [@marc.guasch](https://discuss.elastic.co/u/marc.guasch)\
**Post date:** [February 1, 2022, 11:56am UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/2 "2022-02-01T11:56:38Z")

</div>

Hello!

What version of filebeat are you using? Cloudwatch input is only available with the Elastic License licensed filebeat, if you have the Apache 2.0 licensed version it will not be available. Can this be the issue?

---

<div class="post-metadata">

**Author:** ![h4rdl0ck](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@h4rdl0ck](https://discuss.elastic.co/u/h4rdl0ck)\
**Post date:** [February 1, 2022, 12:02pm UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/3 "2022-02-01T12:02:14Z")

</div>

Hello,  
think i am using the apache-licensed Version. Downloads from there: [Download Filebeat • Lightweight Log Analysis | Elastic](https://www.elastic.co/de/downloads/beats/filebeat)

Do i have to pay for the elastic-licensed Version ?

---

<div class="post-metadata">

**Author:** ![marc.guasch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc.guasch/32/74642_2.png) [@marc.guasch](https://discuss.elastic.co/u/marc.guasch)\
**Post date:** [February 1, 2022, 1:35pm UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/4 "2022-02-01T13:35:10Z")

</div>

The URL you shared points to the Elastic License version:

- [Download Filebeat • Lightweight Log Analysis | Elastic](https://www.elastic.co/de/downloads/beats/filebeat)

You can find the Apache 2.0 version at [Download Filebeat - OSS • Lightweight Log Analysis | Elastic](https://www.elastic.co/downloads/beats/filebeat-oss)

The Elastic License distribution lets you use [this free features](https://www.elastic.co/subscriptions).

If you are in doubt, try downloading the default Elastic License distribution and try your config again.

---

<div class="post-metadata">

**Author:** ![h4rdl0ck](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@h4rdl0ck](https://discuss.elastic.co/u/h4rdl0ck)\
**Post date:** [February 1, 2022, 2:02pm UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/5 "2022-02-01T14:02:30Z")

</div>

Hello Marc, thanks for your answer.

Now it is clear that i am using the elastic licensed Version. Where does the Error come from ?

---

<div class="post-metadata">

**Author:** ![marc.guasch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc.guasch/32/74642_2.png) [@marc.guasch](https://discuss.elastic.co/u/marc.guasch)\
**Post date:** [February 1, 2022, 2:25pm UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/6 "2022-02-01T14:25:32Z")

</div>

I tried your provided config and I only get the mentioned error with the OSS version. Could you check the LICENSE.txt file that is found in your filebeat folder?

In addition, can you share your full config file in case I am missing something? Thanks!

---

<div class="post-metadata">

**Author:** ![h4rdl0ck](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@h4rdl0ck](https://discuss.elastic.co/u/h4rdl0ck)\
**Post date:** [February 2, 2022, 7:00am UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/7 "2022-02-02T07:00:00Z")

</div>

Good Morning Marc,

as you suggested I looked at the LICENSE.txt and it is the ELASTIC LICENSE AGREEMENT.

The error message continues to appear.

Here is my complete filebeat.yml:

```auto
filebeat.inputs:
- type: aws-cloudwatch
  role_arn: arn:aws:iam::#####################
  log_group_arn: arn:aws:logs:eu-central-##################:*
  start_position: beginning
  region_name: eu-central-1
  enabled: true
filebeat.config.modules:
  enabled: false
fields:
Environment: $ENV_NAME
  ApplicationTechName: $APP_NAME
  Component: logstash
# InstanceId: $INSTANCE
# AvailabilityZone: eu-central-1
output.logstash:
  hosts: ["################:5044"]
  ttl: 600
  pipelining: 0
  ssl.certificate_authorities: ["/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem"]
  enabled: true
logging.to_syslog: false
logging.level: info
fields_under_root: true
name: frontend

```

---

<div class="post-metadata">

**Author:** ![h4rdl0ck](https://avatars.discourse-cdn.com/v4/letter/h/e274bd/32.png) [@h4rdl0ck](https://discuss.elastic.co/u/h4rdl0ck)\
**Post date:** [February 2, 2022, 10:24am UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/8 "2022-02-02T10:24:30Z")

</div>

Update: After checking and updating my config in filebeat.yml the error no longer appears.

Thank you for your help Marc 😉

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 2, 2022, 12:25pm UTC](https://discuss.elastic.co/t/filebeat-exiting-error-while-initializing-input-error-creating-input-no-such-input-type-exist-aws-cloudwatch/295942/9 "2022-03-02T12:25:28Z")

</div>

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