For the rollover use case, index templates will not work for setting aliases in the way you have described.
To use with rollover, you may still need to create an index template for certain settings, but those should not include the rollover alias name. It should also match the new index pattern of coffii_amq-*.
If you choose to do rollover, I suggest managing your template using REST API calls, not Logstash. Once you've created the initial index + alias, as you've demonstrated already, Logstash will be configured to exclusively write to the alias you created, e.g.
index => "amp-rollover-alias"
No other work is necessary within Logstash. It will happily continue to write to that alias. You then handle all rollover within Curator. Curator sends the rollover API calls to Elasticsearch. Elasticsearch creates a new index, incrementing the index number from the last value, e.g. coffii_amq_000001 to coffii_amq_000002, and then automatically points the alias amq-rollover-alias at the new index, coffii_amq_000002. You do not have to do anything but call _rollover and have your conditions met for these things to happen. You don't need any alias information in the index template.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.