This is a repackaged software product wherein additional charges apply for a pre-hardened, SI Core STIG Hardened image and seller support. Jenkins on CentOS 10 provides a robust and secure Continuous Integration/Continuous Deployment (CI/CD) pipeline solution, tailored for enterprises seeking to streamline their software development processes. With Jenkins on CentOS 10, users benefit from an optimized environment boasting enhanced security, performance, and stability. The pre-hardened image simplifies the deployment process, allowing teams to focus on development rather than configuration. Ideal for DevOps teams, Jenkins on CentOS 10 supports automation of building, testing, and deploying applications, ensuring that organizations can deliver high-quality software rapidly and efficiently.
Discover the power of Jenkins on CentOS 10, an optimized Amazon Machine Image (AMI) designed for seamless Continuous Integration and Continuous Deployment (CI/CD) workflows. This AMI provides a fully configured Jenkins environment built on the reliable CentOS 10 platform, ensuring stability and performance for your software development needs.
With Jenkins on CentOS 10, you can easily set up automated build pipelines, manage project dependencies, and streamline testing processes. This AMI comes with Jenkins pre-installed, allowing you to focus on building your applications rather than spending time on initial configurations.
Whether you're a small startup or an established enterprise, Jenkins on CentOS 10 enhances your DevOps practices by providing a robust automation server. Leverage the extensive Jenkins ecosystem by integrating plugins to support a wide range of languages and tools, enhancing your team's productivity and collaboration.
In addition to its powerful features, Jenkins on CentOS 10 ensures easy scalability and can be quickly launched in the AWS EC2 cloud, making it an excellent choice for teams looking to adopt cloud-native solutions. Experience the benefits of reduced deployment times and improved software quality with this efficient, ready-to-use AMI.
Start automating your development process today with Jenkins on CentOS 10, the ideal solution for teams aiming to optimize their CI/CD pipelines and enhance their project delivery capabilities.
Hardening and Support
This is a repackaged software product wherein additional charges apply for a pre-hardened, Supported Images Core STIG Hardened image and seller support. Additional detailed information on our hardening process can be found in the Core STIG Hardening for Linux Guide or the Core STIG Hardening for Windows Guide
Jenkins on CentOS Stream 10 provides developers with a robust Continuous Integration/Continuous Delivery (CI/CD) platform, enabling seamless automation of software build processes. With its user-friendly interface and extensive plugin ecosystem, users can rapidly set up and manage automated tasks, facilitating faster deployment cycles. By leveraging this AMI, teams can ensure consistent development practices and increase collaboration across multiple projects and environments.
The CentOS 10 base enhances Jenkins by offering stability, performance, and security, critical for enterprise environments. Users benefit from CentOS's reliability, ensuring their CI/CD pipelines run efficiently without interruptions. Additionally, by utilizing AWS infrastructure, organizations can scale their Jenkins environments according to demand, optimizing resource allocation and cost management while maintaining high availability for their build systems.
This AMI is suitable for various use cases, such as mobile app development, microservices deployment, and web application lifecycle management. Its compatibility with popular source control systems, such as Git, enables effortless integration that streamlines development workflows. Overall, Jenkins on CentOS 10 offers a powerful solution for teams looking to enhance productivity and accelerate their release cycles while maintaining quality through automation.
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.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
You pay by the hour for this preconfigured Jenkins image on hardened CentOS 10. Pricing follows the EC2 instance type you run, not tiers or feature packages. Each dimension maps to a specific AWS instance size, from small burstable options to large compute, memory, storage, and accelerated types. Your rate scales with the size and family you pick, since larger instances carry more CPU, memory, or specialized hardware. You choose the instance that fits your workload, and billing accrues only for the hours it runs. No upfront commitment applies.
Top-of-mind questions for buyers
What does one hourly unit cover for this Jenkins image?
One unit is one running EC2 instance of the type you select, billed per hour. The rate bundles the hardened CentOS 10 image with preconfigured Jenkins software. Each running instance meters separately. The unit maps to the instance size and family, so your rate reflects its CPU, memory, or specialized hardware.
Am I charged when the instance is stopped or paused?
Software charges accrue only while the instance runs. A stopped or paused instance stops the hourly software meter. You may still pay underlying AWS fees for attached storage or reserved resources, but the image's hourly rate applies only to running time. No upfront commitment applies.
Does my cost change automatically if I switch to a different instance type?
Yes. Your hourly rate follows whichever instance type runs. Move to a larger family or size and the rate rises with the added CPU, memory, or accelerators. Move smaller and it drops. The change takes effect when you launch the new instance. No tier upgrade or manual step applies.
supportedimages.com+1
Helpful?
Vendor refund policy
The instance can be terminated at anytime to stop incurring charges
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.
Version release notes
System update
Additional details
Usage instructions
SSH to the instance and login as 'ec2-user' using the key specified at launch.
OS commands via SSH: SSH as user 'ec2-user' to the running instance and
use sudo to run commands requiring root access.
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.
Pre-installed Jenkins environment with automated build pipeline configuration, project dependency management, and streamlined testing process automation on CentOS 10 platform
Plugin Ecosystem Integration
Extensive Jenkins plugin ecosystem supporting multiple programming languages and tools, with compatibility for popular source control systems including Git
Security Hardening
Core STIG hardened image implementation following Security Technical Implementation Guide standards for enhanced security posture
Cloud-Native Scalability
AWS EC2 deployment capability with dynamic scaling support to adjust Jenkins environments according to demand and optimize resource allocation
Pre-Configured Environment
Fully configured Jenkins AMI with pre-installed components eliminating initial configuration requirements and enabling immediate deployment readiness
SELinux Enforcement
SELinux enforcement enabled by default for mandatory access control and security policy enforcement
Cloud-Init Integration
Built-in cloud-init automation support for automated provisioning workflows and instance configuration during deployment
ENA Networking Support
ENA (Elastic Network Adapter) networking enabled for optimized network performance on AWS EC2 instances
Automated Security Updates
System synchronizes with upstream repositories at first boot to install newest security updates and package revisions
SSH Public Key Authentication
SSH public key authentication configured with ec2-user login and root login disabled by default
In-Place Linux Distribution Conversion
Convert2RHEL tooling enables in-place conversion of instances running on rpm-based Linux distributions to Red Hat Enterprise Linux 7 while preserving existing customizations, configurations, and preferences.
Extended Security Support
Extended Life Cycle Support (ELS) provides access to security patches and updates until June 2029, extending support five years beyond the CentOS Linux 7 end-of-life date.
High Availability Support
High Availability tooling and capabilities included for configuring and managing highly available infrastructure and applications.
System Observability and Management
Red Hat Insights integration provides monitoring, analysis, and remediation capabilities for security, stability, and performance issues across workloads, applications, and platforms.
Cross-Infrastructure Consistency
Unified operating foundation supporting consistent management and deployment across physical, virtual, private cloud, public cloud, and edge environments.
Continuous delivery has accelerated our build, test, and deployment workflows
Reviewed on Sep 11, 2026
Review provided by PeerSpot
What is our primary use case?
I have been using Jenkins on CentOS 10 for approximately seven to eight years.
My main use case for Jenkins on CentOS 10 is to run CI/CD pipelines.
To run my pipelines using Jenkins on CentOS 10, we have different applications where the whole build, test, deploy phase is run through pipelines, as well as other configuration that are applied to the applications.
I haven't observed anything truly unique in how we interact with Jenkins on CentOS 10 as I've seen more or less the same use case in other companies.
What is most valuable?
The best features Jenkins on CentOS 10 offers include many plugins that you can get from the community, so it's highly adjustable to the environment, supports multi-branch pipelines, has an architecture of primary and secondary servers for scaling up Jenkins that works really well when you have larger teams using it, and also has many native integrations with Git, Bitbucket and so on, making it excellent overall.
The plugin ecosystem and scalability of Jenkins on CentOS 10 have specifically helped my team because it's really beneficial when you can use additional secondary servers, and it scales well because of that; I use dozens of plugins for authentication, building role-based access control in larger teams and so on, as well as a bunch of pipeline improvements.
The plugins related to the integrations in Jenkins on CentOS 10 are crucial because many of them allow integrations with different systems.
Jenkins on CentOS 10 has positively impacted my organization by allowing our teams to build and deploy applications really fast, and because it has been around for many years, it's easy to find people with good knowledge in Jenkins who can immediately start contributing to the team without having to learn some new tool.
Deployments are at least eighty to ninety percent faster using Jenkins on CentOS 10 compared to scripting your way and developing your own tools, so the time saved is enormous as well as all the cost that comes with it, which otherwise equals additional cost in engineering time spent.
What needs improvement?
The plugins in Jenkins on CentOS 10, while really great because of the huge ecosystem, can also be a pain point because you never know how long they will be maintained, and there's a slight instability there; if you depend on some plugin that does an integration with some product and the plugin is not maintained anymore, you're blocked from using the product features that would integrate through the plugin, and it doesn't have high availability natively.
For how long have I used the solution?
I have been using Jenkins on CentOS 10 for approximately seven to eight years.
What do I think about the stability of the solution?
Jenkins on CentOS 10 is stable.
What do I think about the scalability of the solution?
Jenkins on CentOS 10 can scale well by adding additional servers.
How are customer service and support?
There is no customer support for Jenkins on CentOS 10 since it's open source.
Which solution did I use previously and why did I switch?
I haven't switched from another solution, but I have used other solutions in parallel.
What was our ROI?
I have seen a return on investment in terms of time saved and money saved because of the time saved for engineers, but I don't have any specific data that I would be able to share.
Which other solutions did I evaluate?
At some point, I evaluated CircleCI alongside Jenkins on CentOS 10.
What other advice do I have?
My advice for others looking into using Jenkins on CentOS 10 is that it costs nothing, so give it a try; I'm pretty sure you will find it easy to use. I don't believe there are any improvements needed for Jenkins on CentOS 10 that we haven't discussed yet.