AddSystemsManager causing Deadlock or .NET application to stop unexpectedly
WarrenFerrell opened this issue · comments
Description
Calling .AddSystemsManager and then .Build() causes a 30 second lag.
Reproduction Steps
Using Amazon.Lambda.RuntimeSupport to run a .NET 5 container. Running latest lambda, CDK, packages and latest amazonlinux. Was working 3 weeks ago. Downgrading Lambda packages has not fixed the issue.
Logs
Cannot get any logs because I don't know of any easy way to access the lambda container.
Environment
- Build Version 2.1.0
-
- OS Info: AmazonLinux
- Build Environment: Terminal
dotnet publishinside .net 5 SDK container -
- Targeted .NET Platform: net5.0
What I need to debug the issue further
Need a better way to debug what is going on in the container, right now it's like testing a black box that takes 10 minutes to deploy.
What I've tried
- Downgrading packages,
- Moving Configuration build to before starting lambda bootstrapper.
- Specifying awsCredentials explicitly (this fixed local SSO with the latest awssdk)
- downgrading to Amazonlinux build from 2 months ago
- Tracing calls by submoduling aws-dotnet-extensions-configuration (traced issue to SystemsManagerProcessor:65)
This is a 🐛 bug-report
I tracked this down to line 65 of SystemsManagerProcessor aka the call to IAmazonSimpleSystemsManagement.GetParametersByPathAsync . Going to post over there as well to see if they have any insight
Issue turned out to be some reconfiguration of VPN subnet rules I was not made aware of.
⚠️ COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.