# Why curator\_cli is not supporting aws\_sign\_request option?

**URL:** <https://discuss.elastic.co/t/why-curator-cli-is-not-supporting-aws-sign-request-option/152150>\
**Category:** Elasticsearch\
**Created:** [October 12, 2018, 4:27am UTC](https://discuss.elastic.co/t/why-curator-cli-is-not-supporting-aws-sign-request-option/152150 "2018-10-12T04:27:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![r-plus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/r-plus/32/36431_2.png) [@r-plus](https://discuss.elastic.co/u/r-plus)\
**Post date:** [October 12, 2018, 4:27am UTC](https://discuss.elastic.co/t/why-curator-cli-is-not-supporting-aws-sign-request-option/152150/1 "2018-10-12T04:27:41Z")

</div>

Looks like curator\_cli is not supporting `aws_sign_request` option, why?

```auto
$ curator_cli --version
curator_cli, version 5.5.4

$ curator_cli
Usage: curator_cli [OPTIONS] COMMAND [ARGS]...

Options:
  --config PATH Path to configuration file. Default: ~/.curator/curator.yml
  --host TEXT Elasticsearch host.
  --url_prefix TEXT Elasticsearch http url prefix.
  --port TEXT Elasticsearch port.
  --use_ssl Connect to Elasticsearch through SSL.
  --certificate TEXT Path to certificate to use for SSL validation.
  --client-cert TEXT Path to file containing SSL certificate for client auth.
  --client-key TEXT Path to file containing SSL key for client auth.
  --ssl-no-validate Do not validate SSL certificate
  --http_auth TEXT Use Basic Authentication ex: user:pass
  --timeout INTEGER Connection timeout in seconds.
  --master-only Only operate on elected master node.
  --dry-run Do not perform any changes.
  --loglevel TEXT Log level
  --logfile TEXT log file
  --logformat TEXT Log output format [default|logstash|json].
  --version Show the version and exit.
  --help Show this message and exit.

Commands:
  alias Add/Remove Indices to/from Alias
  allocation Shard Routing Allocation
  close Close Indices
  delete_indices Delete Indices
  delete_snapshots Delete Snapshots
  forcemerge forceMerge Indices (reduce segment count)
  open Open Indices
  replicas Change Replica Count
  restore Restore Indices
  rollover Rollover Index associated with Alias
  show_indices Show Indices
  show_snapshots Show Snapshots
  shrink Shrink Indices to --number_of_shards
  snapshot Snapshot Indices

$ curator_cli --aws_sign_request
Error: no such option: --aws_sign_request

$ curator_cli --aws-sign-request
Error: no such option: --aws-sign-request

```

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [October 12, 2018, 1:31pm UTC](https://discuss.elastic.co/t/why-curator-cli-is-not-supporting-aws-sign-request-option/152150/2 "2018-10-12T13:31:43Z")

</div>

It should if you build a `curator.yml` client file definition and use that with `curator_cli`. The next major release of Curator should also have these available at the command-line.

---

<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:** [November 9, 2018, 1:31pm UTC](https://discuss.elastic.co/t/why-curator-cli-is-not-supporting-aws-sign-request-option/152150/3 "2018-11-09T13:31:43Z")

</div>

Closed on November 9, 2018, 1:31pm UTC

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