The Mirantis Container Runtime (MCR 25.0) for Red Hat Enterprise Linux 9 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
If your teams are already building and managing applications with Docker, you can promote those workloads to production without needing to retool or migrate. Mirantis Container Runtime (formerly Docker Engine - Enterprise) is fully compatible with Docker-based workflows and toolchains, providing a seamless path from development to production. Developers can continue using the same CLI, Dockerfiles, and APIs they already know, while IT can seamlessly promote those workloads into production with the assurance of an Enterprise Support agreement with guaranteed SLAs.
MCR, built on CNCF Docker Moby, is purpose-built for running containers at scale in production. It offers tested and validated releases across a broad set of operating systems, with robust CVE patching and bug fixes to ensure workload stability. MCR also enables hybrid and distributed cloud strategies by supporting the broadest range of platforms in the industry while meeting strict compliance standards.
Mirantis acquired Docker Enterprise in 2019, and since then has been contributing upstream to Docker Moby and related technologies. Today, MCR provides enterprise-ready container infrastructure that aligns with open standards, enabling customers to run Docker-based applications reliably in mission-critical environments.
Key Features include:
Security: AppArmor application-level access control, SELinux mandatory access control (MAC), FIPS 140-2 validated encryption, image signature verification, and support for sandboxed and isolated container runtimes such as Kata and gVisor
Performance: Optimized architecture with minimal resource overhead, fast container startup for efficient deployment and scaling
Ease of Use: Intuitive Docker CLI and support for Docker Swarm container orchestration in addition to Kubernetes
Multi-Cloud Interoperability: Support for multiple cloud platforms and operating systems, giving customers seamless portability with consistent management
AI Workload Support: Native AI container support, enhanced GPU Support with Container Device Interface (CDI) to integrate different accelerators and device types
As an OCI-certified and CRI-conformant runtime, Mirantis Container Runtime (MCR) aligns with industry standards and is compatible with leading container orchestration platforms. Tested at scale and proven with hundreds of customer deployments, Mirantis Container Runtime is used to support mission-critical applications from data centers to the edge.
This offering currently includes Basic 8x5 Support, offering business-hour assistance via web and email, access to a robust knowledge base, regular maintenance updates, critical issue resolutions, and security and product bulletins. This support tier provides reliable remote incident resolution to help ensure your container environments remain secure and up to date during standard operating hours.
For organizations requiring broader coverage or fully managed services, Mirantis offers OpsCare and OpsCare Plus support upgrades. OpsCare provides enterprise-grade 24/7 support, lifecycle guidance, and escalation management. OpsCare Plus extends this with up to 99.99% SLA, a designated Customer Success Manager (CSM), a full ITIL service management suite, and customer advocacy. To explore these enhanced support options and identify the right fit for your workloads, please contact Mirantis sales.
Highlights
MCR provides FIPS 140-2 Validated cryptography ensuring that you meet the highest standards necessary to comply with the federal requirements.
MCR is certified to run on multiple operating systems and infrastructures, for consistent runtime regardless of the platform.
MCR provides enterprise support, with regular CVE and security updates
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
You pay by the hour based on the EC2 instance type running Mirantis Container Runtime on Red Hat Enterprise Linux 9. Each dimension maps to a specific instance type, all at the xlarge size. The list spans general-purpose, compute-optimized, memory-optimized, storage-optimized, and GPU or accelerated instance families. Your rate depends on which instance you choose, so pricing scales with the compute profile you select rather than through fixed tiers. This usage-based model means you are billed only for the hours each instance runs, with no upfront commitment or fixed quantity to configure.
Top-of-mind questions for buyers
What does one hourly unit cover, and what runs on the instance I select?
Each hourly unit covers one running EC2 instance of the type you choose, at the xlarge size, on Red Hat Enterprise Linux 9. The instance runs the container runtime software, which builds and runs containers. You are billed for each hour that instance stays running.
Am I charged when an instance is stopped or powered off?
The software meters running hours only. When you stop or power off an instance, hourly software charges stop accruing. Underlying AWS storage or other AWS resource fees may still apply while the instance is stopped, but those are separate from the container runtime software charge.
Which instance choice drives my cost, and do charges change automatically if I switch types?
Your hourly rate depends entirely on the instance type you run. Compute-optimized, memory-optimized, storage-optimized, and GPU or accelerated families each carry different rates. If you launch a different instance type, that instance bills at its own rate. There are no fixed tiers to upgrade between.
www.mirantis.com+1
Helpful?
Vendor refund policy
none
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
In the AWS Management Console, go to the Services menu.
Under the Compute section, select EC2.
In the left-hand navigation pane, select AMI Catalog
Search for the Linux image you want to launch. i.e. Mirantis Container Runtime for Ubuntu
Click on the Launch Instance button.
Step 3: Search for the Desired AMI
In the Choose an Amazon Machine Image (AMI) step, select the AWS Marketplace tab.
Use the search bar to find the desired AMI. For example, you can search for "Ubuntu 20.04" or any other specific AMI you need.
Browse through the search results and select the AMI that matches your requirements.
Step 4: Subscribe to the AMI
Click on the Select button next to the desired AMI.
Review the pricing details and terms of use.
Click on the Continue button to subscribe to the AMI.
Step 5: Configure Instance Details
In the Choose an Instance Type step, select the instance type that meets your requirements (e.g., t2.micro, m5.large).
Click on the Next: Configure Instance Details button.
Configure the instance details, such as the number of instances, network settings, and IAM role.
Click on the Next: Add Storage button.
Step 6: Add Storage
Configure the storage settings for your instance. You can add additional EBS volumes if needed.
Click on the Next: Add Tags button.
Step 7: Add Tags
Add any tags to your instance to help you identify and manage it.
Click on the Next: Configure Security Group button.
Step 8: Configure Security Group
Configure the security group to allow the necessary inbound traffic. For example, you might need to allow SSH (port 22) for Linux instances or RDP (port 3389) for Windows instances.
Click on the Review and Launch button.
Step 9: Review and Launch
Review all the configuration details for your instance.
Click on the Launch button.
In the Select an existing key pair or create a new key pair dialog, choose an existing key pair or create a new one to access your instance.
Acknowledge that you have access to the selected key pair and click on the Launch Instances button.
Step 10: Access Your Instance
After the instance is launched, go to the Instances section in the EC2 dashboard.
Select your instance and click on the Connect button to get the connection details.
Use the provided instructions to connect to your instance via SSH for Linux.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
The Mirantis Container Runtime (MCR 29.0) for Red Hat Enterprise Linux 9 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
The Mirantis Container Runtime (MCR 23.0) for Red Hat Enterprise Linux 8 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
The Mirantis Container Runtime (MCR 25.0) for Ubuntu 24.04 AMI image provides users quick and secure way to deploy and run business critical applications with enterprise support
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.