AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run an application. Users don’t need to figure out the order for provisioning AWS services or the subtleties of making those dependencies work.…
$0
Cisco Intersight
Score 8.9 out of 10
N/A
Cisco Intersight is an operations platform that helps IT operations teams control and automate Cisco UCS, converged, and hyperconverged infrastructure. Intersight consolidates and automates infrastructure lifecycle management from data centers to the edge in one solution delivered as-a-service.
N/A
IBM Terraform
Score 8.7 out of 10
N/A
IBM Terraform (formerly Hashicorp Terraform) is a cloud infrastructure automation tool used to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It is available Open Source, and via Cloud and Self-Hosted editions.
$0
Pricing
AWS CloudFormation
Cisco Intersight
IBM Terraform
Editions & Modules
Free Tier - 1,000 Handler Operations per Month per Account
$0.00
Handler Operation
$0.0009
per handler operation
No answers on this topic
Open Source
$0
Team & Governance
$20/user
per user/per month
Enterprise
Contact sales team
Offerings
Pricing Offerings
AWS CloudFormation
Cisco Intersight
IBM Terraform
Free Trial
Yes
Yes
No
Free/Freemium Version
Yes
No
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
There is no additional charge for using AWS CloudFormation with resource providers in the following namespaces: AWS::*, Alexa::*, and Custom::*. In this case you pay for AWS resources (such as Amazon EC2 instances, Elastic Load Balancing load balancers, etc.) created using AWS CloudFormation as if you created them manually. You only pay for what you use, as you use it; there are no minimum fees and no required upfront commitments.
When you use resource providers with AWS CloudFormation outside the namespaces mentioned above, you incur charges per handler operation. Handler operations are create, update, delete, read, or list actions on a resource.
The only real comparison would be to Terraform, which is another IaC technology at the infra level. Terraform is cloud-agnostic, which means most popular cloud providers are supported. While AWS CloudFormation is AWS-only. Although, if you consider CDK, CDK for Terraform …
Since the product I'm involved is primarily hosted on AWS we use CloudFormation but in some other products where we have hybrid cloud deployments we prefer Terraform which is opensource.
As we have our whole infrastructure on AWS, that is why we selected AWS CloudFormation. AWS CloudFormation is better integrated with AWS services than other available products and also provides visibility and tracking on AWS. AWS CloudFormation is free while Terraform …
We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if …
Since Cisco Intersight Infrastructure Service is cloud-delivered, there is a great deal of flexibility found in this platform, including the ability to manage infrastructure from anywhere at any time. Cisco is also able to continually upgrade, modify, and enhance this platform, …
IBM Terraform
Verified User
Professional
Chose IBM Terraform
AWS CloudFormation is better if you just want to stick with AWS because it's integration with AWS is better, provides auto-rollback in case of failures, and has GUI to manage and view the stacks built. Terraform is better when we want to stay cloud-agnostic. Terraform is better …
HashiCorp Terraform is much better than Cloud Formation. For one, the language is just easier to use, but more importantly, the provider ecosystem is much better in HashiCorp Terraform than in Cloud Formation.
CloudFormation is only for AWS so if you're trying to deploy to another cloud provider then Terraform is your product. Terraform has lots of public support so you can find answers to questions by Googling. CloudFormation is easy to view the resources/services that are …
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.
It is highly suited for an organisation pushing for a standardised and centralised configuration of settings using policies, profiles and templates. It is highly suited for customers used to legacy UMM that need to refresh their environment, but instead of deploying them in UMM (which is still possible), to take the time and effort to learn Cisco Intersight Infrastructure Service and IMM as well as familiarise themselves with the differences between UMM and IMM, and the issues in UMM which IMM addresses and improves upon. We deployed in UMM initially then transitioned to IMM with the transition too. I cannot think of a scenario where Cisco Intersight Infrastructure Service would not be suited. Even for small-scale deployments, it provides significant benefits. Maybe if you come from another server vendor management environment, the learning curve may feel steep (e.g. many new concepts and constructs that one has to master).
Anything that needs to be repeated en masse. Terraform is great at taking a template and have it be repeated across your estate. You can dynamically change the assets they're generating depending on certain variables. Which means though templated assets will all be similar, they're allowed to have unique properties about them. For example flattening JSON into tabular data and ensuring the flattening code is unique to the file's schema.
Standardising the environment by enforcing use of updating templates.
Show the difference on a profile between what has changed and what setting was last deployed.
Perform bulk deploy operation on profiles (like server profiles).
Policies underpin all settings (e.g. no more defining individual VLANs before being able to use them, or having to clean them up manually when they are no longer in use. You deploy a Domain VLAN policy that states which VLANs are configured on a domain (either standalone) or a domain profile template (if domains profiles are bound to an updating domain profile template).
It would be great to not having to create EVERY profile within a deployment. since some items can be done be default, the defaults should be set and the deployment can be much faster.
When adding Rack servers, indicating that the CIMC interface should not being connected before powering on the system and they it will be managed by Cisco Intersight can reduce down times. We had to manually reset our CIMC after disconnecting from our OOBM switches.
The language itself is a bit unusual and this makes it hard for new users to get onboarded into the codebase. While it's improving with later releases, basic concepts like "map an array of options into a set of configurations" or "apply this logic if a variable is specified" are possible but unnecessarily cumbersome.
The 'Terraform Plan' operation could be substantially more sophisticated. There are many situations where a Terraform file could never work but successfully passes the 'plan' phase only to fail during the 'apply' phase.
Environment migrations could be smoother. Renaming/refactoring files is a challenge because of the need to use 'Terraform mv' commands, etc.
Been using Cisco Software as a service (SaaS) platform in a production environment for a large medical and health professionals that has critical healthcare and patients care dependency.
Support team is very helpful getting system updated as needed, and vendor support is fantastic. Also get a dedicated Cisco networking engine to review and advise system health and recommendations.
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.
Usability of Cisco Intersight is highly dependent on the licensing purchased. The default (free) license level provides a lot of value for the minimal amount of effort to implement. The paid license levels provide additional features (detailed inventory, configuration management and deployment, etc.)
The syntax itself is pretty straightforward. The documentation is well-maintained & easy to follow. Most cloud providers, even smaller ones, maintain official provider libraries, making discovery & learning a breeze. Some, like GCP, even provide high-level libraries on top of their own more primitive provider, making building complex infra much more manageable. The language itself is cloud-agnostic, so you can literally manage resources from multiple providers in a single Terraform repo.
Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.
I have had servers TAC cases open for issues with Cisco Intersight. Some have yet to be resolved. One case that is still open is where the HCL status ( Hardware Compatibility List ) shows not validated when It should be. We have several servers that have the exact same hardware, OS, and the same firmware. One server will show the HCL is not validated but all others will
I have yet to have an opportunity to reach out directly to HashiCorp for support on Terraform. However, I have spent a great deal of time considering their documentation as I use the tool. This opinion is based solely on that. I find the Terraform documentation to have great breadth but lacking in depth in many areas. I appreciate that all of the tool's resources have an entry in the docs but often the examples are lacking. Often, the examples provided are very basic and prompt additional exploration. Also, the links in the documentation often link back to the same page where one might expect to be linked to a different source with additional information.
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
I personally think that Cisco Intersight Infrastructure Service is at the top of its class when it comes to managing data center hardware. The cloud-connected design feels very modern and easy to use. The mobile app is something I wouldn't expect to get in a server management tool. The way it can update, monitor, and manage our servers is very nice. Overall, we are very happy with it.
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other solutions that are available in the market place.
The negative thing is that we prefer to use the UCS Manager in our company because this bare metal is integrated into the FI and no extra appliance is required. SaaS is generally not viewed favorably in Germany.
Telling the user that they have to buy Intersight licenses even if they use UCS Manager annoys our customers.
we are able to deploy our infrastructure in a couple of ours in an automated and repeatable way, before this could take weeks if the work was done manually and was a lot of error prone.
having the state file, you can see a diff of what things have changed manually out side of Terraform which is a huge plus
if state file gets corrupted, it is very hard to debug or restore it without an impact or spending hours ..
writing big scale code can be very challenging and hard to be efficient so it's usable by the whole team
