Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides secure, resizable compute capacity in the cloud. Users can launch instances with a variety of OSs, load them with custom application environments, manage network access permissions, and run images on multiple systems.
$0.01
per IP address with a running instance per hour on a pro rata basis
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
Pricing
Amazon Elastic Compute Cloud (EC2)
Jenkins
Editions & Modules
Data Transfer
$0.00 - $0.09
per GB
On-Demand
$0.0042 - $6.528
per Hour
EBS-Optimized Instances
$0.005
per IP address with a running instance per hour on a pro rata basis
Carrier IP Addresses
$0.005 - $0.10
T4g Instances
$0.04
per vCPU-Hour Linux, RHEL, & SLES
T2, T3 Instances
$0.05 ($0.096)
per vCPU-Hour Linux, RHEL, & SLES (Windows)
No answers on this topic
Offerings
Pricing Offerings
Amazon Elastic Compute Cloud (EC2)
Jenkins
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Elastic Compute Cloud (EC2)
Jenkins
Considered Both Products
Amazon Elastic Compute Cloud (EC2)
Verified User
Team Lead
Chose Amazon Elastic Compute Cloud (EC2)
Azure VM and Google Compute Engine are alternatives to EC2. AWS EC2 is most matures and advanced of the 3. All these provide easy-to-deploy and automatically configured third-party applications, including single virtual machine or multiple virtual machine solutions.
Suitable for companies that are looking for performance at a competitive price, flexibility to switch instance type even with RI, flexibility to add-on IOPS, option to lower running cost with the regular introduction of new instance type that comes with higher performance but at a lower cost.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
The choices on AMIs, instance types and additional configuration can be overwhelming for any non-DevOps person.
The pricing information should be more clear (than only providing the hourly cost) when launching the instance. AWS DynamoDB gives an estimated monthly cost when creating tables, and I would love to see similar cost estimation showing on EC2 instances individually, as not all developers gets access to the actual bills.
The term for reserving instances are at least 12 months. With instance types changing so fast and better instances coming out every other day, it's really hard to commit to an existing instance type for 1 or more years at a time.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
You an start using EC2 instances immediately, is so easy and intuitive to start using them, EC2 has wizard to create the EC2 instances in the web browser or if you are code savvy you can create them with simple line in the CLI or using an SDK. Once you are comfortable using EC2, you can even automate the process.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
AWS's support is good overall. Not outstanding, but better than average. We have had very little reason to engage with AWS support but in our limited experience, the staff has been knowledgeable, timely and helpful. The only negative is actually initiating a service request can be a bit of a pain.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Amazon EC2 is super flexible compared to the PaaS offerings like Heroku Platform and Google App Engine since with Amazon EC2, we have access to the terminal. In terms of pricing, it's basically just the same as Google Compute Engine. The deciding factor is Amazon EC2's native integration with other AWS services since they're all in the same cloud platform.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
It reduced the need for heavy on-premises instances. Also, it completely eliminates maintenance of the machine. Their SLA criteria are also matching business needs. Overall IAAS is the best option when information is not so crucial to post on the cloud.
It makes both horizontal and vertical scaling really easy. This keeps your infrastructure up and running even while you are increasing the capacity or facing more traffic. This leads to having better customer satisfaction.
If you do not choose your instance type suitable for your business, it may incur lots of extra costs.