This will then return a new set of temporary IAM credentials that Cyberduck can use. You will need to use the Security Token Service (STS) command to get-session-token while providing an MFA code. So we are after a simple solution for this please. I should also mention that the users who are gonna connect to S3 and browse through buckets are not tech people and they cannot do much technical stuff.
It would be great if anyone of you could help and have had the same scenario. When MFA is enabled on user account, Cyberduck won't let connecting to S3 and keeping failing and as soon as we disable MFA on that same account we are able to connect to S3 through Cyberduck with same Access Key and Secret Key.ĭo you guys have any thought how we can work around this and force everyone have MFA enabled on their account but being able to access S3 buckets using their own Access Key and Secret Key while MFA enabled? The problem we have is we use Cyberduck to access our AWS S3 buckets and currently we are using Access Keys and Secret Keys within Cyberduck to explore S3 buckets. So currently everyone is forced to enable MFA on their account and use that whenever they login to AWS and need to access anything. We have a policy in place for our users to limit them access to AWS without having MFA enabled on their account.
0 kommentar(er)
