Use IAM roles for S3 instead of AWS Access Keys about hsds

[rsignell-usgs]

Relevant lines are here: https://github.com/HDFGroup/hsds/blob/master/runall.sh#L18-L19

[jreadey]

Hi @isuftin - The server code that creates a S3 connection is expecting the AWS access keys to be defined.

I'll try changing that to see if that will work with the EC2 IAM role.

[rsignell-usgs]

@isuftin and @jreadey , any chance this could be working by Wednesday of next week?
I've got a presentation to USGS CDI, and it would be cool to show, but of course I have backup plan.

[jreadey]

Yes -- I've been busy with some end of the quarter stuff - but should have time to look into it this week.

[jreadey]

I think I got this working now - implemented in commit: 35a6f71.

The default config looks for a IAM role: "hsds_role" if the AWS_SECRET_ACCESS_KEY environment variable is not set. If you'd like to use another name, change the "aws_iam_role" in config.py.

In any case, the role needs to enable read/writes to the S3 Bucket that you are using.

I'll keep this issue open till you confirm it works.

[jreadey]

I haven't heard about any problems this, so closing.
@isuftin - let me know if this isn't working for you.