mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #387] Why do you need to specify IAM role name? #204
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#204
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wimnat on GitHub (Apr 6, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/387
I would like to know why you need to specify IAM role name? When would IAM role specified be different than what can be found out from http://169.254.169.254/latest/meta-data/iam/info?
To maintain backward compatibility, I propose that you should be able to specify an option that reads the IAM role from http://169.254.169.254/latest/meta-data/iam/info and then uses this to authenticate.
My reasoning for this request - I want to add an s3fs mount to my fstab before creating an AMI. The AMI may be started with different iam roles so i don't want to hard code to a particular iam role name.
@ggtakec commented on GitHub (May 6, 2016):
@wimnat I'm sorry for my late reply.
I mered new codes which is changed about iam_role option.
New iam_role option requires the IAM role name or "auto".
If you specify "auto", s3fs will automatically use the IAM role names that are set to an instance.(loading IAM role name from http://169.254.169.254/latest/meta-data/iam/info)
If you specify this option without any argument, it is the same as that you have specified the "auto".
As a result of this change, I think it is what you want.
I closed this issue, but if you found bugs or have requests, please reopen this issue.
Thanks.
@vbarba commented on GitHub (May 19, 2016):
Hi,
I think that this is not working propperly:
s3fs bucket-tomount /mnt -o iam_role
s3fs: could not determine how to establish security credentials.
but instance role is ok:
curl http://169.254.169.254/latest/meta-data/iam/info
{
"Code" : "Success",
"LastUpdated" : "2016-05-19T11:42:58Z",
"InstanceProfileArn" : "arn:aws:iam::155XXXXXX:instance-profile/XXXXX",
"InstanceProfileId" : "AIPAIJSXXXXXXV4OJS"
}
Thanks.
@nturner commented on GitHub (May 20, 2016):
I'm seeing the same problem as @vbarba. I filed https://github.com/s3fs-fuse/s3fs-fuse/issues/419 to track this.
@ggtakec commented on GitHub (May 29, 2016):
@vbarba I merged @nturner 's patch, please see #421 and use latest codes in master branch.
Regards,