-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSMXmlRepository.GetAllElementsAsync fails to call SSM when XRay is enabled #43
Comments
The problem is that I'm not sure where I should call these methods manually though... not even sure there's an extension point available for me to do this (creating the segment around the |
Because the library is polling in the background outside of the scope of a request that creates the X-Ray segment. That is what is triggering the The easiest workaround is to set the Here is the documentation for more information. |
Thanks for the workaround, I'll probably resort to that and disable the related logs to avoid polluting our error notifications channel. It's a shame there's no way to have a more specific way to address this problem though, there might be cases where it's still legitimate to throw an error. Also, one may want to instrument these calls too. Maybe provide extension points around the call to SSM? |
Hi madmox, as stated by normj, this is currently behaving as designed. However, we will change this request from a bug to a feature request and check if we can prioritize it. |
Describe the bug
I have an ASP.NET application deployed on ECS Fargate, and I want to use SSM for data protection. I also use XRay for tracing. When the application starts, it fails because it can't read SSM (even though I setup the correct IAM permissions in the task's role).
Expected Behavior
The application should start normally.
Current Behavior
The following exceptions are thrown:
Reproduction Steps
AWS .NET SDK and/or Package version used
Amazon.AspNetCore.DataProtection.SSM 3.0.0
Targeted .NET Platform
.NET 6
Operating System and version
Docker image mcr.microsoft.com/dotnet/aspnet:6.0
The text was updated successfully, but these errors were encountered: