Better support for permissions-restricted (IAM) environments on AWS

[coderanger]

This addresses two issues I filed (LIBCLOUD-497, LIBCLOUD-498).

It adds:

• ACL override support for S3 via extra={'acl': '...'}
• Support for a token= keyword argument on S3 driver (and can be easily added to other AWS drivers) to include the AWS Security Token param/header, which is required when using IAM role-provider credentials or other temporary AS credentials.
• Makes get_container on S3 no longer call list_containers and otherwise work correctly in an environment with highly restricted permissions. This is a (minorly) backwards incompatible change as `get_container will no longer load the creation time of the bucket. This is not of huge importance, but should be mentioned in the release notes.

[Kami]

Thanks!

I'm going to add more comments, but for testing that the token is present you should add a test case to the MockHttp class which actually receives the requests and returns the mock responses.

For example, you could set MockHttp.type inside test_token method and then add a corresponding method to the MockHttp class and verify that token is present in the headers.

E.g.

 def _TOKEN(self, method, url, body, headers):
    self.assertEqual(headers['x-amz-security-token'], ...)
   ...

[Kami]

Thanks!

I'm going to add more comments, but for testing that the token is present you should add a test case to the MockHttp class which actually receives the requests and returns the mock responses.

For example, you could set MockHttp.type inside test_token method and then add a corresponding method to the MockHttp class and verify that token is present in the headers.

E.g.

 def _TOKEN(self, method, url, body, headers):
    self.assertEqual(headers['x-amz-security-token'], ...)
   ...

[coderanger]

The headers passed in there don't seem to contain any auth-related parameters.

(Pdb) headers
{'Host': 's3.amazonaws.com', 'Accept-Encoding': 'gzip,deflate', 'User-Agent': 'libcloud/0.14.0-beta3 (Amazon S3 (standard)) '}

[coderanger]

The headers passed in there don't seem to contain any auth-related parameters.

(Pdb) headers
{'Host': 's3.amazonaws.com', 'Accept-Encoding': 'gzip,deflate', 'User-Agent': 'libcloud/0.14.0-beta3 (Amazon S3 (standard)) '}

[Kami]

@coderanger Oh, right, I totally missed this out. Rest of the values get sent as part of query parameters and not via headers.

This means the code needs to be updated to send X-Amz-Security-Token value via headers and not via query parameters. We also need to test this and make sure it works if you send Signature, AWSAccessKeyId, etc. via query parameter and X-Amz-Security-Token via headers.

Edit: While we are at it, it would also be good to check it they might support sending this value via query parameters as well (I quickly glanced over the documentation and I could see this value being sent via headers).

[Kami]

@coderanger Oh, right, I totally missed this out. Rest of the values get sent as part of query parameters and not via headers.

This means the code needs to be updated to send X-Amz-Security-Token value via headers and not via query parameters. We also need to test this and make sure it works if you send Signature, AWSAccessKeyId, etc. via query parameter and X-Amz-Security-Token via headers.

Edit: While we are at it, it would also be good to check it they might support sending this value via query parameters as well (I quickly glanced over the documentation and I could see this value being sent via headers).

[coderanger]

Still need to double check that Amazon actually works with this style of sending the token, will do that in a moment.

[coderanger]

Still need to double check that Amazon actually works with this style of sending the token, will do that in a moment.

[Kami]

Hmm, are you sure that the token also needs to be taken into account when calculating the signature?

From the documentation (http://docs.aws.amazon.com/STS/latest/UsingSTS/using-temp-creds.html):

"Include the IAM session token that is part of the temporary security credentials. You include the session token as an authorization header to the request—for example, as the X-Amz-Security-Token header. (The session token is not part of the information that's used to create the signature.)"

[coderanger]

Yes, not because it has special meaning but because you need to sign either all params or all x-amz headers (depending on the type of request).

[Kami]

I see.

Did you test the whole patch with a live installation yet?

In any case, the patch looks good to me. I'll go ahead and test it and if everything looks good, I'll go ahead and merge it.

[coderanger]

Yep, tested via depot with both normal and temporary credentials.

[Kami]

I assume that S3 still returns 401 if you don't have the necessary permissions and the container doesn't exist?

If that is indeed the case, I wonder if just throwing here might be better / more correct.

[coderanger]

No, it returns a 404 no matter what your permissions are. You only get 401 if it exists and you don't have perms.

[Kami]

Alright, in this case we should be all set.

[Kami]

Alright, I've squashed the commits and merged changes into trunk - thanks!

Tomorrow, I also plan to update documentation with some examples of how to use this new functionality.

[Kami]

Alright, I've squashed the commits and merged changes into trunk - thanks!

Tomorrow, I also plan to update documentation with some examples of how to use this new functionality.