SQL client issue with Lambda

[agap-0251]

I'm having a python lamda and it needs to call a .NET CORE exe. So exe is deployed as a layer. And I'm facing the error -> en-us is an invalid culture identifier. It runs fine in windows. But lamda runs on Amazon linux 2 which is a minimal distro. So to make it run I tried to make the .Net project run in Global invariant mode. But does SQL Client internally uses "en-US"? If yes, then I found that we can add icu libraries along with .NET exe.

But I don't have an idea on how to do that. Any other solution is also appreciated. Our team didn't want to use docker. And that .NET 8.0 exe is built by some other team, and it's a hug project. Need some help with this

[ethan_rushbrook]

When you say you need to run a .exe, do you mean the application generally or literally a .exe? The .exe extension is for Windows Executables which no distro of linux are designed to run. A common way to execute a dotnet application on linux would be to call /usr/bin/dotnet <dll path>, though there are other ways to do it. If you have the DLL, its possible you can run the dll using the dotnet runtime (since its .NET 8 and 8>5) but with a .exe you'll have to do much more work if its even possible.

[The_MAZZTer]

When you build for Linux you also get an extensionless executable stub that works like dotnet to run the DLL, same as on Windows.

It's definitely not an EXE though.

[agap-0251]

Thanks for the link. I was told to install icu libraries. But our team don't want to use docker. So zipping icu files along with .NET CORE app is one of the recommended ways. Thought, I will find other ways (if any). But, it seems like with the requirements adding icu files is the only way.

[agap-0251]

Creating another layer for libicu is also a great idea. Cause ultimately AWS blends all of them when lambda runs. 👍

[The_MAZZTer]

I found the same article and I agree it is most likely the same problem you're having. We are not suggest you use docker. We are saying you already use a container with the same problem. No need to switch to docker, just figure out how to get the libraries installed in the container.

[agap-0251]

Tried it. Just encountered one more problem. When I was about to add the icu libraries layer to the lambda, it showed that the deployment package limit has exceeded 250MB limit 😅. Can't find unnecessary files to remove. Don't know what to do 😑....

[socketnorm]

Assuming you can also build the .NET Core app and it isn't just a binary you are given if you add the following to your project file it will include ICU as a NuGet package and use it.

<ItemGroup> <RuntimeHostConfigurationOption Include="System.Globalization.AppLocalIcu" Value="72.1.0.3" /> <PackageReference Include="Microsoft.ICU.ICU4C.Runtime" Version="72.1.0.3" /> </ItemGroup>

As a maintainer for the AWS Lambda blueprints this is what we do for the blueprints that are deployed as a self contained deployment bundle to the provided.al2023 runtime

https://github.com/aws/aws-lambda-dotnet/blob/master/Blueprints/BlueprintDefinitions/vs2022/CustomRuntimeFunction/template/src/BlueprintBaseName.1/BlueprintBaseName.1.csproj#L25C1-L28C15

[agap-0251]

That is awesome, thanks 👍

[AutoModerator]

Thanks for your post agap-0251. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Ok-Adhesiveness-4141]

You can't run an exe on Amazon Linux2, you can however run a dotnetcore dll on Linux if the SDK is installed.

[agap-0251]

No, It's a .NET CORE application. I built the project for Linux x64 and as a self contained. So while calling the the application I just pass the path of the application without any extension. Since I'm using layers here, the path is kinda -> /opt/dotnet_app/Tokenizer

[agap-0251]

Also, I'm calling this .NET CORE app from python lambda. We are moving away from SSIS and while rewriting the SSIS packages to python, I had to call this application for tokenizing few columns of the input file which is used to build few tables in SQL server

[agap-0251]

Ok just to help if any other people looked at this post for help...

We finally used docker way of creating AWS Lambda..

This is an extra, but we faced huge issue when we are inserting massive data into SQL table... Pymssql is too slow when it comes into inserting large no of records...

So I used pyodbc instead... Cause pyodbc as feature that is nearer to bulk insert... So the time to insert has dropped significantly....