AWS Mainframe Modernization Service (Managed Runtime Environment experience) is no longer open to new customers. For capabilities similar to AWS Mainframe Modernization Service (Managed Runtime Environment experience) explore AWS Mainframe Modernization Service (Self-Managed Experience). Existing customers can continue to use the service as normal. For more information, see AWS Mainframe Modernization availability change.

AWS Blu Age Runtime artifacts

AWS Blu Age Runtime artifacts are the components for deploying and running modernized applications. This document outlines the different types of artifacts available, their storage locations, and how to access them.

AWS Blu Age Runtime (non-managed) artifacts

Artifacts access and storage

The AWS Blu Age Runtime artifacts for non-managed deployments are stored in region-specific S3 buckets. Each version has its own dedicated folder, allowing for easy version management and access.

There are two types of buckets:

Release buckets

Release buckets contain directories for the most recently deployed versions and follow the naming convention: aws-bluage-runtime-artifacts-<accountId>-<region>.

Pre-release buckets

Pre-release buckets contain directories for alpha versions corresponding to the latest short-lived incremental pre-releases and follow the naming convention: convention: aws-bluage-runtime-artifacts-dev-<accountId>-<region>.

Access to the Production and to the Pre-release buckets are granted independently. For more information on how to request access, and more details about the S3 bucket organization, see Onboarding AWS Blu Age Runtime .

Artifacts contents

In both Release and Pre-release buckets, you'll find:

aws-bluage-runtime-x.y.z.zip

This archive, where x.y.z represents the version number (major.minor.patch as per semantic versioning, see AWS Blu Age versioning), and contains the core AWS Blu Age Runtime components essential for executing AWS Blu Age applications, including:

aws-bluage-webapps-x.y.z.zip

This archive, where x.y.z follows the same versioning scheme as above, includes web applications and libraries necessary for managing and controlling AWS Blu Age deployments:

Package Signature Verification

The released zip files are provided as digitally signed ZIP archives to ensure security and authenticity. Digital signatures help verify that the files you download are genuine, unaltered, and officially released by our organization. This prevents tampering and protects against malware or compromised files that could be maliciously distributed.

To verify the signature of the ZIP file before using it, you can use the following command:

jarsigner -verify -certs -verbose aws-bluage-runtime-x.y.z.zip

Here the result example for a cerfified file :

...
jar verified.

For details on how security vulnerabilities are addressed, see AWS Mainframe Modernization Refactor with AWS Blu Age release overview.

Developer AWS Blu Age Runtime artifacts

Artifacts access and storage

The AWS Blu Age Developer Runtime artifacts are stored in dedicated S3 buckets. This runtime includes both Release and Alpha pre-release versions. Access to these artifacts is managed through AWS Blu Age toolbox requests. Once your request is processed and approved, you'll be granted access to the appropriate bucket from the AWS account specified in your request.

Developer Runtime bucket

The main bucket for the Developer Runtime is: s3://toolbox-dev-runtime

For more detailed information on requesting access see Blu Age Toolbox documentation.

Artifact contents

Developer runtime artifacts typically include:

gapwalk-x.y.z.zip

This archive contains the development version of the Gapwalk component, which is a crucial part of the AWS Blu Age Runtime. It's designed to bridge legacy applications with modern cloud-native environments.