AWS CloudFormation vs. Red Hat OpenShift Dev Spaces

I still give it an 8 because it's one of those tools that just quietly does the heavy lifting for you but it can really test your patience when it breaks esp with deep nested stacks. It's perfect for projects where we need clean consistent environments every time. It's less ideal for quick experimental setups like new EC2 configs or Lambda permission tweaks.

Incentivized

We have a team of 500 people so it's most reliable and scalable if any new joinees. That way user's can directly create their own workspace and start working and share the work stack throughout development teams securely, to update and modify any upcoming events. The best thing about Red Hat Workspace is it's simple, with all Runtime libraries pre-installed, so no need to request a platform from Azure or any other platform provider just log in and start creating a workspace. It has version control so can easily import GIT projects can start work without worrying we don't have Java, Python or any other platform not installed just select the platform needed and start working.

Incentivized

• All resources can segregated based on stacks which provides greater visibility
• A complete audit trail of what went wrong while deploying a particular resource
• Automatically rollbacks if any service as part of CloudFormation results in an error
• The UI tool is useful

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• Can improve UI like Visual studio so that VS user's can switch without any difficulty.

Incentivized

It's easy enough to get a shared template & apply it. You don't even have to download-then-upload or copy-and-paste, a publicly-accessible url works.

Diving deeper, it has enough powerful capabilities to make the life of a platform / DevOps engineer bearable.

However, you need equally deep knowledge to troubleshoot issues, when they inevitably pop up. This is the same for all IaC technologies, as they are additional abstraction layers on top of the native API provided by the cloud providers.

Incentivized

Cloning a virtual machine creates a virtual machine that is cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information. Management guide.For information copy of the original. The new virtual Cloning virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information

Incentivized

• + We can standup a VPC in minutes
• - It took a lot of inital time to set up
• + With logging/rollback, made testing much easier.

Incentivized

• No need to request for any platform again and again.

Incentivized