Amazon Web Services S3 connectors

Question

Amazon Web Services S3 connectors

Kirolos Mena 5

We have Microsoft Sentinel, and we need to integrate with Amazon Web Services S3 connectors, but we are getting the error with the role

User's image

Neil Carless 0 Reputation points

2025-03-31T10:02:43.6766667+00:00

The RoleSessionName that Microsoft sends has changed from MicrosoftSentinel_ to MicrosoftDefenderForClouds_.

This is set in the Trust Relationship policy for the OIDC_xxxxxx role
Sakshi Devkante 3,335 Reputation points Microsoft External Staff

2025-03-31T16:41:45.9733333+00:00

Hello Kirolos Mena,

You already opened a support ticket with Severity A, 2503270050003107, as we noticed. A support engineer has been actively working on the ticket and is currently discussing the issue with their team internally. I or the support engineer will notify you of any updates regarding the ticket.
Catherine Kyalo 1,305 Reputation points Microsoft Employee

2025-04-02T08:36:01.54+00:00

Hi @Kirolos Mena ,

I am following up to find out whether you found a solution to this question. It would be helpful for the community to understand how you managed to resolve this scenario.
Divya Mohan P 20 Reputation points

2025-04-03T12:35:24.0166667+00:00

Both of these RoleSessionName are not working
MicrosoftSentinel_
MicrosoftDefenderForClouds_.
Divya Mohan P 20 Reputation points

2025-04-07T08:03:01.0833333+00:00

@Neil Carless This solution doesn't seems to work consistently.

2 answers

Your answer

Neil Carless 0 Reputation points

2025-03-31T10:02:43.6766667+00:00

The RoleSessionName that Microsoft sends has changed from MicrosoftSentinel_ to MicrosoftDefenderForClouds_.

This is set in the Trust Relationship policy for the OIDC_xxxxxx role
Sakshi Devkante 3,335 Reputation points Microsoft External Staff

2025-03-31T16:41:45.9733333+00:00

Hello Kirolos Mena,

You already opened a support ticket with Severity A, 2503270050003107, as we noticed. A support engineer has been actively working on the ticket and is currently discussing the issue with their team internally. I or the support engineer will notify you of any updates regarding the ticket.
Catherine Kyalo 1,305 Reputation points Microsoft Employee

2025-04-02T08:36:01.54+00:00

Hi @Kirolos Mena ,

I am following up to find out whether you found a solution to this question. It would be helpful for the community to understand how you managed to resolve this scenario.
Divya Mohan P 20 Reputation points

2025-04-03T12:35:24.0166667+00:00

Both of these RoleSessionName are not working
MicrosoftSentinel_
MicrosoftDefenderForClouds_.
Divya Mohan P 20 Reputation points

2025-04-07T08:03:01.0833333+00:00

@Neil Carless This solution doesn't seems to work consistently.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Catherine Kyalo 1,305 Microsoft Employee

Hi Kirolos Mena,

This issue has now been resolved and the AWS Connection to sentinel has now been restored. We apologize for any inconvenience caused.

Here is a similar issue for more information: https://learn.microsoft.com/en-us/answers/questions/2244660/aws-assumed-role-rolesessionname-is-not-working-co

If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.

Share via

Amazon Web Services S3 connectors

2 answers

Your answer