Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Amazon Corretto

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Amazon Corretto is a downstream distribution of the Open Java Development Kit (OpenJDK). This open source technology allows users to develop and run Java applications on a variety of operating systems such as Windows, Linux, and macOS. This distribution of OpenJDK is intended to act as a drop-in replacement for Java standard edition (SE) distributions.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.6
Decision Date:	06/21/2024 at 22:00:33 UTC
Introduced By:	TRM Request
Vendor Name:	Amazon Web Services

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
8.232.x	10/14/2019	01/15/2020	01/15/2020
8.242.x	01/15/2020	04/15/2020	04/15/2020
8.252.x	04/14/2020	07/15/2020	07/15/2020
8.262.x	07/15/2020	10/20/2020	10/20/2020
8.265.x	07/29/2020	10/20/2020	10/20/2020
8.272.x	10/20/2020	01/15/2021	01/15/2021
8.275.x	11/06/2020	01/15/2021	01/15/2021
8.282.x	01/15/2021	04/15/2021	04/15/2021
8.292.x	04/14/2021	07/15/2021	07/15/2021
8.302.x	07/12/2021	10/15/2021	10/15/2021
8.312.x	10/15/2021	01/15/2022	01/15/2022
8.304.x	01/15/2022	04/15/2022	04/15/2022
8.303.x	10/15/2021	01/15/2022	01/15/2022
8.332.x	04/15/2022	07/15/2022	07/15/2022
8.322.x	01/15/2022	04/15/2022	04/15/2022
8.342.x	07/15/2022	10/15/2022	10/15/2022
8.352.x	10/18/2022	01/15/2023	01/15/2023
8.362.x	02/02/2023	04/15/2023	04/15/2023
8.363.x		07/15/2023	07/15/2023
8.372.x		07/15/2023	07/15/2023
8.382.x		10/15/2023	10/15/2023
8.392.x	10/17/2023
8.412.x	04/16/2024
11.0.5.x	10/14/2019	01/15/2020	01/15/2020
11.0.6.x	01/15/2020	04/15/2020	04/15/2020
11.0.7.x	04/14/2020	07/15/2020	07/15/2020
11.0.8.x	07/15/2020	10/20/2020	10/20/2020
11.0.9.x	10/20/2020	01/15/2021	01/15/2021
11.0.10.x	01/15/2021	04/15/2021	04/15/2021
11.0.11.x	04/04/2021	07/15/2021	07/15/2021
11.0.12.x	07/12/2021	10/15/2021	10/15/2021
11.0.13.x	10/15/2021	01/15/2022	01/15/2022
11.0.14.x	01/15/2022	04/15/2022	04/15/2022
11.0.15.x	04/15/2022	07/15/2022	07/15/2022
11.0.16.x	07/15/2022	10/15/2022	10/15/2022
11.0.17.x	10/15/2022	01/15/2023	01/15/2023
11.0.18.x	02/02/2023	04/15/2023	04/15/2023
11.0.19.x		07/15/2023	07/15/2023
11.0.20.x		10/15/2023	10/15/2023
11.0.21.x	10/17/2023	01/15/2024	01/15/2024
11.0.22.x
11.0.23.x	04/16/2024
17.0.0.x	09/14/2021	01/15/2021	01/15/2021
17.0.1.x	10/19/2021	01/15/2021	01/15/2021
17.0.2.x	01/15/2022	04/15/2022	04/15/2022
17.0.3.x	04/15/2022	07/15/2022	07/15/2022
17.0.4.x	07/15/2022	10/15/2022	10/15/2022
17.0.5.x	10/15/2022	01/15/2023	01/15/2023
17.0.6.x	01/17/2023	04/15/2023	04/15/2023
17.0.7.x		07/15/2023	07/15/2023
17.0.8.x		10/15/2023	10/15/2023
17.0.9.x		01/15/2024	01/15/2024
17.0.10.x
17.0.11.x	04/16/2024
19.0.x (non-LTS)	10/18/2022	04/15/2023	04/15/2023
20.0.x (non-LTS)	03/21/2023	10/15/2023	10/15/2023
21.x	08/25/2023

