Infrastructure setup requirements for AWS Blu Age Runtime (non-managed)

This topic describes the minimum infrastructure configuration required to run AWS Blu Age Runtime (non-managed). The following procedures describe how to set up AWS Blu Age Runtime (non-managed) on your compute of choice to deploy a modernized application on the AWS Blu Age Runtime. The resources that you create must be in an Amazon VPC that has a subnet that is dedicated to your application domain.

Infrastructure requirements

Create a security group

If you plan to work on Amazon EC2 instances on Amazon EKS, skip this procedure because the Amazon EKS cluster creation process creates a security group on your behalf. Use that security group in the following procedures instead of creating a new one.

1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

2. In the left navigation pane, under Security, choose Security groups.

3. In the central pane, choose Create security group.

4. In the Security group name field, enter M2BluagePrivateLink-SG.

5. In the Inbound rules section, choose Add rule.

6. For Type, choose HTTPS.

7. For Source enter your VPC CIDR.

8. In the Outbound rules section, choose Add rule.

9. For Type, choose HTTPS.

10. For Destination, enter 0.0.0.0/0.

11. Choose Create security group.

Create an Amazon VPC endpoint

1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

2. In the left navigation pane, under Virtual private cloud, choose Endpoints.

3. In the central pane, choose Create endpoint.

4. In the Services section, enter SQS in the search field, and then select the Amazon SQS service that corresponds to your Region.

5. In the VPC section, select the Amazon VPC that you created in the previous step.

6. In the Subnets section, select the subnet that you created for your application domain.

7. In the Security groups section, select the security group from the previous procedure.

8. Choose Create endpoint.

Create an IAM policy

1. Open the IAM console at https://console.aws.amazon.com/iam/.

2. In the left navigation pane, under Access management, choose Policies.

3. In the central pane, choose Create policy.

4. In the Policy editor section, choose JSON.

5. Replace all of the JSON that you see in the editor with the following JSON.

   JSON

   {
       "Version":"2012-10-17",		 	 	 
       "Statement": [
           {
               "Sid": "VisualEditor0",
               "Effect": "Allow",
               "Action": [
                   "sqs:GetQueueUrl",
                   "sqs:ReceiveMessage",
                   "sqs:SendMessage"
               ],
               "Resource": "*"
           }
       ]
   }
   

   Note

   If you need further details to customize your policy, contact your AWS Blu Age delivery manager or account manager.

6. Choose Next.

7. Enter a name for the policy, then choose Create policy.

Create an IAM role

1. Open the IAM console at https://console.aws.amazon.com/iam/.

2. In the left navigation pane, under Access management, choose Roles.

3. In the central pane, choose Create role.

4. In the Use case section, depending on your compute choice, choose one of the following:

   • EC2 (for Amazon EC2 and Amazon EKS on Amazon EC2)

   • Elastic Container Service and then EC2 Role for Elastic Container Service (for Amazon ECS on Amazon EC2)

   • Elastic Container Service and then Elastic Container Service Task (for Amazon ECS managed by Fargate)

5. Choose Next.

6. In the search box, enter the name of the policy that you created earlier.

7. Select the checkbox to the left of your policy.

   Note

   If you can't add a policy, finish creating the role and then update the role to add the policy.

8. Choose Next.

9. Enter a name for the role, then choose Create role.

Amazon EC2 instance types for AWS Blu Age Runtime (on Amazon EC2)

The following is a list of the Amazon EC2 instance types that you can use for AWS Blu Age Runtime (on Amazon EC2) when creating Amazon EC2 instances or when defining Amazon EKS worker nodes.

Check that the instance of your interest is available in the desired region you plan to deploy.

