AWS CodeDeploy is a fully managed deployment service that automates software deployments to a variety of compute services such as Amazon EC2, AWS Fargate, AWS Lambda, and on-premises servers. AWS CodeDeploy aims to make it easier for users to rapidly release new features, avoid downtime during application deployment, and handle the complexity of updating applications.
$0.02
per on-premises instance
HCL BigFix
Score 7.1 out of 10
N/A
BigFix, now supported by HCL Technologies since the acquisition of BigFix from IBM in 2018, is an endpoint management solution providing endpoint visibility and IT asset discovery, automated endpoint patching (BigFix Lifecycle and BigFix Patch) policy enforcement (BigFix Compliance), and software asset discovery for licensed and unlicensed software (BigFix Inventory).
N/A
Pricing
AWS CodeDeploy
HCL BigFix
Editions & Modules
AWS CodeDeploy
$0.02
per on-premises instance
No answers on this topic
Offerings
Pricing Offerings
AWS CodeDeploy
HCL BigFix
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
AWS CodeDeploy
HCL BigFix
Considered Both Products
AWS CodeDeploy
Verified User
Anonymous
Chose AWS CodeDeploy
Both have the same concept, but AWS has gained some ground over Google by creating cheaper services, and the fact they have servers wherever there is an Amazon makes the speed to access the platform faster and the jumps in the network also quicker. GCP has its global advantage …
Jenkins has been the reliable workhorse but it has aged quite a bit. The biggest issue with open source Jenkins is the requirement of hosting it by yourself, as it is not available inside AWS context as a service. That does fit into cloud-native thinking where you want to focus …
Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool.
The most important reason we use AWS CodeDeploy was we use Amazon Web Services and our ecosystem platform. We want all the software components seamlessly integrated together. The CI/CD is always an issue to our software process, and also, we don't want to have any downtime when …
We have significantly enhanced our ability to patch desktops, including laptops, desktop, cloud, virtual machines and other mobile devices used by end-users. BigFix's endpoint management functionality allows us to seamlessly patch a wide range of operating systems, such as …
The functionality seemed greater and the pricing was more advantageous for the firm at the time of purchase. The decision was made due to our business relationship with IBM, the demonstrations provided by several former users of BigFix and the expansive feature set that can be …
We used Spiceworks in small scales. BigFix is more enterprise-ready and able to support a large environment like ours. It also offers functions that are not available in Spiceworks.
Although it lacks the ability to deploy agentless scanning or patch deployments it makes up in its real-time data of devices do to the use of agents. Compared to our other patch management software Ivanti we believe that it fills the role of workstation management better than …
For greenfield projects built on AWS there are very few reasons why not to choose AWS CodeDeploy. It works out of the box and integrates seamlessly into your cloud environment. If you plan to migrate your existing legacy builds away e.g. from Jenkins, you may need to reserve a substantial amount of time for that and the benefits gained may not be worth the effort.
BigFix is well suited for patch review and deployment, but there are key features that can definitely be improved. An example is that if a specific patch is deployed, but a cumulative update that contains that patch is not deployed, the system still shows the patch as outstanding or not implemented. Another area for improvement is the customization of BigFix. The tool has many uses and can be extremely helpful, but the amount of knowledge required to customize the solution is significant and customized scripts or "fixlets" need to be created. If common things could be pre-packaged and provided to the customer community, it would allow for an easier deployment and use of the tool.
Here is where AWS as a whole stepped up big. The UI is more intuitive and easy to use. The separation is clear, and the guides are abundant. They still need to create starter tutorials for newcomers so we don't lose much time learning/teaching others. Having someone with basic knowledge and examples where they can gain experience will make it better.
While some support calls are quickly responded to, many times our engineers have been pointed to collaborative web sites such as Bigfix.me for solutions or the option of engaging professional services has been proposed. While this may seem like a good way to drive business, it is not seen as efficient a support process as could be provided to the customer base.
Both have the same concept, but AWS has gained some ground over Google by creating cheaper services, and the fact they have servers wherever there is an Amazon makes the speed to access the platform faster and the jumps in the network also quicker. GCP has its global advantage because it is extremely easy to use, but overall, AWS has more to offer as long as you know it.
We have significantly enhanced our ability to patch desktops, including laptops, desktop, cloud, virtual machines and other mobile devices used by end-users. BigFix's endpoint management functionality allows us to seamlessly patch a wide range of operating systems, such as Windows, MacOS, ChromeOS, and Linux systems, ensuring comprehensive patch management across IT infrastructures. We have established a track record of delivering secure and hassle-free patching solutions to our clients