mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1605] The use of AWS Metadata Version 2 with EC2 Instances breaks S3FS mounts #841
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#841
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 @eelbrink on GitHub (Mar 16, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1605
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
s3fs --version
Amazon Simple Storage Service File System V1.86 (commit:unknown) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
dpkg -s fuse
Package: fuse
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 104
Maintainer: Ubuntu Developers ubuntu-devel-discuss@lists.ubuntu.com
Architecture: amd64
Version: 2.9.7-1ubuntu1
Depends: libc6 (>= 2.14), libfuse2 (= 2.9.7-1ubuntu1), adduser, mount (>= 2.19.1), sed (>= 4)
Conffiles:
/etc/fuse.conf 298587592c8444196833f317def414f2
Description: Filesystem in Userspace
Filesystem in Userspace (FUSE) is a simple interface for userspace programs to
export a virtual filesystem to the Linux kernel. It also aims to provide a
secure method for non privileged users to create and mount their own filesystem
implementations.
Homepage: https://github.com/libfuse/libfuse/wiki
Original-Maintainer: Laszlo Boszormenyi (GCS) gcs@debian.org
Kernel information (uname -r)
5.4.0-1025-aws
GNU/Linux Distribution, if applicable (cat /etc/os-release)
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
s3fs command line used, if applicable
/etc/fstab entry, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
When we implemented AWS EC2 Metadata Version 2 for our EC2 instances due to security reasons, s3f3 does not connect to s3 bucket anymore.
The below code shows how Metadata version 2 is enabled.
It complains with the following error:
@thenickdude commented on GitHub (Mar 17, 2021):
Support for IMDSv2 was only added in 1.88, you're using the older 1.86. Update to the latest release.
@eelbrink commented on GitHub (Mar 24, 2021):
Thanks @thenickdude, I will update the once that are still using an older version. However, how would this actually work? Does S3FS request the secure token itself? or do we have to request the token first and then run S3FS with
use_session_tokenin order for it to work?@kornicameister commented on GitHub (Nov 2, 2021):
Any update on question from @eelbrink? @eelbrink perhaps you've been able to determine how this work? Most specifically how that is going to work with /etc/fstab?
@kornicameister commented on GitHub (Nov 2, 2021):
If I try to use
s3fslike so:s3fs some-bucket ./mount-point -o use_cache=/tmp -o iam_role=MyRole -o use_session_token -f -dI get following output and bucket does not mount:and I do run
s3fs --version: v1.90