Migrate Your Identity Router for Amazon Web Services from t2 to t3

This procedure describes how to safely migrate an AWS-hosted Identity Router (IDR) deployment from a t2 instance to a t3 instance. This applies only if you have IDR deployments running on AWS t2 instances. Migration steps are not applicable to new IDR deployments.

Important

Do not change the AWS instance type from t2 to t3 before completing the pre-migration steps (1 to 6 of the following procedure) in the IDR console.

If the pre-migration steps are not completed before changing the instance type, the IDR upgrade can fail. This condition cannot be reversed and may require deployment of a new IDR instance in AWS.

Procedure 

1. Upgrade IDR to the 12.26.x release version and verify that the application is healthy before proceeding.

2. Log in to the IDR console.

3. Navigate to the Setup page.

4. Scroll down to the AWS T2 to T3 Premigration section.

5. Click Create.

6. Verify that the status changes to Ready to migrate from AWS T2 to T3.

   Note:  Do not continue until the status is displayed as Ready to migrate from AWS T2 to T3.
   

7. Log in to the AWS console.

8. Verify that you are connected to the correct AWS account and region.

9. Select the IDR instance and stop it. Wait until all pending operations and status checks are complete.

10. Verify that the instance status is Stopped.

11. Navigate to Actions > Instance settings > Change instance type.

12. Select t3.large, and then click Change instance type. Reopen the instance details and verify that the instance type is displayed as t3.large.

13. Before starting the instance, open AWS CloudShell from the AWS console.

14. Run the following command to enable Elastic Network Adapter (ENA) support:

    aws ec2 modify-instance-attribute --instance-id <instance-id> --ena-support
    

15. Verify ENA support is enabled before starting the instance:

    aws ec2 describe-instances --instance-ids <instance-id> --query 
    'Reservations[0].Instances[0].EnaSupport' --output text
    

16. Start the IDR instance. Verify that the instance returns to the Running state. Verify that both System Status Checks and Instance Status Checks pass successfully.

17. Log in to the IDR console, verify that the application is accessible, core IDR services are running correctly, and no migration or upgrade errors are present.

Troubleshooting

• If the Change instance type option is unavailable, verify that the EC2 instance is completely stopped before attempting to modify the instance type.

• If the AWS CLI command fails, verify that the specified instance ID is correct and that your AWS session has sufficient permissions to modify EC2 instance attributes.

• If IDR does not return to a healthy state after the instance type change, immediately review the IDR application logs and AWS instance status checks.

Next Step

After the migration is complete, perform a full validation of authentication workflows and application integrations to confirm that IDR is operating normally.