AWS CodeDeploy vs. EMCO Remote Installer vs. Red Hat Satellite

Getting the code from Git Hub, uploading it to the repository, making changes, and deploying it to a specific environment makes AWS tremendous and easy to work with. Once you know how to do it, it is easy to replicate. On the other hand, if you are new, it gets confusing, and you need guidance on the steps to take not to compromise the application.

Incentivized

Red Hat Satellite works amazingly with servers that need more control over their packages. For one or two servers that you're just doing "dnf update" Red Hat Satellite is way overkill.

Incentivized

• Integration with other AWS services
• No administration required
• Unified and easy process for dev teams

Incentivized

• Patches
• License Management
• Dashboards / Visibility

• There is one limitation is it can't do multi-tier apps
• It is not possible to control the order in which deployment occurs if more than one deployment attempts to run at the same time
• AWS CodeDeploy does not integrate with GitHub

Incentivized

• I woud love for it to provide the same functionality for non-RHEL OS's
• Containerized Installation
• Simplified workflow setup

Incentivized

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.

Incentivized

When you're first getting into the platform, the GUI can be a little confusing. It takes a little while to get accustomed to where everything is, and what everything is used for. I highly recommend prior training / classes before diving into the platform. This will ensure a better transition into the platform, and more likely to use more features of it overall due to the new knowledge gained

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

Incentivized

• AWS CodeDeploy has reduced the engineer involvement in deployments
• Our QA team has been able to effectively deploy tickets for testing, and our Release Managers can manage production deployments
• Progress indicators have given us a better baseline for deployment times, which is helpful for time-sensitive releases

Incentivized

• We have been able to automate the update process to not require after-hours monitoring.
• Centralizing updates has greatly reduced the overall time servers are down and processing their individual updates.
• We are able to bring our own RPM packages in and stage them in the same deployment model as official Red Hat packages.

Incentivized