Chapter 12. Preparing and uploading cloud images by using RHEL image builder RHEL image builder can create custom system images ready for use on various cloud platforms. To use your customized RHEL system image in a cloud, create the system image with RHEL image builder by using the chosen output type, configure your system for uploading the image, and upload the image to your cloud account. You can push customized image clouds through the Image Builder application in the RHEL web console, available for a subset of the service providers that we support, such as AWS and Microsoft Azure clouds. See Creating and automatically uploading images directly to AWS Cloud AMI and Creating and automatically uploading VHD images directly to Microsoft Azure cloud . 12.1. Preparing and uploading AMI images to AWS You can create custom images and can update them, either manually or automatically, to the AWS cloud with RHEL image builder. 12.1.1. Preparing to manually upload AWS AMI images Before uploading an AWS AMI image, you must configure a system for uploading the images. Prerequisites You must have an Access Key ID configured in the AWS IAM account manager . You must have a writable S3 bucket prepared. See Creating S3 bucket . Procedure Install Python 3 and the pip tool: Install the AWS command-line tools with pip : Set your profile. The terminal prompts you to provide your credentials, region and output format: Define a name for your bucket and create a bucket: Replace bucketname with the actual bucket name. It must be a globally unique name. As a result, your bucket is created. To grant permission to access the S3 bucket, create a vmimport S3 Role in the AWS Identity and Access Management (IAM), if you have not already done so in the past: Create a trust-policy.json file with the trust policy configuration, in the JSON format. For example: Create a role-policy.json file with the role policy configuration, in the JSON format. For example: Create a role for your Amazon Web Services account, by using the trust-policy.json file: Embed an inline policy document, by using the role-policy.json file: Additional resources Using high-level (s3) commands with the AWS CLI 12.1.2. Manually uploading an AMI image to AWS by using the CLI You can use RHEL image builder to build ami images and manually upload them directly to Amazon AWS Cloud service provider, by using the CLI. Prerequisites You have an Access Key ID configured in the AWS IAM account manager. You must have a writable S3 bucket prepared. See Creating S3 bucket . You have a defined blueprint. Procedure Using the text editor, create a configuration file with the following content: Replace values in the fields with your credentials for accessKeyID , secretAccessKey , bucket , and region . The IMAGE_KEY value is the name of your VM Image to be uploaded to EC2. Save the file as CONFIGURATION-FILE .toml and close the text editor. Start the compose to upload it to AWS: Replace: blueprint-name with the name of the blueprint you created image-type with the ami image type. image-key with the name of your VM Image to be uploaded to EC2. configuration-file .toml with the name of the configuration file of the cloud provider. Note You must have the correct AWS Identity and Access Management (IAM) settings for the bucket you are going to send your customized image to. You have to set up a policy to your bucket before you are able to upload images to it. Check the status of the image build: After the image upload process is complete, you can see the "FINISHED" status. Verification To confirm that the image upload was successful: Access EC2 on the menu and select the correct region in the AWS console. The image must have the available status, to indicate that it was successfully uploaded. On the dashboard, select your image and click Launch . Additional Resources Required service role to import a VM 12.1.3. Creating and automatically uploading images to the AWS Cloud AMI You can create a (.raw) image by using RHEL image builder, and choose to check the Upload to AWS checkbox to automatically push the output image that you create directly to the Amazon AWS Cloud AMI service provider. Prerequisites You must have root or wheel group user access to the system. You have opened the RHEL image builder interface of the RHEL web console in a browser. You have created a blueprint. See Creating a blueprint in the web console interface . You must have an Access Key ID configured in the AWS IAM account manager. You must have a writable S3 bucket prepared. Procedure In the RHEL image builder dashboard, click the blueprint name that you previously created. Select the tab Images . Click Create Image to create your customized image. The Create Image window opens. From the Type drop-down menu list, select Amazon Machine Image Disk (.raw) . Check the Upload to AWS checkbox to upload your image to the AWS Cloud and click . To authenticate your access to AWS, type your AWS access key ID and AWS secret access key in the corresponding fields. Click . Note You can view your AWS secret access key only when you create a new Access Key ID. If you do not know your Secret Key, generate a new Access Key ID. Type the name of the image in the Image name field, type the Amazon bucket name in the Amazon S3 bucket name field and type the AWS region field for the bucket you are going to add your customized image to. Click . Review the information and click Finish . Optionally, click Back to modify any incorrect detail. Note You must have the correct IAM settings for the bucket you are going to send your customized image. This procedure uses the IAM Import and Export, so you have to set up a policy to your bucket before you are able to upload images to it. For more information, see Required Permissions for IAM Users . A pop-up on the upper right informs you of the saving progress. It also informs that the image creation has been initiated, the progress of this image creation and the subsequent upload to the AWS Cloud. After the process is complete, you can see the Image build complete status. In a browser, access Service->EC2 . On the AWS console dashboard menu, choose the correct region . The image must have the Available status, to indicate that it is uploaded. On the AWS dashboard, select your image and click Launch . A new window opens. Choose an instance type according to the resources you need to start your image. Click Review and Launch . Review your instance start details. You can edit each section if you need to make any changes. Click Launch Before you start the instance, select a public key to access it. You can either use the key pair you already have or you can create a new key pair. Follow the steps to create a new key pair in EC2 and attach it to the new instance. From the drop-down menu list, select Create a new key pair . Enter the name to the new key pair. It generates a new key pair. Click Download Key Pair to save the new key pair on your local system. Then, you can click Launch Instance to start your instance. You can check the status of the instance, which displays as Initializing . After the instance status is running , the Connect button becomes available. Click Connect . A window appears with instructions on how to connect by using SSH. Select A standalone SSH client as the preferred connection method to and open a terminal. In the location you store your private key, ensure that your key is publicly viewable for SSH to work. To do so, run the command: Connect to your instance by using its Public DNS: Type yes to confirm that you want to continue connecting. As a result, you are connected to your instance over SSH. Verification Check if you are able to perform any action while connected to your instance by using SSH. Additional resources Open a case on Red Hat Customer Portal Connecting to your Linux instance by using SSH 12.2. Preparing and uploading VHD images to Microsoft Azure You can create custom images and can update them, either manually or automatically, to the Microsoft Azure cloud with RHEL image builder. 12.2.1. Preparing to manually upload Microsoft Azure VHD images To create a VHD image that you can manually upload to Microsoft Azure cloud, you can use RHEL image builder. Prerequisites You must have a Microsoft Azure resource group and storage account. You have Python installed. The AZ CLI tool depends on python. Procedure Import the Microsoft repository key: Create a local azure-cli.repo repository with the following information. Save the azure-cli.repo repository under /etc/yum.repos.d/ : Install the Microsoft Azure CLI: Note The downloaded version of the Microsoft Azure CLI package can vary depending on the current available version. Run the Microsoft Azure CLI: The terminal shows the following message Note, we have launched a browser for you to login. For old experience with device code, use "az login --use-device-code . Then, the terminal opens a browser with a link to https://microsoft.com/devicelogin from where you can login. Note If you are running a remote (SSH) session, the login page link will not open in the browser. In this case, you can copy the link to a browser and login to authenticate your remote session. To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the device code to authenticate. List the keys for the storage account in Microsoft Azure: Replace resource-group-name with name of your Microsoft Azure resource group and storage-account-name with name of your Microsoft Azure storage account. Note You can list the available resources using the following command: Make note of value key1 in the output of the command. Create a storage container: Replace storage-account-name with name of the storage account. Additional resources Microsoft Azure CLI. 12.2.2. Manually uploading VHD images to Microsoft Azure cloud After you have created your customized VHD image, you can manually upload it to the Microsoft Azure cloud. Prerequisites Your system must be set up for uploading Microsoft Azure VHD images. See Preparing to upload Microsoft Azure VHD images . You must have a Microsoft Azure VHD image created by RHEL image builder. In the GUI, use the Azure Disk Image (.vhd) image type. In the CLI, use the vhd output type. Procedure Push the image to Microsoft Azure and create an instance from it: After the upload to the Microsoft Azure Blob storage completes, create a Microsoft Azure image from it: Note Because the images that you create with RHEL image builder generate hybrid images that support to both the V1 = BIOS and V2 = UEFI instances types, you can specify the --hyper-v-generation argument. The default instance type is V1. Verification Create an instance either with the Microsoft Azure portal, or a command similar to the following: Use your private key via SSH to access the resulting instance. Log in as azure-user . This username was set on the step. Additional Resources Composing an image for the .vhd format fails (Red Hat Knowledgebase) 12.2.3. Creating and automatically uploading VHD images to Microsoft Azure cloud You can create .vhd images by using RHEL image builder that will be automatically uploaded to a Blob Storage of the Microsoft Azure Cloud service provider. Prerequisites You have root access to the system. You have access to the RHEL image builder interface of the RHEL web console. You created a blueprint. See Creating a RHEL image builder blueprint in the web console interface . You have a Microsoft Storage Account created. You have a writable Blob Storage prepared. Procedure In the RHEL image builder dashboard, select the blueprint you want to use. Click the Images tab. Click Create Image to create your customized .vhd image. The Create image wizard opens. Select Microsoft Azure (.vhd) from the Type drop-down menu list. Check the Upload to Azure checkbox to upload your image to the Microsoft Azure Cloud. Enter the Image Size and click . On the Upload to Azure page, enter the following information: On the Authentication page, enter: Your Storage account name. You can find it on the Storage account page, in the Microsoft Azure portal . Your Storage access key : You can find it on the Access Key Storage page. Click . On the Authentication page, enter: The image name. The Storage container . It is the blob container to which you will upload the image. Find it under the Blob service section, in the Microsoft Azure portal . Click . On the Review page, click Create . The RHEL image builder and upload processes start. Access the image you pushed into Microsoft Azure Cloud . Access the Microsoft Azure portal . In the search bar, type "storage account" and click Storage accounts from the list. On the search bar, type "Images" and select the first entry under Services . You are redirected to the Image dashboard . On the navigation panel, click Containers . Find the container you created. Inside the container is the .vhd file you created and pushed by using RHEL image builder. Verification Verify that you can create a VM image and launch it. In the search bar, type images account and click Images from the list. Click +Create . From the dropdown list, choose the resource group you used earlier. Enter a name for the image. For the OS type , select Linux . For the VM generation , select Gen 2 . Under Storage Blob , click Browse and click through the storage accounts and container until you reach your VHD file. Click Select at the end of the page. Choose an Account Type, for example, Standard SSD . Click Review + Create and then Create . Wait a few moments for the image creation. To launch the VM, follow the steps: Click Go to resource . Click + Create VM from the menu bar on the header. Enter a name for your virtual machine. Complete the Size and Administrator account sections. Click Review + Create and then Create . You can see the deployment progress. After the deployment finishes, click the virtual machine name to retrieve the public IP address of the instance to connect by using SSH. Open a terminal to create an SSH connection to connect to the VM. Additional resources Microsoft Azure Storage Documentation Create a Microsoft Azure Storage account Open a case on Red Hat Customer Portal Help + support Contacting Red Hat 12.2.4. Uploading VMDK images and creating a RHEL virtual machine in vSphere With RHEL image builder, you can create customized VMware vSphere system images, either in the Open virtualization format ( .ova ) or in the Virtual disk ( .vmdk ) format. You can upload these images to the VMware vSphere client. You can upload the .vmdk or .ova image to VMware vSphere using the govc import.vmdk CLI tool. The vmdk you create contains the cloud-init package installed and you can use it to provision users by using user data, for example. Note Uploading vmdk images by using the VMware vSphere GUI is not supported. Prerequisites You created a blueprint with username and password customizations. You created a VMware vSphere image either in the .ova or .vmdk format by using RHEL image builder and downloaded it to your host system. You installed and configured the govc CLI tool, to be able use the import.vmdk command. Procedure Configure the following values in the user environment with the GOVC environment variables: Navigate to the directory where you downloaded your VMware vSphere image. Launch the VMware vSphere image on vSphere by following the steps: Import the VMware vSphere image in to vSphere: For the .ova format: Create the VM in vSphere without powering it on: For the .ova format, replace the line -firmware=efi -disk=" foldername /composer-api.vmdk" \ with `-firmware=efi -disk=" foldername /composer-api.ova" \ Power-on the VM: Retrieve the VM IP address: Use SSH to log in to the VM, using the username and password you specified in your blueprint: Note If you copied the .vmdk image from your local host to the destination using the govc datastore.upload command, using the resulting image is not supported. There is no option to use the import.vmdk command in the vSphere GUI and as a result, the vSphere GUI does not support the direct upload. As a consequence, the .vmdk image is not usable from the vSphere GUI. 12.2.5. Creating and automatically uploading VMDK images to vSphere using image builder GUI You can build VMware images by using the RHEL image builder GUI tool and automatically push the images directly to your vSphere instance. This avoids the need to download the image file and push it manually. The vmdk you create contains the cloud-init package installed and you can use it to provision users by using user data, for example. To build .vmdk images by using RHEL image builder and push them directly to vSphere instances service provider, follow the steps: Prerequisites You are a member of the root or the weldr group. You have opened link:https://localhost:9090/RHEL image builder in a browser. You have created a blueprint. See Creating a RHEL image builder blueprint in the web console interface . You have a vSphere Account . Procedure For the blueprint you created, click the Images tab . Click Create Image to create your customized image. The Image type window opens. In the Image type window: From the dropdown menu, select the Type: VMware vSphere (.vmdk). Check the Upload to VMware checkbox to upload your image to the vSphere. Optional: Set the size of the image you want to instantiate. The minimal default size is 2 GB. Click . In the Upload to VMware window, under Authentication , enter the following details: Username : username of the vSphere account. Password : password of the vSphere account. In the Upload to VMware window, under Destination , enter the following details about the image upload destination: Image name : a name for the image. Host : The URL of your VMware vSphere. Cluster : The name of the cluster. Data center : The name of the data center. Data store :The name of the Data store. Click . In the Review window, review the details of the image creation and click Finish . You can click Back to modify any incorrect detail. RHEL image builder adds the compose of a RHEL vSphere image to the queue, and creates and uploads the image to the Cluster on the vSphere instance you specified. Note The image build and upload processes take a few minutes to complete. After the process is complete, you can see the Image build complete status. Verification After the image status upload is completed successfully, you can create a Virtual Machine (VM) from the image you uploaded and login into it. To do so: Access VMware vSphere Client. Search for the image in the Cluster on the vSphere instance you specified. Select the image you uploaded. Right-click the selected image. Click New Virtual Machine . A New Virtual Machine window opens. In the New Virtual Machine window, provide the following details: Select New Virtual Machine . Select a name and a folder for your VM. Select a computer resource: choose a destination computer resource for this operation. Select storage: For example, select NFS-Node1 Select compatibility: The image should be BIOS only. Select a guest operating system: For example, select Linux and Red Hat Fedora (64-bit) . Customize hardware : When creating a VM, on the Device Configuration button on the upper right, delete the default New Hard Disk and use the drop-down to select an Existing Hard Disk disk image: Ready to complete: Review the details and click Finish to create the image. Navigate to the VMs tab. From the list, select the VM you created. Click the Start button from the panel. A new window appears, showing the VM image loading. Log in with the credentials you created for the blueprint. You can verify if the packages you added to the blueprint are installed. For example: Additional resources Introduction to vSphere Installation and Setup 12.3. Preparing and uploading custom GCE images to GCP You can create custom images and then automatically update them to the Oracle Cloud Infrastructure (OCI) instance with RHEL image builder. 12.3.1. Uploading images to GCP with RHEL image builder With RHEL image builder, you can build a gce image, provide credentials for your user or GCP service account, and then upload the gce image directly to the GCP environment. 12.3.1.1. Configuring and uploading a gce image to GCP by using the CLI Set up a configuration file with credentials to upload your gce image to GCP by using the RHEL image builder CLI. Warning You cannot manually import gce image to GCP, because the image will not boot. You must use either gcloud or RHEL image builder to upload it. Prerequisites You have a valid Google account and credentials to upload your image to GCP. The credentials can be from a user account or a service account. The account associated with the credentials must have at least the following IAM roles assigned: roles/storage.admin - to create and delete storage objects roles/compute.storageAdmin - to import a VM image to Compute Engine. You have an existing GCP bucket. Procedure Use a text editor to create a gcp-config.toml configuration file with the following content: GCP_BUCKET points to an existing bucket. It is used to store the intermediate storage object of the image which is being uploaded. GCP_STORAGE_REGION is both a regular Google storage region and a dual or multi region. OBJECT_KEY is the name of an intermediate storage object. It must not exist before the upload, and it is deleted when the upload process is done. If the object name does not end with .tar.gz , the extension is automatically added to the object name. GCP_CREDENTIALS is a Base64 -encoded scheme of the credentials JSON file downloaded from GCP. The credentials determine which project the GCP uploads the image to. Note Specifying GCP_CREDENTIALS in the gcp-config.toml file is optional if you use a different mechanism to authenticate with GCP. For other authentication methods, see Authenticating with GCP . Retrieve the GCP_CREDENTIALS from the JSON file downloaded from GCP. Create a compose with an additional image name and cloud provider profile: The image build, upload, and cloud registration processes can take up to ten minutes to complete. Verification Verify that the image status is FINISHED: Additional resources Identity and Access Management Create storage buckets 12.3.1.2. How RHEL image builder sorts the authentication order of different GCP credentials You can use several different types of credentials with RHEL image builder to authenticate with GCP. If RHEL image builder configuration is set to authenticate with GCP using multiple sets of credentials, it uses the credentials in the following order of preference: Credentials specified with the composer-cli command in the configuration file. Credentials configured in the osbuild-composer worker configuration. Application Default Credentials from the Google GCP SDK library, which tries to automatically find a way to authenticate by using the following options: If the GOOGLE_APPLICATION_CREDENTIALS environment variable is set, Application Default Credentials tries to load and use credentials from the file pointed to by the variable. Application Default Credentials tries to authenticate by using the service account attached to the resource that is running the code. For example, Google Compute Engine VM. Note You must use the GCP credentials to determine which GCP project to upload the image to. Therefore, unless you want to upload all of your images to the same GCP project, you always must specify the credentials in the gcp-config.toml configuration file with the composer-cli command. 12.3.1.2.1. Specifying GCP credentials with the composer-cli command You can specify GCP authentication credentials in the upload target configuration gcp-config.toml file. Use a Base64 -encoded scheme of the Google account credentials JSON file to save time. Procedure Get the encoded content of the Google account credentials file with the path stored in GOOGLE_APPLICATION_CREDENTIALS environment variable, by running the following command: In the upload target configuration gcp-config.toml file, set the credentials: 12.3.1.2.2. Specifying credentials in the osbuild-composer worker configuration You can configure GCP authentication credentials to be used for GCP globally for all image builds. This way, if you want to import images to the same GCP project, you can use the same credentials for all image uploads to GCP. Procedure In the /etc/osbuild-worker/osbuild-worker.toml worker configuration, set the following credential value: 12.4. Preparing and uploading custom images directly to OCI You can create custom images and then automatically update them to the Oracle Cloud Infrastructure (OCI) instance with RHEL image builder. 12.4.1. Creating and automatically uploading custom images to OCI With RHEL image builder, build customized images and automatically push them directly to your Oracle Cloud Infrastructure (OCI) instance. Then, you can start an image instance from the OCI dashboard. Prerequisites You have root or weldr group user access to the system. You have an Oracle Cloud account. You must be granted security access in an OCI policy by your administrator. You have created an OCI Bucket in the OCI_REGION of your choice. Procedure Open the RHEL image builder interface of the web console in a browser. Click Create blueprint . The Create blueprint wizard opens. On the Details page, enter a name for the blueprint, and optionally, a description. Click . On the Packages page, select the components and packages that you want to include in the image. Click . On the Customizations page, configure the customizations that you want for your blueprint. Click . On the Review page, click Create . To create an image, click Create Image . The Create image wizard opens. On the Image output page, complete the following steps: From the "Select a blueprint" drop-down menu, select the blueprint you want. From the "Image output type" drop-down menu, select Oracle Cloud Infrastructure (.qcow2) . Check the "Upload OCI checkbox to upload your image to the OCI. Enter the "image size" . Click . On the Upload to OCI - Authentication page, enter the following mandatory details: User OCID: you can find it in the Console on the page showing the user's details. Private key On the Upload to OCI - Destination page, enter the following mandatory details and click . Image name: a name for the image to be uploaded. OCI bucket Bucket namespace Bucket region Bucket compartment Bucket tenancy Review the details in the wizard and click Finish . RHEL image builder adds the compose of a RHEL .qcow2 image to the queue. Verification Access the OCI dashboard Custom Images. Select the Compartment you specified for the image and locate the image in the Import image table. Click the image name and verify the image information. Additional resources Managing custom images in the OCI. Managing buckets in the OCI. Generating SSH keys. 12.5. Preparing and uploading customized QCOW2 images directly to OpenStack You can create custom .qcow2 images with RHEL image builder, and manually upload them to the OpenStack cloud deployments. 12.5.1. Uploading QCOW2 images to OpenStack With the RHEL image builder tool, you can create customized .qcow2 images that are suitable for uploading to OpenStack cloud deployments, and starting instances there. RHEL image builder creates images in the QCOW2 format, but with further changes specific to OpenStack. Warning Do not mistake the generic QCOW2 image type output format you create by using RHEL image builder with the OpenStack image type, which is also in the QCOW2 format, but contains further changes specific to OpenStack. Prerequisites You have created a blueprint. Procedure Start the compose of a QCOW2 image. Check the status of the building. After the image build finishes, you can download the image. Download the QCOW2 image: Access the OpenStack dashboard and click +Create Image . On the left menu, select the Admin tab. From the System Panel , click Image . The Create An Image wizard opens. In the Create An Image wizard: Enter a name for the image Click Browse to upload the QCOW2 image. From the Format dropdown list, select the QCOW2 - QEMU Emulator . Click Create Image . On the left menu, select the Project tab. From the Compute menu, select Instances . Click the Launch Instance button. The Launch Instance wizard opens. On the Details page, enter a name for the instance. Click . On the Source page, select the name of the image you uploaded. Click . On the Flavor page, select the machine resources that best fit your needs. Click Launch . You can run the image instance using any mechanism (CLI or OpenStack web UI) from the image. Use your private key via SSH to access the resulting instance. Log in as cloud-user . 12.6. Preparing and uploading customized RHEL images to the Alibaba Cloud You can upload a customized .ami images that you created by using RHEL image builder to the Alibaba Cloud. 12.6.1. Preparing to upload customized RHEL images to Alibaba Cloud To deploy a customized RHEL image to the Alibaba Cloud, first you need to verify the customized image. The image needs a specific configuration to boot successfully, because Alibaba Cloud requests the custom images to meet certain requirements before you use it. Note RHEL image builder generates images that conform to Alibaba's requirements. However, Red Hat recommends also using the Alibaba image_check tool to verify the format compliance of your image. Prerequisites You must have created an Alibaba image by using RHEL image builder. Procedure Connect to the system containing the image that you want to check by using the Alibaba image_check tool. Download the image_check tool: Change the file permission of the image compliance tool: Run the command to start the image compliance tool checkup: The tool verifies the system configuration and generates a report that is displayed on your screen. The image_check tool saves this report in the same folder where the image compliance tool is running. Troubleshooting If any of the Detection Items fail, follow the instructions in the terminal to correct it. Additional resources Image Compliance Tool. 12.6.2. Uploading customized RHEL images to Alibaba You can upload a customized AMI image you created by using RHEL image builder to the Object Storage Service (OSS). Prerequisites Your system is set up for uploading Alibaba images. See Preparing for uploading images to Alibaba . You have created an ami image by using RHEL image builder. You have a bucket. See Creating a bucket . You have an active Alibaba Account . You activated OSS . Procedure Log in to the OSS console . In the Bucket menu on the left, select the bucket to which you want to upload an image. In the upper right menu, click the Files tab. Click Upload . A dialog window opens on the right side. Configure the following: Upload To : Choose to upload the file to the Current directory or to a Specified directory. File ACL : Choose the type of permission of the uploaded file. Click Upload . Select the image you want to upload to the OSS Console.. Click Open . Additional resources Upload an object. Creating an instance from custom images. Importing images. 12.6.3. Importing images to Alibaba Cloud To import a customized Alibaba RHEL image that you created by using RHEL image builder to the Elastic Compute Service (ECS), follow the steps: Prerequisites Your system is set up for uploading Alibaba images. See Preparing for uploading images to Alibaba . You have created an ami image by using RHEL image builder. You have a bucket. See Creating a bucket . You have an active Alibaba Account . You activated OSS . You have uploaded the image to Object Storage Service (OSS). See Uploading images to Alibaba . Procedure Log in to the ECS console. On the left-side menu, click Images . On the upper right side, click Import Image . A dialog window opens. Confirm that you have set up the correct region where the image is located. Enter the following information: OSS Object Address : See how to obtain OSS Object Address . Image Name Operating System System Disk Size System Architecture Platform : Red Hat Optional: Provide the following details: Image Format : qcow2 or ami , depending on the uploaded image format. Image Description Add Images of Data Disks The address can be determined in the OSS management console. After selecting the required bucket in the left menu: Select Files section. Click the Details link on the right for the appropriate image. A window appears on the right side of the screen, showing image details. The OSS object address is in the URL box. Click OK . Note The importing process time can vary depending on the image size. The customized image is imported to the ECS Console. Additional resources Notes for importing images. Creating an instance from custom images. Upload an object. 12.6.4. Creating an instance of a customized RHEL image using Alibaba Cloud You can create instances of a customized RHEL image by using the Alibaba ECS Console. Prerequisites You have activated OSS and uploaded your custom image. You have successfully imported your image to ECS Console. See Importing images to Alibaba . Procedure Log in to the ECS console. On the left-side menu, select Instances . In the upper-right corner, click Create Instance . You are redirected to a new window. Complete all the required information. See Creating an instance by using the wizard for more details. Click Create Instance and confirm the order. Note You can see the option Create Order instead of Create Instance , depending on your subscription. As a result, you have an active instance ready for deployment from the Alibaba ECS Console . Additional resources Creating an instance by using a custom image. Create an instance by using the wizard.

