We are pleased to announce that you can now attach an Ubuntu Pro subscription directly to any base image in AWS Image Builder, allowing you to create enterprise-grade custom images from the get go.
Until now, getting Ubuntu Pro into a custom AMI (Amazon Machine Image) meant either starting from an Ubuntu Pro base image or manually applying a token during the build. You can now attach an Ubuntu Pro subscription to any base image directly in your build pipeline even if the base image is a non-Ubuntu Linux image.
This unlocks simpler and more flexible AMI builds: add Ubuntu Pro as just another component to the recipe, with no manual steps required. This makes Ubuntu Pro straightforward to integrate into CI/CD pipelines and automated provisioning workflows.
Note: Attaching Ubuntu Pro to a non-Ubuntu host only licenses the cluster to run Ubuntu Pro containers. It does not give the host access to Ubuntu Pro services like Expanded Security Maintenance, compliance hardening, or Kernel live patching.
Make sure you have the following in place:
imagebuilder:GetComponent, aws-marketplace:Subscribe).ubuntu-pro-client should be installed for the Pro client to activate services on first boot.Subscribe to the component that matches your target architecture:
You can do this using the AWS Web Console or the AWS CLI. The overall flow is the same:
If you are using the AWS Web console, open the Source dropdown and select AWS Marketplace. This will display all available Marketplace components. Search for Ubuntu Pro and select the component that matches your base AMI architecture (AMD64 or ARM64).
If you are using AWS CLI, you will need to take note of the Ubuntu Pro component ARN to use it in your API call.
The next step should be familiar: configure custom workflows, infrastructure details, and distribution settings.
Once you have added the Ubuntu Pro component to your recipe, the rest of the workflow follows the instructions of the standard Image Builder:
Once the image is built, the Ubuntu Pro subscription will be attached to the resulting AMI as instance metadata. If your base image is Ubuntu and the Pro client is installed, the default Ubuntu Pro services will be activated on the next boot.
If you want to learn more in detail about how to build a recipe with the Ubuntu Pro component, read more in our official documentation page.
To confirm the Ubuntu Pro license was attached correctly, check whether the right Marketplace product code is present on your AMI.
Go to EC2 → AMIs, select your AMI, and look at the Product codes field in the details panel below. You should see one of the following:
Marketplace:9bztusbna2lfuk6zw7upzdvsv — AMD64 imagesMarketplace:291iwywwdb7ujmih1x7z4l3my — Graviton (ARM64) imagesaws ec2 describe-images
--owners self
--query 'Images[*].{ImageId: ImageId, Name: Name, ProductCodes: ProductCodes[*].ProductCodeId}'
--output text Lo and behold 👐, Ubuntu MATE 26.10 (Stonking Stingray) is here! 🎊 We are back…
This article provides a guide demonstrating how to deploy Kiwix Server on Ubuntu VPS. What…
A few months ago, we introduced Myna, our project to bring private, local speech-to-text dictation…
Ubuntu 26.10 “Stonking Stingray” arrives at a time when AI tools are accelerating vulnerability discovery.…
One of the best things about Rust is how easy it is to get started.…