Jenkins on Hardened Ubuntu 24.04 with Support logo

    Jenkins on Hardened Ubuntu 24.04 with Support

    This product has charges associated with it for seller support and enhanced security configurations. It provides Jenkins pre-installed on a secure Ubuntu 24.04 LTS environment, optimized for cloud deployment and includes support.

    Ratings and reviews

    4.3
    8 ratings
    3 star
    2 star
    1 star
    50%
    50%
    0%
    0%
    0%
    3 AWS reviews
    |
    5 external reviews
    External reviews are from PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (8)
    RiteshPurbey

    Controlled access for deployments has improved and supports secure job automation

    Reviewed on Jun 15, 2026
    Review provided by PeerSpot

    What is our primary use case?

    We use Jenkins on Hardened Ubuntu within the company and do not recommend it to customers. I am currently using Jenkins on Hardened Ubuntu mainly to avoid giving users access over the cloud portal.

    What is most valuable?

    Jenkins on Hardened Ubuntu is valuable for us from a continuous deployment perspective. We have created a job that allows end-users to start and stop AWS or Azure machines without requiring access to the portal. We give Jenkins access to them, and they can manage their tasks as needed.

    We have some jobs to copy files and perform other automated actions on Jenkins. Users can build the job, and their tasks are completed.

    Jenkins on Hardened Ubuntu provides privileges to a few users, such as the infrastructure team, who have administrator roles, while others have access only to particular jobs with the appropriate ACL privileges.

    We have integrated Jenkins on Hardened Ubuntu with our Active Directory to measure security effectiveness.

    What needs improvement?

    Currently, Jenkins on Hardened Ubuntu is almost obsolete. Tools such as GitLab now provide self-sufficient end-to-end deployment options. Azure DevOps and AWS with Bitbucket are similar, and Jenkins is not beneficial for our code deployment perspective anymore.

    Many SCM providers are highly capable for deployment, such as GitLab and GitHub, which are sufficient for triggering jobs. I am not exactly aware of how Jenkins on Hardened Ubuntu can be improved since many are moving away from Jenkins.

    Most of the plugins currently lack management. Our concern is that some security plugins should at least be maintainable by Jenkins rather than third parties.

    For how long have I used the solution?

    I have been working with Jenkins on Hardened Ubuntu for more than eight years.

    How are customer service and support?

    Since we are using an open source version of Jenkins on Hardened Ubuntu, we have never connected with Jenkins support.

    Which solution did I use previously and why did I switch?

    Before using Jenkins on Hardened Ubuntu, we worked with some tools from a cloud provider, such as Argo CD.

    Which other solutions did I evaluate?

    My expertise is limited to Jenkins on Hardened Ubuntu and Argo CD. I would recommend the latter as a solution instead.

    What other advice do I have?

    We have Jenkins plugins and other things for Jenkins on Hardened Ubuntu. There are many security-related plugins that need to be maintained, so some additional features could enhance Jenkins on Hardened Ubuntu's usability.

    Jenkins on Hardened Ubuntu is easy to use. Since it is open source, it was highly recommended a decade ago and many organizations used it, but times have changed, and now everyone is shifting to other tools.

    We are upgrading Jenkins on Hardened Ubuntu regularly. When a patch update comes, we apply it simultaneously with any available Jenkins updates, which helps us plan accordingly.

    I rated this product eight out of ten.

    Ria Gupta

    Secure governance has improved event management and now provides reliable AI-driven workflows

    Reviewed on Jun 10, 2026
    Review provided by PeerSpot

    What is our primary use case?

    I use Jenkins on Hardened Ubuntu to manage and maintain Jenkins. It is used during conference events.

    What is most valuable?

    Regarding Jenkins on Hardened Ubuntu's AI capabilities, I find its governance and security to be quite secure. The accuracy and reliability of Jenkins on Hardened Ubuntu's AI output is 90% accurate.

    For how long have I used the solution?

    I have been using Jenkins on Hardened Ubuntu for seven years.

    What other advice do I have?

    My advice to others looking into using Jenkins on Hardened Ubuntu is to go ahead and use it. I would rate this product an 8 out of 10.

    Nirmit Dagli

    Automated pipelines have transformed our CI/CD workflows and support fast, reliable deployments

    Reviewed on Jun 09, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for Jenkins on Hardened Ubuntu is to run CI/CD pipelines.

    A quick specific example of how I use Jenkins on Hardened Ubuntu for my CI/CD pipelines includes having Jenkins pods installed on Hardened Ubuntu, and when we run our deployment, it runs through Jenkins with test cases to deploy on Ubuntu.

    What is most valuable?

    The best features Jenkins on Hardened Ubuntu offers include pipelines.

    What stands out to me about the pipelines feature is that there are multiple pipelines, and the flexibility is great. It is easy to use; we have timelines, we can see the logs, and everything functions well.

    Jenkins on Hardened Ubuntu has positively impacted my organization because it works fast and has helped us improve our CI/CD pipelines.

    What needs improvement?

    Jenkins on Hardened Ubuntu functions well in terms of improvement, and I do not have additional suggestions regarding needed improvements.

    For how long have I used the solution?

    I have been using Jenkins on Hardened Ubuntu for two years.

    What other advice do I have?

    I do not want to add anything about the features regarding integration or security.

    Regarding Jenkins on Hardened Ubuntu's AI capabilities, I do not know about its governance and security.

    Regarding Jenkins on Hardened Ubuntu's AI capabilities, I do not know about its accuracy and reliability of output.

    I give this product a rating of 10.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    reviewer2846268

    Secure pipelines have supported critical deployments but role control still needs improvement

    Reviewed on Jun 03, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for Jenkins on Hardened Ubuntu is building pipelines for CI/CD and making sure that it has the proper security where the product that we deploy demands it.

    What is most valuable?

    The best features Jenkins on Hardened Ubuntu offers are primarily centered around the security aspect of it, including a security baseline, the ability to set it up as a reverse proxy, and ensuring that it does not allow access to the internet or any other unwanted networks in the company.

    The security baseline and reverse proxy setup of Jenkins on Hardened Ubuntu has helped my team by offering a reduced attack surface, meaning we can remove or disable any unnecessary packages. The agents are exposed only to the environments they need access to. Jenkins on Hardened Ubuntu node is built in the same hardened image. Troubleshooting is easier thanks to a more predictable OS behavior compared to a Jenkins server running on a regular server with access by different teams, and we have a better compliance posture.

    Jenkins on Hardened Ubuntu really helped me out in a specific deployment scenario by having a lot of different plugins and being a tool that has been around for a very long time. For continuous integration pipelines, it can be used in a number of different ways, whether it is deploying Kubernetes containers or deploying C# code in Azure Functions, as it can handle pretty much anything thanks to the number of extensions and the community around it.

    What needs improvement?

    One area Jenkins on Hardened Ubuntu could improve is role control, particularly with RBAC permissions, as this has been an issue for a long time. While some plugins have helped in the past, they are now out of support, making it hard to establish a proper RBAC setup and integrate with SSO, MFA, and similar security measures. Adding some observability with more logs and traces would also be beneficial.

    For how long have I used the solution?

    I have been using Jenkins on Hardened Ubuntu for about five to six years on and off.

    What do I think about the stability of the solution?

    Jenkins on Hardened Ubuntu is stable.

    What do I think about the scalability of the solution?

    Jenkins on Hardened Ubuntu's scalability is acceptable, but nothing fancy, as it is an old product.

    How are customer service and support?

    I have never used customer support for Jenkins on Hardened Ubuntu, if there is any.

    Which solution did I use previously and why did I switch?

    I used Azure DevOps, CircleCI, and other tools, but I did not switch per se; they were just used in a different project.

    Which other solutions did I evaluate?

    Before choosing Jenkins on Hardened Ubuntu, I evaluated Azure DevOps and CircleCI.

    What other advice do I have?

    My advice to others looking into using Jenkins on Hardened Ubuntu is that if you really have to use it, it is a good option to give it a try. I would rate this product a 7.

    reviewer2808960

    Automated pipelines have accelerated microservice deployments and support frequent secure releases

    Reviewed on Apr 07, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for Jenkins on Hardened Ubuntu is for the deployment of my microservices, creating the pipeline when creating the new services, and we can deploy easily for microservices in any environment.

    A specific example of a pipeline I've set up in Jenkins on Hardened Ubuntu is when I need to go on the setting there and add our GitHub repository URL so that it can fetch that particular branch or that particular code, and then I can write that configuration file in our microservices, such as what the steps need to be there, including some code coverage checking, Sonar check, and some security checks, which we can do on our microservice configuration level, enabling it and deploying it by creating the new pipeline on Jenkins.

    What is most valuable?

    One of the best features Jenkins on Hardened Ubuntu offers is for deploying; we can independently deploy any microservices by just creating a pipeline using a few steps only, and that is one of the main features of Jenkins, allowing us to avoid any manual setup or other tasks, as we can also write some scripts for automation deployment.

    When I mention writing scripts for automated deployment in Jenkins on Hardened Ubuntu, the kind of scripts that have been most useful for me include some TypeScript, as well as some script files for using Jenkins scripts written specifically for deployment, so during the deployment, there are certain steps that go through that script and it will deploy.

    Jenkins on Hardened Ubuntu has positively impacted my organization by showing a lot of improvement; it reduces our time and increases our development process, and it helps a lot everywhere. The difference Jenkins on Hardened Ubuntu makes is significant, as the deployment process has gone from hours to minutes.

    What needs improvement?

    Jenkins on Hardened Ubuntu can have some enhancements; the UI can be more attractive, as it is just a normal layout right now, so we can have some kind of tiles and devise some separate area to choose that particular pipeline itself related to configuration and the pipeline, but apart from that, functionality-wise, it is good, though sometimes Jenkins is down when we are doing multiple deployments at the same time, which is one major issue.

    For how long have I used the solution?

    I have been using Jenkins on Hardened Ubuntu for the last five to six years.

    What other advice do I have?

    Jenkins on Hardened Ubuntu is a very good feature, supplying us with a continuous integration and continuous deployment process, allowing us to easily deploy frequent changes and test our features, so it is very helpful for us. There is nothing else about Jenkins on Hardened Ubuntu's features that I think is worth mentioning.

    Kasiraja Thangapandian

    Role-based automation has streamlined secure CI pipelines and supports data-driven delivery decisions

    Reviewed on Mar 02, 2026
    Review provided by PeerSpot

    What is our primary use case?

    I am still working with Black Duck. I am working with both Jenkins on Hardened Ubuntu and Coverity. I have Jenkins on Hardened Ubuntu on Ubuntu and Windows. I am utilizing almost 200 Jenkins on Hardened Ubuntu plugins on hardened Ubuntu.

    Jenkins on Hardened Ubuntu is used for automated testing as well as manual testing, and in automated testing, I am able to organize and streamline the process. Once I build or once the requirement is there, the build pipelines are triggered to get the output and ensure the testing is in progress. It is extremely useful.

    There is a role-based access system in Jenkins on Hardened Ubuntu on hardened Ubuntu and I am able to configure it for each user. For a developer, for integrator, for viewer, for reporters, there is a complete role-based access system. I call it RBAC. I have introduced these things and completely integrated with LDAP and it is highly secure.

    Real-time feedback is impacting my team's productivity positively. There are a lot of version upgrades. I am at the latest version too, and I have not seen any crash or any problem with the current environment. It is good. I am able to proceed and upgrade. I am almost having 15 to 18 Jenkins on Hardened Ubuntu instances. Globally, I am using it across India and outside India too.

    What is most valuable?

    Jenkins on Hardened Ubuntu has extremely benefited our CI/CD pipelines. The whole of our build systems are completely running on Jenkins on Hardened Ubuntu and it is a day-to-day activity. Almost 300 to 400 integrators are using Jenkins on Hardened Ubuntu. It is basically to orchestrate our workflow and it is easy for us to take the build and release to the customer. It is extremely useful.

    The metrics that I am using to measure the security effectiveness of Jenkins on Hardened Ubuntu are the DORA metrics. There is a standardized DORA metrics. I am already using DORA metrics which is exclusively for those things and there are four to five metrics that can be used to measure those things.

    What needs improvement?

    Any product that I create, I will have an improvement expectation for Jenkins on Hardened Ubuntu. The one expectation that I have is that the UI can be still improved. Some more metrics can be established. Nowadays, there are a lot of configurations. I should be able to really connect with AI as another feature that can also be integrated. These are the three or four items that can be added to the improvement toward Jenkins on Hardened Ubuntu.

    Jenkins on Hardened Ubuntu could include AI chat features in the future to make it even better. When there is a build happening or when there is a job happening, I could ask in the chat how long that takes or what is the current job running. These AI features can be included.

    For how long have I used the solution?

    I have been working with Jenkins on Hardened Ubuntu for the last 10 to 12 years.

    What do I think about the stability of the solution?

    Initially, I had a little struggle in setting up Jenkins on Hardened Ubuntu but now I have become proficient and have expertise. This is not a big concern.

    Initially, I faced some issues with plugins that might be incompatible while setting up Jenkins on Hardened Ubuntu. I had to really understand and ensure and set it up. The version and the plugin compatibility have to be checked properly. This helps me to quickly set up the environment.

    What was our ROI?

    I have seen return on investment. Approximately, it took me almost around 83 to 85 percentage to see ROI.

    What's my experience with pricing, setup cost, and licensing?

    The price for Jenkins on Hardened Ubuntu is not a constraint for me. As long as there are good features and it is a must, there should not be a problem. I have to invest in order to do my business. I do not see it as one of the constraints or limitations to work with.

    What other advice do I have?

    I am satisfied with Jenkins on Hardened Ubuntu and I am an expert with it. I am working with Jenkins on Hardened Ubuntu simultaneously on different operating systems, not only on Ubuntu but also Windows, and I find Ubuntu to be more convenient. Ubuntu is very straightforward to set up with just a few commands, which is why it is very easy. My review rating for Jenkins on Hardened Ubuntu is 8.5 out of 10.
    reviewer2795433

    Secure pipelines have reduced incidents and save significant setup and configuration time

    Reviewed on Jan 18, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for Jenkins on Hardened Ubuntu is using a secure CICD pipeline on an Amazon Machine Image, which is already secure, so that deploying code is as secure as it can be rather than running it on my own VM and worrying about the security.

    In my use case for Jenkins on Hardened Ubuntu, I write code within Visual Studio Code, push it to our code repository, and then Jenkins on Hardened Ubuntu has a webhook which allows it to link to that repository, enabling it to fetch the code and deploy it by running the CICD pipeline, making Jenkins on Hardened Ubuntu the CICD server in a secure way on Hardened Ubuntu AWS hosted.

    There is nothing unique about my workflow or how it integrates with other tools.

    What is most valuable?

    One of the best features Jenkins on Hardened Ubuntu offers is that it saves time because rather than trying to have a vanilla OS, such as Ubuntu on an EC2 instance, and then trying to secure it yourself, Jenkins on Hardened Ubuntu is already secured with a ton of insecure features disabled on the VM, which saves us time and is quite cost-effective.

    The IAM integration has helped my team because it is quicker to set up and more secure since using AWS IAM roles is natively secure, where long-term credentials can be insecure, but by using already configured IAM roles, it is much more secure.

    Jenkins on Hardened Ubuntu has positively impacted my organization because it is more secure to use rather than us trying to use a vanilla OS, lowering the attack surface of common OS-related vulnerabilities.

    What needs improvement?

    There is a maintenance overhead to using Jenkins on Hardened Ubuntu since the customer is responsible for patching both Jenkins on Hardened Ubuntu and the OS, and although security issues are somewhat handled, Jenkins on Hardened Ubuntu third-party plugins may still be insecure, and hardened images can be too restrictive.

    I do not think there are any other improvements needed for Jenkins on Hardened Ubuntu that have not been mentioned yet.

    For how long have I used the solution?

    I've used it within the last year, for a period of around one year.

    What do I think about the stability of the solution?

    Jenkins on Hardened Ubuntu is very stable, as it is maintained by AWS.

    What do I think about the scalability of the solution?

    Jenkins on Hardened Ubuntu is highly scalable because you can choose to have it on one instance, two, three, however many you want, and it automatically scales based on what you need.

    How are customer service and support?

    The customer support is part of AWS and Amazon support in general, which is always very good, with different tiers available offering quick response times and dedicated account managers for the highest tier.

    How would you rate customer service and support?

    Negative

    Which solution did I use previously and why did I switch?

    The previous solution I used was a vanilla OS, just using Ubuntu, and I switched to Jenkins on Hardened Ubuntu for increased security.

    How was the initial setup?

    I chose nine out of ten because it is very good for what it aims to do; it could be a little bit cheaper, but that is a minor thing, and I think it is reasonably priced.

    What was our ROI?

    I have definitely noticed a reduction in incidents and time saved since switching to Jenkins on Hardened Ubuntu, which saves at least between ten to twenty hours in configuration time, translating to potential savings of hundreds or even thousands of dollars.

    From a time saved perspective, this solution saves at least between ten to twenty hours, but likely more, and it could prevent potential losses of tens or hundreds of thousands if it stops a security incident.

    Which other solutions did I evaluate?

    The only other option I evaluated before choosing Jenkins on Hardened Ubuntu was just using a base Ubuntu OS rather than a secured version from the Amazon Marketplace.

    What other advice do I have?

    If you are looking to self-host Jenkins on a VM, Jenkins on Hardened Ubuntu is a very secure way to do it, but many organizations now opt for cloud-managed CICD pipelines, so it is not appropriate for everyone.

    There is no other business relationship with this vendor other than being a customer.

    I gave this product a rating of nine out of ten.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Akhilesh B N

    Integration capabilities and support are impressive

    Reviewed on Aug 07, 2025
    Review from a verified AWS customer

    What is our primary use case?

    I am using Jenkins on Hardened Ubuntu for procuring the infrastructure to deploy our applications and procuring databases for various tasks.

    How has it helped my organization?

    The benefits of Jenkins on Hardened Ubuntu include its easy integration with every tool. It can be used as both an integration tool and a deployment tool. With the help of scripts, we can easily configure Jenkins on Hardened Ubuntu in an effective way.

    What is most valuable?

    Jenkins on Hardened Ubuntu is an open-source tool that has many plugins to support all applications. This stands out as its main advantage.

    What needs improvement?

    I have not seen many disadvantages with Jenkins on Hardened Ubuntu.

    From an improvement perspective, implementing AI features would be beneficial. If AI could be integrated for scripting in the Jenkins pipeline, it would be really good for users. Since AI has been adopted for many tools recently, this integration would enhance functionality.

    For how long have I used the solution?

    I have been using Jenkins on Hardened Ubuntu for the past six years.

    What was my experience with deployment of the solution?

    The installation and deployment process is straightforward, and I have not encountered any issues.

    What do I think about the stability of the solution?

    Stability is excellent with Jenkins on Hardened Ubuntu. I have experienced minimal unavailability with the system.

    What do I think about the scalability of the solution?

    Jenkins on Hardened Ubuntu is easy to scale.

    How are customer service and support?

    We have dealt with technical support from Jenkins on Hardened Ubuntu. The support provided has been good.

    How would you rate customer service and support?

    Positive

    What was our ROI?

    There has been a return on investment for many organizations using Jenkins on Hardened Ubuntu.

    What's my experience with pricing, setup cost, and licensing?

    The organization handles the payment for Jenkins on Hardened Ubuntu. I am not certain about how they calculate the usage percentage and pricing.

    What other advice do I have?

    We are using Jenkins on Hardened Ubuntu and other DevOps tools on AWS cloud. As DevOps administrators, we use various tools to configure and manage approximately 1000-1500 servers.

    We use leasing services with AWS to reduce costs through bulk purchasing of services.

    I work with AWS cloud for infrastructure procurement and database-related tasks. I am not familiar with the distributed build features or automated alerting and auditing features, as a separate team manages those aspects.

    On a scale of 1-10, I rate Jenkins on Hardened Ubuntu a 9.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)