alarm "console-access-without-mfa" due to external identity provider

0

Hello everyone, We used Okta as an identity provider and also do MFA via Okta to access AWS. AWS now doesn't notice that we are doing mfa and we get the alarm "console-access-without-mfa" in cloudwatch. Does anyone have a similar problem or can tell us how we can teach AWS that we do MFA via Okta and this alarm disappears

1 個回答
0
已接受的答案

Hello ,

This is Dinesh from AWS Premium support.

Please note that at the moment it is not possible to enable MFA on AWS side for SAML federated users. The current best practice is to handle it on the identity provider side. However, this would still not resolve your problem as AWS STS does not carry forward the MFA claim from your IdP to AWS. Thus, SAML authenticated users even with an MFA authentication on the IdP side will be considered as MFA unauthenticated users on AWS endpoint. This is applicable for AWS SSO users as well.

Having said that, our service team is aware of this issue and there is an outstanding feature request to set "additionalEventData.MFAUsed" even when MFA is used on IdP side. All of our new announcements and releases can be found on our What’s New page[+] https://aws.amazon.com/new/ and news blog[+] https://aws.amazon.com/blogs/aws/

Workaround: You can consider to modify the event pattern as the following so you don't get alarm for all the SAML federated user's (IdP Users) login.

{($.eventName = "ConsoleLogin") && ($.additionalEventData.MFAUsed != "Yes") && ($.additionalEventData.SamlProviderArn NOT EXISTS)}

Thank you

AWS
已回答 6 個月前
  • Hi Dinesh, thanks for the fast respond. Then we'll wait and see if there's a solution to the issue soon

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南