Azure-Sentinel
Azure-Sentinel copied to clipboard
Azure
Deprecated dependencies in S3toSentinel Lambda
Amazon have deprecated the .NET Core 3.1 runtime in AWS, as such we are looking to update to a supported runtime framework in AWS.
It looks as though the provided function has .NET Core 3.1 listed in the dependencies, which is preventing the functon from detecting the updated runtime framework (.NET6) and thus fail.
I have attempted to manually update the S3toSentinel.deps.json and S3toSentinel.runtimeconfig.json and provide the correct framework, but to no avail.
For context, here is the error presented by AWS Lambda when testing the function with the .NET6 runtime:
And here are what I believe to be the offending lines from S3toSentinel.deps.json and S3toSentinel.runtimeconfig.json, respectively:
Hi @lmarshman-caci , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 13 Mar 2024. Thanks!
Hi @v-rusraut, that's brilliant. Thanks so much for the swift response!
Hi @lmarshman-caci , Please provide more details about this issue or provide repro steps. Thanks
Hi @v-rusraut, please see screenshots attached to original post for log output from AWS Lambda, along with what I believe to be the lines responsible in the dependencies.
To reproduce, upgrade the Lambda runtime framework to a newer .NET version within AWS and trigger a test event from the AWS console.
The below output will be returned when running the function on a runtime other than .NET Core 3.1:
Please see this page from the AWS documentation around runtime deprecation: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-deprecation-levels
.NET Core 3.1 was fully deprecated on 03/05/2023, meaning it is no longer possible to deploy the provided Lambda function with the current dependency on this framework.
Hope this info is of use, please let me know if there's anything else I can provide from my end to assist.
Cheers, Leith
Hi @lmarshman-caci , Thanks for provide more information about issue, we will provide you an update till 22 Mar 2024.
Hi @lmarshman-caci ,Could you please confirm this the data connector i.e. https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/S3-Lambda ,so will work further analysis on replicating the issue
@v-muuppugund Hi there, that's correct - specifically, it's the two aforementioned files from the S3toSentinel.zip
Many thanks!
Hi @lmarshman-caci ,The following is the status 1.Set up done for prerequisites for environment 2.AWS lamda function created 3.Working on next steps for issue replication once done ,will update you and will work on changes for the issue.
Hi @lmarshman-caci ,The following is the status 1.Set up done for prerequisites for environment 2.AWS lamda function created 3.Working on next steps for issue replication once done ,will update you and will work on changes for the issue.
Hi @lmarshman-caci ,still need some time for completing the environment setup and replicating the issue,will update you
Hi @v-muuppugund, that's great - thank you for keeping us posted, it is much appreciated!
Hi @lmarshman-caci ,facing an issue while completing the environment setup ,working on it,will update you
Hi @lmarshman-caci ,There is a deprecation of .NET core and unable to repo the issue unable to create lamda functons with .net core3.1 as its nor supported ,so we need to create fresh LaMDA functions with .NET frame work, please find below screen shot for reference
Completed the analysis for this requirement and will be picking up in our queue and will update you once the changes have been completed,please let me know if you have any questions we can discuss in detail
Hi @v-muuppugund, many thanks for the update. Just to confirm, this deprecation was the cause for issue on our end also.
Appreciate you looking into this, I'll keep an eye out for further updates.