Chapter 3. Deploying a RHEL image as an EC2 instance on AWS

Verification

1. Verify the installation:

   $ aws --version

   aws-cli/1.19.77 Python/3.6.15 Linux/5.14.16-201.fc34.x86_64 botocore/1.20.77

2. Configure awscli2 for AWS credentials and settings:

   $ aws configure

   AWS Access Key ID [None]:
   AWS Secret Access Key [None]:
   Default region name [None]:
   Default output format [None]:

Procedure

1. Run qemu-img to convert .qcow2 image to .raw image format:

   # qemu-img convert -f qcow2 -O raw rhel-10.0-sample.qcow2 rhel-10.0-sample.raw

2. Upload the image to the Amazon S3 bucket:

   $ aws s3 cp rhel-10.0-sample.raw s3://<example-s3-bucket-name>

Procedure

1. Use the vmimport role:

   $ aws iam create-role --role-name vmimport \
   --assume-role-policy-document file://<example_vmimport_trust_policy_file>

2. Embed an inline policy document by using the vmimport role policy file:

   $ aws iam put-role-policy --role-name vmimport \
   --policy-name vmimport-access \
   --policy-document file://<example_vmimport_role_policy_file>

   Also, you can grant VM Import/Export permissions by creating an IAM role (often named vmimport) with a trust policy for vmie.amazonaws.com and attaching the JSON policy from the AWS guide.

3. Import RHEL image as a snapshot:

   $ aws ec2 import-snapshot --disk-container file://<example_containers_json_file>

4. Confirm that the snapshot import finished successfully with the completed status:

   $ aws ec2 describe-import-snapshot-tasks --import-task-ids <example_import_task_id>

   You can import a RHEL VM image from Amazon S3 as a snapshot to Amazon EC2. Prepare a <example_containers_json_file> file that points to your S3 bucket and object key, then start the import and monitor the task ID that the command returns.

5. Register a RHEL AMI from the completed snapshot:

   $ aws ec2 register-image \
   --name <example_rhel_custom_ami_name> \
   --architecture x86_64 \
   --virtualization-type hvm \
   --root-device-name /dev/sda1 \
   --block-device-mappings "[{\"DeviceName\": \"/dev/sda1\",\"Ebs\": {\"SnapshotId\": \"<example_snapshot_id>\"}}]" \
   --ena-support

6. Create a key pair for the RHEL EC2 instance:

   $ aws ec2 create-key-pair --key-name <example_key_pair_name> \
   --query 'KeyMaterial' --output text > <example_key_file>.pem

   This key pair is per region and save a .pem file.

7. Restrict permissions on the key file:

   $ chmod 400 <example_key>.pem

8. Launch a RHEL EC2 instance from the registered AMI:

   $ aws ec2 run-instances \
   --image-id <example_registered_ami_id> \
   --instance-type <example_instance_type> \
   --key-name <example_key_pair_name>

9. Connect to the RHEL EC2 instance where the default user is ec2-user:

   $ ssh -i <example_key>.pem ec2-user@<instance_public_dns_or_ip>

Procedure

1. Register your system:

   # subscription-manager register

2. Attach your subscriptions:

   • You can use an activation key to attach subscriptions. For details, see creating Red Hat Customer Portal Activation Keys.
   • Otherwise, you can manually attach a subscription by using the subscription Pool ID attaching a host-based subscription by using Pool ID to hypervisors.

3. Optional: To collect various system metrics about the instance in the Red Hat Hybrid Cloud Console, you can register the instance with Red Hat Lightspeed.

   # insights-client register --display-name <display_name_value>

Procedure

1. Upload the gold image to AWS. For details, see one of the following:

   • Uploading a RHEL image to AWS by using the command line
   • Uploading a RHEL image to AWS by using the AWS console
2. Create VMs by using the uploaded image. If your RHSM settings are correct, they will be automatically subscribed to RHSM.

Procedure

1. Run qemu-img to convert .qcow2 image to .raw image format:

   # qemu-img convert -f qcow2 -O raw rhel-10.0-sample.qcow2 rhel-10.0-sample.raw

2. Upload the image to the S3 bucket by using Amazon S3 console

Procedure

1. Open the AWS Management Console. Search for IAM, open IAM, choose Roles, then choose Create role for vmimport.

2. In the Trusted entity type field, choose Custom trust policy. Paste the vmie.amazonaws.com trust policy from the VM Import/Export documentation, then choose Next.

   Add permissions: skip managed policies if you add an inline VM Import/Export policy next; otherwise attach required policies, then Next.

3. Role name vmimport, Create role.

   In case of adding permissions, open the role. Choose the Permissions tab, choose Add permissions, choose Create inline policy, then choose the JSON tab. Paste the vmimport access policy with your S3 bucket ARNs, then choose Create policy.

4. Open CloudShell from the toolbar or global search.

   In the CloudShell pane, set the Region selector to the same Region as your S3 object.

   At the CloudShell (where the shell accepts aws commands, not the console Search field), enter aws ec2 import-snapshot with your disk container file, then aws ec2 describe-import-snapshot-tasks until the import status is completed.

5. In the Amazon EC2 console, open Elastic Block Store, choose Snapshots, and confirm the snapshot ID.

   On Snapshots, select the snapshot, open Actions, choose Create image from snapshot, then finish the wizard.

6. Open Images, choose AMIs, select the AMI, choose Launch instance from AMI, then finish the wizard.

7. If you need a key pair, choose Network & Security, Key pairs, then Create key pair, and choose .pem.

   Save <example_key>.pem with restrictive file permissions.

8. Choose Instances, select the instance, choose Connect, then open EC2 Instance Connect or SSH client.
9. On the instance, register Red Hat subscriptions.