Commands:
yum install python3 python3-pip
pip3 install awscli
aws configure AWS Access Key ID [None]: AWS Secret Access Key [None]: Default region name [None]: Default output format [None]:
BUCKET= bucketname aws s3 mb s3://USDBUCKET
{ "Version": "2022-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "Service": "vmie.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "StringEquals": { "sts:Externalid": "vmimport" } } }] }
{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": ["s3:GetBucketLocation", "s3:GetObject", "s3:ListBucket"], "Resource": ["arn:aws:s3:::%s", "arn:aws:s3:::%s/ "] }, { "Effect": "Allow", "Action": ["ec2:ModifySnapshotAttribute", "ec2:CopySnapshot", "ec2:RegisterImage", "ec2:Describe "], "Resource": "*" }] } USDBUCKET USDBUCKET
aws iam create-role --role-name vmimport --assume-role-policy-document file://trust-policy.json
aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document file://role-policy.json
provider = "aws" [settings] accessKeyID = " AWS_ACCESS_KEY_ID " secretAccessKey = "AWS_SECRET_ACCESS_KEY" bucket = "AWS_BUCKET" region = "AWS_REGION" key = "IMAGE_KEY"
composer-cli compose start blueprint-name image-type image-key configuration-file .toml
composer-cli compose status
chmod 400 <_your-instance-name.pem_>
ssh -i <_your-instance-name.pem_> ec2-user@<_your-instance-IP-address_>
rpm --import https://packages.microsoft.com/keys/microsoft.asc
[azure-cli] name=Azure CLI baseurl=https://packages.microsoft.com/yumrepos/vscode enabled=1 gpgcheck=1 gpgkey=https://packages.microsoft.com/keys/microsoft.asc
yumdownloader azure-cli rpm -ivh --nodeps azure-cli-2.0.64-1.el7.x86_64.rpm
az login
az storage account keys list --resource-group <resource_group_name> --account-name <storage_account_name>
az resource list
az storage container create --account-name <storage_account_name> --account-key <key1_value> --name <storage_account_name>
az storage blob upload --account-name <_account_name_> --container-name <_container_name_> --file <_image_-disk.vhd> --name <_image_-disk.vhd> --type page
az image create --resource-group <_resource_group_name_> --name <_image_>-disk.vhd --os-type linux --location <_location_> --source https://USD<_account_name_>.blob.core.windows.net/<_container_name_>/<_image_>-disk.vhd - Running
az vm create --resource-group <_resource_group_name_> --location <_location_> --name <_vm_name_> --image <_image_>-disk.vhd --admin-username azure-user --generate-ssh-keys - Running
GOVC_URL GOVC_DATACENTER GOVC_FOLDER GOVC_DATASTORE GOVC_RESOURCE_POOL GOVC_NETWORK
govc import.vmdk ./composer-api.vmdk foldername
govc import.ova ./composer-api.ova foldername
govc vm.create -net.adapter=vmxnet3 -m=4096 -c=2 -g=rhel8_64Guest -firmware=efi -disk=" foldername /composer-api.vmdk" -disk.controller=scsi -on=false vmname
govc vm.power -on vmname
govc vm.ip vmname
ssh admin@<_ip_address_of_the_vm_>
rpm -qa | grep firefox
provider = "gcp" [settings] bucket = "GCP_BUCKET" region = "GCP_STORAGE_REGION" object = "OBJECT_KEY" credentials = "GCP_CREDENTIALS"
sudo base64 -w 0 cee-gcp-nasa-476a1fa485b7.json
sudo composer-cli compose start BLUEPRINT-NAME gce IMAGE_KEY gcp-config.toml
sudo composer-cli compose status
base64 -w 0 "USD{GOOGLE_APPLICATION_CREDENTIALS}"
provider = "gcp" [settings] provider = "gcp" [settings] credentials = "GCP_CREDENTIALS"
[gcp] credentials = " PATH_TO_GCP_ACCOUNT_CREDENTIALS "
composer-cli compose start blueprint_name openstack
composer-cli compose status
composer-cli compose image UUID
curl -O https://docs-aliyun.cn-hangzhou.oss.aliyun-inc.com/assets/attach/73848/cn_zh/1557459863884/image_check
chmod +x image_check
./image_check