As much as you want. The only limit is the number of projects you are allowed to create on AWS Blu Insights (see your profile).
A user can maintain up to 50 runs per project.
You can specify the permission of a Transformation project by updating the permissions of the codebase project since the transformation center inherits all the permissions of the Codebase project. Regarding the modules Inputs and Velocity, we grant all permissions for all members of the project.
We prevent the actions of download, if the role you are using prevents the Download action.
To invite a user to a Transformation project, you need to first invite them in the referenced codebase project, and grant them the permission to access the Assets module in the referenced codebase project. See How to create a Transformation project.
Eligible invitees include:
Members of the AWS Blu Insights codebase project with asset permissions.
Members with full access to all modules in the AWS Blu Insights codebase.
Only individuals with approved AWS Blu Insights accounts and explicit project invitations can access a project.
The most recent 100 Velocity versions are available in the Transformation Center service.
Every day, two new Velocity versions are released. Only the latest 100 versions of Velocity are available in the Transformation Center service.
If a run fails, you may need information to understand why. The first thing to do is to check the logs of the failed action. To do so, just check the concerned action (one marked as failed) and click on “View Log”. In most of the cases, the information you need will be at the end of the log file. Note that when an action fails, all the next ones will be “Aborted”. If the previous step does not help you solving the issue. You may try to relaunch the entire run. The section Re-launch run of the page Velocity Runs contains more information about this.
This icon appears when your project is no more supported by Velocity, i.e. does not contain anymore legacy source code file that can be transformed (see more on Create a Transformation project).
You might not find the codebase project you are looking for into the Codebase reference projects list if:
You might see this warning in the following cases:
The issues view is only displayed when you have selected some issues from your runs. See more on Transformation Center Issues.
You have reached the limit set by your AWS Blu Insights role (linked to certification level). You can click on your avatar in the upper right corner to show the menu and see the limit.
No. Only L3 Certified are allowed to generate the source code. If you are L2 Certified, you can download the Weather Report which is sufficient for the Assessment phase.
The ability to generate the source code depends on both your and the project Executive's roles and permissions. If a Run cannot be initiated, the following restrictions apply:
In order to improve billing security and to avoid any unwanted billings. Weather report is enabled by default for billable projects only. To launch a non weather report run, click on the toggle to disable it.
Comments in the legacy code are fully preserved and integrated into the modernized code using advanced heuristics. These heuristics ensure comments are appropriately placed, whether as Javadoc or standard comment lines. Retaining comments is critical as they often contain valuable details about business logic and program history.
The most effective approach is to use the Refactoring Toolbox. Create a custom refactoring script tailored to the desired naming convention. Apply this script during the transformation phase within the Transformation Center. Training on creating, testing, and executing custom refactorings is available through the AWS Blu Age certification cursus.
The refactoring process generates two key files for each legacy program:
These files are written in a dedicated domain-specific language (DSL).
No, AWS CLI is not supported for AWS Blu Insights Transformation Center.