Corretto is designed as a drop-in replacement for all Java SE distributions unless you are using features not available in OpenJDK. Once Corretto binaries are installed on a host and correctly invoked to run your Java applications (e.g., using the alternatives command on Linux), existing command-line options, tuning parameters, monitoring, and anything else in place will continue to work as before.

Before OpenJDK 11, JavaFX was included in OpenJDK. However, in 2018, Oracle decoupled JavaFX from OpenJDK, removing it from OpenJDK distributions. Corretto 8 does include JavaFX for the following platforms:

AL2 x64
AL2023 x64
Generic Linux x64
Windows x86 JDK
Windows x64 JDK
Windows x86 JRE
Windows x64 JRE
macOS x64

We do not include it on other platforms, regardless of version. For example, JavaFX is not supported in Corretto 8 for Mac M1.

We recommend that you upgrade to Corretto 21+, since this release will have more up-to-date code and generally perform better than its predecessors. In some instances you may wish to be on the latest JDK, which could be a short term support release with near EOL date. You can find and download the JFX releases from the JavaFX website.

Corretto 8 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later, Server 2016, Server 2019, Server 2022 and Server 2025.

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 6+, CentOS 6+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+

Corretto 11 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later, Server 2016, Server 2019, Server 2022, and Server 2025.

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 6+, CentOS 6+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+.

Corretto 17 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later,  -Server 2016, Server 2019, Server 2022, and Server 2025.

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 6+, CentOS 6+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+.

Corretto 21 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later, Server 2016, Server 2019, Server 2022, and Server 2025

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 6+, CentOS 6+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+.

Corretto 25 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later, Server 2016, Server 2019, Server 2022, and Server 2025.

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 7+, CentOS 7+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+.

Corretto 26 installation packages are distributed by Amazon for Linux (glibc), Linux (musl-libc), Windows, and macOS.

Windows builds are supported on versions 10 or later, Server 2016, Server 2019, Server 2022, and Server 2025.

macOS builds are supported on all versions of macOS still receiving security patches from Apple. Currently supported versions are 14 (Sonoma) or later on x64 and aarch64 architectures.

Linux (glibc) builds are supported on Red Hat Enterprise Linux 7+, CentOS 7+, Ubuntu Linux 14+, Debian Linux 8+, Amazon Linux AMI, and SuSE 12+.

Linux (musl-libc) builds are supported on Alpine Linux 3.20+.

If a security scanner reports that a Corretto-Docker image includes a CVE, the first recommended action is to seek an updated version of this image. Updated Corretto-Docker images are available at this site.

If no updated image is available, run the appropriate command to update packages for the platform, e.g. run "yum update -y --security" for AmazonLinux or "apk -U upgrade" for Alpine Linux in your Dockerfiles or systems to resolve the issue immediately.

If no updated package is available, please treat this as a potential security issue and follow the [AWS vulnerability reporting instructions] or email AWS security directly at aws-security@amazon.com.

It is the responsibility of the base docker image supplier to provide timely security updates to images and packages. AWS only supplies base docker images for Amazon Linux, which are available from the Docker Hub Amazon Linux 2 page and the Amazon Linux 2 ECR Public Gallery. Alpine-based docker images are available from the Docker Hub Alpine Linux page.

Docker Hub automatically rebuilds Docker images when a new base image is made available, but the Corretto team does not make changes to our Dockerfiles to pull in one-off package updates. If a new base image has not yet been made generally available by a base docker image supplier, please contact that supplier to request that the fix be addressed in a new base docker image distribution.

Note that there are multiple reasons why a CVE may appear to be present in a docker image, as explained here.