Current Decision Matrix (06/17/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2028

CY2029

CY2030

Future>

Release

8.232.x

Unapproved

8.242.x

Unapproved

8.252.x

Unapproved

8.262.x

Unapproved

8.265.x

Unapproved

8.272.x

Unapproved

8.275.x

Unapproved

8.282.x

Unapproved

8.292.x

Unapproved

8.302.x

Unapproved

8.312.x

Unapproved

8.303.x

Unapproved

8.322.x

Unapproved

8.332.x

Unapproved

8.342.x

Unapproved

8.352.x

Unapproved

8.362.x

Unapproved

8.363.x

Unapproved

8.372.x

Unapproved

8.382.x

Unapproved

8.392.x

Unapproved

8.412.x

Approved w/Constraints
[4, 8, 10, 11, 12]

11.0.5.x

Unapproved

11.0.6.x

Unapproved

11.0.7.x

Unapproved

11.0.8.x

Unapproved

11.0.9.x

Unapproved

11.0.10.x

Unapproved

11.0.11.x

Unapproved

11.0.12.x

Unapproved

11.0.13.x

Unapproved

11.0.14.x

Unapproved

11.0.15.x

Unapproved

11.0.16.x

Unapproved

11.0.17.x

Unapproved

11.0.18.x

Unapproved

11.0.19.x

Unapproved

11.0.20.x

Unapproved

11.0.21.x

Unapproved

11.0.22.x

Unapproved

11.0.23.x

Approved w/Constraints
[4, 8, 10, 11, 12]

17.0.0.x

Unapproved

17.0.1.x

Unapproved

17.0.2.x

Unapproved

17.0.3.x

Unapproved

17.0.4.x

Unapproved

17.0.5.x

Unapproved

17.0.6.x

Unapproved

17.0.7.x

Unapproved

17.0.8.x

Unapproved

17.0.9.x

Unapproved

17.0.10.x

Unapproved

17.0.11.x

Approved w/Constraints
[4, 8, 10, 11, 12]

19.0.x (non-LTS)

Unapproved

20.0.x (non-LTS)

Unapproved

21.x

Approved w/Constraints
[4, 8, 10, 11, 12]

Decision Constraints


[1]	This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population.

[2]	Due to major security vulnerabilities associated with JDK, only the current supported patch sets, which are released every 3 months, are approved for use and the prior patch set will be divested for one quarter to allow time for transition. Note: It is the system owner`s responsibility to ensure proper licensing is obtained and in place for Java patches that are installed on machines they own. Care should be taken to test and minimize product interaction where this technology is used on the same machine with other vendor`s JDK implementations. Security Engineering (SE) conducted a pre-assessment and security requirements verification of Amazon Corretto. It is advised that if this product is used within the VA the following constraints be applied: 1. If VA sensitive information is involved, ensure that the underlying infrastructure and application are configured to provide FIPS 140-2 encryption for web access supporting Amazon Corretto to provide the VA required FIPS 140-2 compliant cryptographic modules for encryption of data at rest and in transit. 2. Due to frequent changes to the lifecycle, system administrators must ensure that the supported version is being used. 3. VA already has an AWS Support Plan, it must be verified that Corretto is covered on the plan the VA currently has; otherwise, it is recommended that the VA purchase a plan to receive assistance with Corretto. 4. Corretto should be administered only by the Desktop and Device Engineering team with access to this product restricted and limited to privileges that are needed to perform specific duties. Also audit logs should be reviewed in accordance with VA Handbook 6500, Continuous Monitoring standards. 5. It is strongly recommended that these patches are prioritized, tested, and installed as soon as they become available. The product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Due to major security vulnerabilities associated with JDK, only the current supported patch sets, which are released every 3 months, are approved for use and the prior patch set will be divested for one quarter to allow time for transition. Note: It is the system owner`s responsibility to ensure proper licensing is obtained and in place for Java patches that are installed on machines they own. Care should be taken to test and minimize product interaction where this technology is used on the same machine with other vendor`s JDK implementations. Security Engineering (SE) conducted a pre-assessment and security requirements verification of Amazon Corretto. It is advised that if this product is used within the VA the following constraints be applied: 1.Amazon Corretto will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. 2. VA already has an AWS Support Plan, it must be verified that Corretto is covered on the plan the VA currently has; otherwise, it is recommended that the VA purchase a plan to receive assistance with Corretto. 3.Corretto should be administered only by the Desktop and Device Engineering team with access to this product restricted and limited to privileges that are needed to perform specific duties. Also audit logs should be reviewed in accordance with VA Handbook 6500, Continuous Monitoring standards. 4. It is strongly recommended that these patches are prioritized, tested, and installed as soon as they become available.

[7]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[8]	Due to major security vulnerabilities associated with JDK, only the current supported patch sets, which are released every 3 months, are approved for use and the prior patch set will be divested for one quarter to allow time for transition. Note: It is the system owner`s responsibility to ensure proper licensing is obtained and in place for Java patches that are installed on machines they own. Care should be taken to test and minimize product interaction where this technology is used on the same machine with other vendor`s JDK implementations. Per the Initial Product Review, users must abide by the following constraints: Amazon Corretto will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. VA already has an AWS Support Plan, it must be verified that Corretto is covered on the plan the VA currently has; otherwise, it is recommended that the VA purchase a plan to receive assistance with Corretto. Corretto should be administered only by the Desktop and Device Engineering team with access to this product restricted and limited to privileges that are needed to perform specific duties. Also audit logs should be reviewed in accordance with VA Handbook 6500, Continuous Monitoring standards. It is strongly recommended that these patches are prioritized, tested, and installed as soon as they become available.

[9]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[11]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[12]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

Note:

At the time of writing, version 8.412.08.1 (1.8.0412) is the most current version, released 04/16/2024.
The Most Current Server Versions are 11.0.23.91, 17.0.11.9.1, and 21.0.3.9.1.
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 8.412.08.1 (1.8.0.412).

The Server versions are not included in the DDE standard. Update to the most current Long Time Support (LTS) version that is included with the package.
NOTE: Versions undergoing evaluation may not be released for production at time of TRM review. Information was included to anticipate/capture future releases for planning and migration. Java 7 became unsupported on 7/22/2022 and is TRM unapproved. Due to major security vulnerabilities associated with this technology, only the current supported patch sets, which are released every 3 months, are approved for use and the prior patch set will be divested for one quarter to allow time for transition. Java 12, 13, 14, 15, 16, 18, 19, and 20 are not long term supported releases and only have 6 month lifecycles. These versions will not be approved in VA.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.


Application Technology Development Tools	Development Frameworks

- The information contained on this page is accurate as of the Decision Date (06/21/2024 at 22:00:33 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/17/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/17/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES