AWS m2 documentation change
Summary
Consolidated documentation by removing 'non-managed' and 'Developer' runtime distinctions. Removed detailed S3 bucket access information and added artifact table with component details. Fixed typo in 'certified'.
Security assessment
No security vulnerabilities or weaknesses are addressed. Changes involve documentation restructuring and content removal (e.g., S3 bucket naming conventions/access details), but no evidence of security incident response or vulnerability patching. Removal of access details doesn't introduce security risks.
Diff
diff --git a/m2/latest/userguide/ba-runtime-artifacts.md b/m2/latest/userguide/ba-runtime-artifacts.md index c06eeb6ba..6c02f16bf 100644 --- a//m2/latest/userguide/ba-runtime-artifacts.md +++ b//m2/latest/userguide/ba-runtime-artifacts.md @@ -5 +5 @@ -AWS Blu Age Runtime (non-managed) artifactsDeveloper AWS Blu Age Runtime artifacts +AWS Blu Age Runtime artifacts @@ -13,17 +13 @@ AWS Blu Age Runtime artifacts are the components for deploying and running moder -## 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 ](./ba-runtime-setup-onboard.html). +## AWS Blu Age Runtime artifacts @@ -37,9 +21 @@ In both Release and Pre-release buckets, you'll find: -This archive, where x.y.z represents the version number (`major.minor.patch` as per semantic versioning, see [AWS Blu Age versioning](./ba-versioning.html)), and contains the core AWS Blu Age Runtime components essential for executing AWS Blu Age applications, including: - - * **Gapwalk** : A crucial component of the AWS Blu Age Runtime, designed to bridge the gap between legacy applications and modern cloud-native environments. It serves as a compatibility layer that allows applications modernized by AWS Blu Age to run effectively on contemporary platforms. - - * **bluage.bin** : The core binary file of the AWS Blu Age Runtime. This file is critical for the operation of the runtime. - - * All necessary libraries and supporting files for the AWS Blu Age Runtime operation. - - +This archive, where x.y.z represents the version number (see [AWS Blu Age versioning](https://docs.aws.amazon.com/m2/latest/userguide/ba-versioning.html)), contains the core AWS Blu Age Runtime components essential for executing AWS Blu Age applications, including: @@ -46,0 +23,6 @@ This archive, where x.y.z represents the version number (`major.minor.patch` as +Artifact | Description | Type | Distribution Folder +---|---|---|--- +gapwalk-application-x.y.z.war | Blu Age main web application **Gapwalk** | War | webapps +*.jar | Blu Age Runtime Framework **Shared Libraries** (Gapwalk) | Jars | shared +gapwalk-*-x.y.z.war | Blu Age additional web applications **(utility-pgm, hierarchical support, ... )** | War | webapps-extra +bac-x.y.z.war / jac-x.y.z.war | Blu Age **Administration Consoles (non-standalone)** | War | webapps-consoles @@ -50 +32 @@ This archive, where x.y.z represents the version number (`major.minor.patch` as -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: +This archive, where x.y.z follows the same versioning scheme as above, includes Blu Age Administration Consoles (standalone) @@ -69 +51 @@ To verify the signature of the ZIP file before using it, you can use the followi -Here the result example for a cerfified file : +Here the result example for a certified file : @@ -81,20 +62,0 @@ While we strive to release our products without CVEs, new CVEs may appear later -## 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](https://bluinsights.aws/docs/bluage-toolbox-introduction) 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. -