Brandon Bradley

I recommend using `elasticsearch.pkg` state during your AMI creation step and `elasticsearch` state on your running instances.

@myoung34 If you used just `elasticsearch.pkg` during your Packer build, your extra steps would not be required (sans SaltStack removal). rabbitmq-formula seems to have used this pattern because their `pkg.installed`...

Can you share your pillar data? And the relevant part of the state run?

I think you are looking for `match: grain` instead of `match: pillar`.

Sorry, I was wrong. There is pillar matching. Is that top.sls in your pillar or states?

Do you have any Elasticsearch Debian repos in your sources.list or sources.list.d?

What is the contents of those files?

Did you add the asterisks beside `1.0.3+dfsg-5+deb8u1 0`?

What does your `sources.list` entry for http://security.debian.org look like?

How do you setup Debian? Cloud? debootstrap? My Jessie VMs and [the documentation](https://www.debian.org/security/) use: ``` deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free ```