# Amazon Linux 2023 Update (OpenSSL 3.2) causing OpenSSL.jl / HTTP.jl failures

**URL:** <https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090>\
**Category:** General Usage\
**Tags:** aws\
**Created:** [November 24, 2025, 4:56pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090 "2025-11-24T16:56:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wikunia](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wikunia/32/2180_2.png) [@Wikunia](https://discourse.julialang.org/u/Wikunia)\
**Post date:** [November 24, 2025, 4:56pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090/1 "2025-11-24T16:56:44Z")

</div>

Hi everyone,

I wanted to document a breaking issue that recently started appearing on AWS environments (specifically Amazon Linux 2023) as of mid-November 2025, in case anyone else is hitting a wall with their production builds.

### The Symptom

If you are running Julia on AWS (EC2, Lambda, or Docker containers based on `amazonlinux:2023`), you might suddenly see `HTTP.jl` or `OpenSSL.jl` failing during precompilation or initialization with an error like this:

`JuliaERROR: LoadError: AssertionError: ret == 1 Stacktrace: [1] OpenSSL.SSLContext(ssl_method::OpenSSL.SSLMethod, verify_file::String) @ OpenSSL .../src/ssl.jl:165`

This seems to happen even if your `Manifest.toml` hasn’t changed.

### The Cause

Amazon recently rolled out the **AL2023.9** release (Nov 2025), which updates the system OpenSSL version from 3.0 to **3.2.2** and enforces stricter FIPS provider management.

When `OpenSSL_jll` artifact (used by `HTTP.jl`) tries to initialize on the new AL2023 kernel, it conflicts with the system’s FIPS configuration, causing the context initialization to return `0` (failure) instead of `1` (success).

### Fixes

Not sure how to best fix this I only saw about ways on finding a way to use the openssl of AWS directly but would be nice if this could maybe be handled by OpenSSL.jl

For now I am fortunate to be able to drop a dependency to avoid this but I guess others will run into this so just wanted to open up a topic for this.

### Related issue

- [OpenSSL.jl#54](https://github.com/JuliaWeb/OpenSSL.jl/issues/54)

---

<div class="post-metadata">

**Author:** ![avik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/avik/32/17_2.png) [@avik](https://discourse.julialang.org/u/avik)\
**Post date:** [November 25, 2025, 8:18pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090/2 "2025-11-25T20:18:53Z")

</div>

I’ve added the results of some investigations and a reproducer into the linked issue: [OpenSSL v1.6.0 associated with bug with remote VSCode sessions · Issue #54 · JuliaWeb/OpenSSL.jl · GitHub](https://github.com/JuliaWeb/OpenSSL.jl/issues/54#issuecomment-3577360236)

---

<div class="post-metadata">

**Author:** ![affans](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/affans/32/11911_2.png) [@affans](https://discourse.julialang.org/u/affans)\
**Post date:** [November 25, 2025, 11:26pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090/3 "2025-11-25T23:26:16Z")

</div>

This is not just an Amazon issue. I am getting the same issue using Remote SSH on vscode to log in into an Ubuntu 24 server.

---

<div class="post-metadata">

**Author:** ![Wikunia](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wikunia/32/2180_2.png) [@Wikunia](https://discourse.julialang.org/u/Wikunia)\
**Post date:** [November 28, 2025, 4:33pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090/4 "2025-11-28T16:33:01Z")

</div>

Thanks for having a look into it. Just to double check the issue with vscode and AWS are the same, right? And 1.12 should work on AWS then as well?

---

<div class="post-metadata">

**Author:** ![avik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/avik/32/17_2.png) [@avik](https://discourse.julialang.org/u/avik)\
**Post date:** [December 1, 2025, 9:07pm UTC](https://discourse.julialang.org/t/amazon-linux-2023-update-openssl-3-2-causing-openssl-jl-http-jl-failures/134090/5 "2025-12-01T21:07:14Z")

</div>

OK, so this should now be fixed in OpenSSL.jl `v1.6.1`. Please let me know if this doesn’t fix things for you.

Ref: [Fix error when passing a CA cert directory by aviks · Pull Request #57 · JuliaWeb/OpenSSL.jl · GitHub](https://github.com/JuliaWeb/OpenSSL.jl/pull/57)

> [@Wikunia](#):
>
> Just to double check the issue with vscode and AWS are the same, right

I believe so, but I haven’t reproduced this on Amazon Linux myself. Please try out the new version and see what happens.

Regards

Avik