t3.small
t3.medium
t3.large
t3.xlarge
t3.2xlarge
t2.small
t2.medium
t2.large
t2.xlarge
t2.2xlarge
r7a.medium
r7a.large
r7a.xlarge
r7a.2xlarge
r7a.4xlarge
r7a.8xlarge
r7a.12xlarge
r7a.16xlarge
r7a.24xlarge
r7a.32xlarge
r7a.48xlarge
r7a.metal-48xl
r7i.large
r7i.xlarge
r7i.2xlarge
r7i.4xlarge
r7i.8xlarge
r7i.12xlarge
r7i.16xlarge
r7i.24xlarge
r7i.48xlarge
r7i.metal-24xl
r7i.metal-48xl
r6i.xlarge
r6i.large
r6i.4xlarge
r6i.2xlarge
r5b.xlarge
r5b.large
r5b.2xlarge
r3.xlarge
m6i.xlarge
m6i.large
m6i.8xlarge
m6i.4xlarge
m6i.2xlarge
m6i.16xlarge
m5zn.xlarge
m5zn.large
m5zn.3xlarge
m5zn.2xlarge
m5.xlarge
m5.large
m5.8xlarge
m5.4xlarge
m5.2xlarge
m5.16xlarge
m5.12xlarge
c6i.xlarge
c6i.large
c6i.8xlarge
c6i.4xlarge
c6i.2xlarge
c6i.16xlarge
c5.xlarge
c5.large
c5.9xlarge
c5.4xlarge
c5.2xlarge
c5.18xlarge
c5.12xlarge

Running AWS Blu Age Runtime on Amazon EC2

To create an Amazon EC2 instance, use the following steps.

Create an Amazon EC2 instance

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. Choose Launch instance.

3. For Instance type, choose one of the types listed in Amazon EC2 instance types for AWS Blu Age Runtime (on Amazon EC2).

4. In the Key pair section, either choose an existing key pair or create a new one.

5. In the Network settings section, choose Select existing security group.

6. For Common security groups, choose M2BluagePrivateLink-SG.

7. Expand the Advanced details section.

8. For IAM instance profile, choose the IAM role that you created earlier.

9. Choose Launch instance.

Install the application on the Amazon EC2 instance

1. When the state of the Amazon EC2 instance changes to Running, connect to the instance.

2. Install the following software components on the instance:

   • Java Runtime Environment (JRE) 17.

   • Apache Tomcat 10.

   • AWS Blu Age Runtime (on Amazon EC2). Install the AWS Blu Age runtime at the root of Apache Tomcat installation folder (some files will be added while others will be overwritten).

   To install the additional webapps delivered alongside the AWS Blu Age Runtime archive, set up a secondary instance of the Apache Tomcat server, and decompress the webapps archive at that location. For detailed instructions, see AWS Blu Age Runtime artifacts.

Running AWS Blu Age Runtime on Amazon ECS on Amazon EC2

1. Create an Amazon ECS cluster, with Amazon EC2 instances as an underlying infrastructure. See Getting started with Windows on Amazon EC2 in the Amazon Elastic Container Service Developer Guide.

2. Specify the IAM role that you created in the previous steps.

3. Choose one of the instance types listed in Amazon EC2 instance types for AWS Blu Age Runtime (on Amazon EC2).

4. In Network settings for Amazon EC2 instances, choose the security group that you created in the previous steps.

Running AWS Blu Age Runtime on Amazon EKS on Amazon EC2

1. Create an Amazon EKS cluster. See Creating an Amazon EKS cluster in the Amazon EKS User Guide.

2. As mentioned previously, a security group is created on your behalf. You can use that security group when you create the Amazon VPC endpoint.

3. Create a node group. Specify the IAM role that you created in the previous steps.

4. Choose one of the instance types listed in Amazon EC2 instance types for AWS Blu Age Runtime (on Amazon EC2).

5. Amazon EKS will automatically assign the security group to the spawned Amazon EC2 instances.

Running AWS Blu Age Runtime on Amazon ECS managed by AWS Fargate

Create an Amazon ECS cluster with AWS Fargate (serverless) as an underlying infrastructure. See Getting started with Fargate in the Amazon Elastic Container Service Developer Guide.