libssl.so.1.1 not found in al2.v20

[evbo]

I'm using AppConfig lambda layer provided by AWS, as demonstrated here:
https://github.com/ymwjbxxq/rust_aws_app_config

INIT_START Runtime Version: provided:al2.v20 Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:xyz
--
[appconfig agent] 2023/08/07 23:49:03 INFO AppConfig Lambda Extension 2.0.165
[appconfig agent] 2023/08/07 23:49:03 INFO serving on localhost:2772
/var/task/bootstrap: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
EXTENSION Name: AppConfigAgent State: Ready Events: [INVOKE, SHUTDOWN]
[appconfig agent] 2023/08/07 23:49:04 INFO AppConfig Lambda Extension 2.0.165
[appconfig agent] 2023/08/07 23:49:05 INFO serving on localhost:2772
/var/task/bootstrap: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Everything's been working great, then I randomly get this error message after many successful executions. Any suggestions how to debug this further? How did it ever work to begin with? That version of amazon linux hasn't had a patch since July 25th, so that hasn't changed.

I am using the following layer:
arn:aws:lambda:us-west-2:359756378197:layer:AWS-AppConfig-Extension-Arm64:45

[calavera]

Your code depends on OpenSSL. The AWS Lambda sandbox doesn't have that library installed, and your code won't run. I know nothing about the project that you're pointing to, but I'd recommend you to build it with Rustls, removing any dependency it has with OpenSSL.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for the maintainers of this repository to see.
If you need more assistance, please 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.

[evbo]

@calavera I figured it out: It is actually true that AWS Lamba did have OpenSSL installed, which is why I never had this error until recently when they deprecated TLS version 1.1:
https://aws.amazon.com/blogs/security/tls-1-2-required-for-aws-endpoints/

So the solution is to either update to depending on OpenSSL for versions >=TLS 1.2 or migrate to using rustls-tls, which I agree is my favorite approach too