AWS Transform for mainframe refactor

General

Do I need to log in to the AWS console to use AWS Transform for mainframe refactor?

Yes.

Do team members have to use the same AWS account ID?

No.

How to enter AWS Transform for mainframe refactor from the AWS Console?

1. Log in to the AWS Console    
2. Navigate to AWS Transform service    
3. In Transformation paths, click on “Launch refactor”

Here is a recording guiding you through the first SSO access with an AWS Account/Role combination that hasn’t yet accessed AWS Transform for mainframe refactor:

And this one shows the SSO access for approved accounts:

How to migrate a legacy AWS Transform for mainframe refactor account to SSO?

AWS Transform for mainframe refactor will detect if the entered email is linked to a legacy account and will guide you through to migrate to SSO. You will receive an email asking you to confirm that you want to link your legacy account to the concerned AWS Account and role.

Here is a recording guiding you through the process:

No. For each AWS account, you will create a new refactor environment. Remember, the AWS account used for the environment will be charged for Transformation Center usage. To work with multiple AWS accounts on AWS Transform for mainframe refactor, we recommend to go for one of these two options:

  • Use emails following this pattern: <<alias>>+<<AWS account ID>>@<<domain>> (if your domain email server allows it).
  • Request email addresses with the domains of the customers you are working with: (e.g. <<alias>>@<<customer-1-domain>> and <<alias>>@<<customer-2-domain>>).

I have one AWS account. Can I have multiple AWS Transform for mainframe refactor environments on it?

Yes. One AWS Transform for mainframe refactor environment can be created for every role on the account.

AWS Transform for mainframe refactor does not open when I try to access it from the console (the new tab is instantly closed). What can I do?

First, make sure you are in an AWS region where the AWS Transform for mainframe refactor service is available. Then, make sure that the role you are using on your AWS account has an IAM Policy that allows it to access AWS Transform for mainframe refactor.    
The role you are using should at least have the permissions of the following statement:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "m2:GetSignedBluinsightsUrl"
            ],
            "Resource": "arn:aws:m2:{region}:{account}:*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "transform:GetWebAppUrl"
            ],
            "Resource": "*"
        }
    ]
}

with your own values for {region} and {account}.

Why does AWS Transform for mainframe refactor ask for an email?

AWS Transform for mainframe refactor will use that email address to provide updates on your ongoing modernization projects. As different AWS Transform for mainframe refactor users can use from the same AWS Account, the address of the AWS Account can’t be used for this purpose.

Do I have to use the same email to log in to the AWS Console and to enter AWS Transform for mainframe refactor?

No, you don’t.

How do I update my name?

Update your Profile in a snap! Click on your avatar in the upper right corner of AWS Transform for mainframe refactor and in order to edit your information, select Profile in Menu.

Why does my account get disabled?

For security reasons, we disable inactive accounts. Although AWS Transform for mainframe refactor alerts you prior to disable your account. If you need to re-activate it, please follow the instruction when trying to log-in.

My account has not been validated. What should I do?

Please create an AWS Support case with you email and AWS account ID.

How does the SSO work from the AWS Console to AWS Transform for mainframe refactor?

It involves JWT tokens that are encrypted and decrypted by the console and AWS Transform for mainframe refactor using AWS KMS.

Can I access AWS Transform for mainframe refactor using the AWS CLI?

Yes, use the get-signed-bluinsights-url CLI command for this. For example the aws m2 get-signed-bluinsights-url --region eu-west-3 command will get a you an SSO URL to AWS Transform for mainframe refactor in eu-west-3.

If different users access AWS Transform for mainframe refactor by assuming the same role with different role session names, will they all have their own refactor environment?

Yes, there will be one AWS Transform for mainframe refactor environment for every role session name.

Can I use a personal email to register to AWS Transform for mainframe refactor?

No.

How can I control the list of invited individuals in my projects?

Use Profiles to control who can invite other members.

I have lost access to my AWS account. How can I connect to my AWS Transform for mainframe refactor?

You can gain back access to AWS Transform for mainframe refactor by following one of these two options:

  • Request to unlink your AWS account by contacting the support. After your accounts are unlinked, you can log in to AWS Transform for mainframe refactor from your new AWS account. Notice, this is not possible if you have ongoing billable Transformation Center projects.
  • Create a new AWS Transform for mainframe refactor account. Use emails following this pattern: <<alias>>+<<AWS account ID>>@<<domain>> (if your domain email server allows it).

 

How long is my AWS Transform for mainframe refactor session?

AWS Transform for mainframe refactor sessions have a limited duration to ensure security. Users will receive a warning message before their session expires, allowing them to save their work. For security reasons, we recommend always logging out when you've finished your work.