ec2 Client does not honor parameters

[theRealDrumBum]

I Briefly ran through the code, but it looks like params are not being passed on the ec2 client (the only PostField for curl on the stack was the 'describeInstances' method name). For example:

$response = $ec2->describeInstances(array(
'Filter' => array(
// So AWS isn't exactly honoring this filter, will need to double check below
array(
'Name' => 'instance-state-name',
'Value' => $filterStopped ? 'running' : '*'
),
array(
'Name' => 'tag-key',
'Value' => $tag
)
)
));

Returns the entire corpus of our ec2 account and does not do any filtering.

[mtdowling]

The value you should pass is actually Filters not Filter. Does that fix the issue for you?

[theRealDrumBum]

Good catch! It changed the results, but it wasn't why I expected. I changed it to handle a very simple case first:

  'Filters' => array(
                array(
                    'Name'   => 'instance-state-name',
                    'Value'  => 'running'
                )

And didn't get any results..., where without the Filter I get 197 results (mixed with running and stopped states).

[jeremeamia]

See the API docs for DescribeInstances.

Values should also plural (i.e.,Value should be Values). Sorry we didn't catch that the first time around. It should look like:

'Filters' => array(
    array(
        'Name'   => 'instance-state-name',
        'Values' => array('running')
    )
)

There is also an example in the EC2 integration tests.

[theRealDrumBum]

Awesome! Thanks for pointing that out.