- Newest
- Most votes
- Most comments
According to Red Hat, supported methods for creating RHEL cloud instances are either (i) building your own image and then licensing it using BYOL; or (ii) provision an instance using the AWS-provided AMI https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/deploying_rhel_8_on_amazon_web_services/index#methods-for-creating-rhel-cloud-instances_introducing-rhel-on-public-cloud-platforms
Exporting from Azure and then importing to AWS sounds like it falls into category (i) and as such the instance would need to be attached to Satellite to get its updates. Rather than the AWS RHUI repos, access to which is included in the pricing of instances provisioned in category (ii).
Azure's website actually tries to unravel this better than anything I've seen on AWS https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/redhat/redhat-rhui#important-information-about-azure-rhui
Relevant content
- asked a year ago
- asked a year ago
- asked 11 days ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 days ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago
Thank you Steve. So once we acquire a subscription for this RHEL machine, is it easy as attaching the subscription via Subscription Manager CLI and would receive an update? OR should we still clean up the Azure RHUI repos?