AWS CloudFormation

Pros

It is easy to provision AWS resources and update them. It supports rollback. It also allows seeing the changes that will be applied using changesets. It is transactional , either all the resources are updated or none are.

Cons

The error messages when running the Cloudformation stacks are sometimes not easy to decipher.

Alternatives Considered

Reasons for Switching to AWS CloudFormation

Pros

Included as a service in the AWS platform, can be used to provision infrastructure and services.

Cons

It's not vendor neutral which can be a problem with multi-cloud deployment which can be a problem, the competitor Terraform has many more features.

Alternatives Considered

Reasons for Choosing AWS CloudFormation

Switched From

Reasons for Switching to AWS CloudFormation

Pros

CloudFormation, like many other services, is designed for AWS from the ground up. It's supported by the developers, and it shows in how you're able to roll back changes, etc, which can't be done with Terraform.

Cons

The syntax is significantly more confusing (to me) than Terraform. HashiCorp's HCL makes it a lot easier to write and visualize what I'm trying to create. CloudFormation only works on AWS; if you'll be working on anything else, you'll have to learn a different tool.

Pros

Scaling up! It's so easy to scale up and scale down your EC2 instance depending on your requirement at any particular time. This saves your costs hourly and in the long run.

Cons

Not much is wrong with CloudFormation on AWS. However, it is not easy for a first-time no-code builder to deploy an error-free stack. You have to know what you are doing when deploying a stack or updating it! As a no-code builder like myself, I made many mistakes setting up my first stack. So please watch tutorials and go through enough learning material and equip yourself to deploy your stack correctly.

Alternatives Considered

Reasons for Switching to AWS CloudFormation

Pros

Very comprehensive and low level schema that allows capability to template up the desired cloud solution

Cons

Cloudformation can sometimes fail to update stacks due to drift issues.

Have to be extra cautious changing some resource parameters, can cause 'new' instances to of the resources to be created instead of updating the existing resource.

Alternatives Considered

Reasons for Choosing AWS CloudFormation

Switched From

Reasons for Switching to AWS CloudFormation

Pros

It's powerful for managing the cloud using one dashboard

Cons

it not easy as know, need more detail of the knowledge

Pros

The best thing about AWS Cloud is that, It has a lot of different features that we can use to make our app much more robust, fast and easy to use. It proivdes us with functions like cloud watch and email sending which we can use to keep an watch on our application and notify the developer whenever something happens.

Cons

The documentation for AWS Cloud is not upto the mark, As a begineer I found it a bit too hard to understand. A lot of the things were not clear and I was only able to make use of the features with the help of my superior

Pros

AWS CloudFormation is a infrastructure-as-code solution that allows you to bootstrap infrastructure and services within the AWS space. It contains a very comprehensive set of features to build out infrastructure with the necessary security controls and service integrations that you would need.

Cons

AWS CloudFormation has a steep learning curve for a service that only supports AWS.

Pros

providing a configuration, provisions the cloud resource as required very instantly. saves a lot of time. can also export existing resource as configuration

Cons

can provide integrations with ide tools like extension for VS Code for even simpler interface.

Pros

Infrastructure-as-code best practices, infrastructure configuration in a template based approach, infrastructure automation provisioning, cost savings, no manual overhead

Cons

Need support for multi cloud Infrastructure configurations similar to Terraform tool

Pros

I like that you can easily pick up and move infrastructure when needed programmatically.

Cons

I have not found any downside to cloud formation

Pros

CloudFormation helped us build our infrastructure quickly and reliably on AWS. Without much knowledge about infrastructure or AWS, we could use the documentation, references, and code samples of CloudFormation stacks provided by AWS and the OSS community to build our infrastructure. Instead of navigating AWS Console and being confused, we could copy/paste the resource name or configuration property to Google and quickly know what it's for and how to use it. Sharing knowledge among team members is automatic since anyone can look at the code to see the current state of the infrastructure. CloudFormation will save you plenty of time if you have multiple environments for your application. You create one template and use it for all of your environments, knowing that they will behave as expected.

Cons

CloudFormation templates cannot have complex logic, making them easy to understand, but this limited logic support sometimes forced us to create separate files for our development and production environments.

Pros

Very easy to use ..just you need to write yaml or json code for creating infrastructure and it will create all the resources you need smoothly. Also, it does not make you pay for doing this..its free, you just need to pay for resources created.

Cons

Everything's awesome but one version control system should be integrated to maintain version of stacks

Pros

AWS CloudFormation help to automate and deployment of AWS Infrastructure. It is easy to build Templates and and deploy infra into different AWS accounts. and you can easily maintain versioning so if you want build older version infra will be easy. The best thing with AWS is Technical support, There is lot of support documentation and training videos available. Also AWS technical support team is available for 24X7.

Cons

When we do setup multiple AWS Services using AWS console to migrate it to different account AWS cloudFormation has little complex procedure. I feel happy if AWS cloudFormation template gets created with click.

Pros

It assists us in a variety of ways in completing our tasks. With cloud formation, managing, adding, updating, and deleting resources is also a breeze. It has fantastic community support, which I can use to refer to and put into effect the finest deployment tactics. I utilise a combination of CloudFormation and CodePipeline to automate the delivery of numerous resources such that their integrity and customizations are not compromised.

Cons

It's as easy as it seems; you can create a template that will launch various Amazon services. There is no equivalent.

Pros

This service is a great way to look at the recent build, deployment logs for your services deployed on the cloud in various environments.

Cons

The builds sometimes take more time in running and the deployment logs are not displayed. Sometimes the stacks needs to be deleted if it can't be rollbacked.

Pros

We use this service to create multiple resources on the AWS cloud infrastructure. Like EC2, VPC, Route53, etc we create these services through CloudFormation.

Cons

Sometimes it takes more time to find the CloudFormation templates to create the resources on the AWS cloud.

Pros

AWS has a great CMS IAM were easy to use to add users . Setting admins and restrictions to Accounts were easy to setup up.

Cons

2 factor authentication sometime would rest multiple times durning server run time which causes disrubtions .wehn scaling up servers you may get over charged .

Pros

AWS gave us a way to start multiple services from a JSON or YAML file, CloudFormation. It is also possible to maintain, debug and assign environment variables that can be migrated easily to any other region.

Cons

There is no counterpart. It is as simple as it sounds, you can design a template that can start multiple Amazon services, no catch.

Pros

CloudFormation makes managing AWS resources a breeze. Consistent deployments across all regions has been an absolute game changer. The interface is very user friendly

Cons

Deleting resources can sometimes be a pain. It would be good to have a "force delete" option that will blitz resources regardless of the deletion policy.

Pros

Cloudformation makes it possible to deploy stacks that create and update services by simply updating a template. I usually use it with the AWS CDK because I’m a JavaScript developer. It makes it very easy to spin up new environments very easy.

Cons

It can be slow to update and create. Sometimes it fails to delete and you have to delete the stack manually.

Pros

The tool allows you to design your infrastructure with a fairly simple and understandable syntax.

Cons

It is not compatible with other cloud systems as do other tools that remain disconnected from the cloud used.

Pros

Give you full power to develop, deploy and manage your cloud infrastructure

Cons

A bit complex to start with
Sometimes you will need to dig online for proper documentation with an example

Pros

The documentation oh my word. I was new to cloud computing but the docs were very helpful

Cons

The only downside for me is the cost probably due to exchange rate in my country

Pros

AWS CloudFormation is widely appreciated for its ability to simplify infrastructure management through automation

Cons

While it integrates well with AWS services, working with non-AWS resources or hybrid cloud setups can be cumbersome and often requires custom resources.

Pros

One of the greatest strengths for me has been the creation of the resource control infrastructure for automating infrastructure creation. Rather than having to set each resource up individually I am able to specify them in a template and then launch everything at once. This has has reduced the amount of time I take and ''eliminates” tasks that would require my attention.

Cons

Templates used with Cloud Formation are in JSON or YAML and to start getting the picture, things can get a bit complicated…😊 Anyone who is just beginning to use such software must admit that the process is rather intimidating at the beginning stages. Until I felt at ease, I had to invest quite studying the syntax that was employed in the language.

Pros

AWS cloud formation is great thing because many benefits of this like deployment speed ,scaling ,service intergration etc.

Cons

nothing like this everything is working fine only one thing that if you are perfect in RND that means you can do easily everything.

Pros

1. Ease of integration for AWS and other services.
2. Properly documented and extremely smooth deployment process.
3. Ability to write IAAS quickly and with automation for smooth maintenance and replication activities.

Cons

1. Difficult to start with because learning the product is quite tricky.
2. Can be use for AWS hosted machines and services.
3. Managing and balancing billing is difficult.

Pros

Provides Automation it's deploy all stacks in a single command.

Cons

Template size limitations deal with large setups

Pros

I like how AWS Cloud F makes infrastructure management possible to automate by consistent, repeatable deployments with templates. Integration with other services and safety features, such as change sets and drift detection, provides flexibility as well as security.

Cons

I like how AWS Cloud Formation will automatically create and manage infrastructure as code, and ensure consistency and repeatability across environments

Pros

Facilitates cloud infrastructure management by enabling users to create, modify, and remove AWS resources in a controlled and consistent way.

Cons

Due to its role as a layer of abstraction, Cloud Formation can be challenging to manage in multi-region and multi-account environments.

Pros

It's capability to efficiently manage and deploy complex cloud infrastructure through reusable, automated processes using text-based templates.

Cons

It's rigidity and complexity in implementing changes.

Pros

Call Hub is what we use for work. I like that the calls are clear with no interruptions.

Cons

The call lists have had the same numbers under different state reps so basically we are calling the same people twice for no reason.

Pros

The best part is that it is pretty easy to use and felt easy to understand when i had started as a newbie, and i could integrate it with other AWS softwares, which further improved integration and connectivity. The VPS deployment is also very fast and easy to maintain. The readymade templates further made my job very easy. Good implementation of IAAS

Cons

Although i appreciate the integration with other AWS softwares, it still limits me from integrating it with other cloud platforms, also the yaml/json files sometimes are a pain to work with so you need some patience while dealing with it

Pros

This become so easy for the developers to create the templates and makes the Admin's life too easy.

Cons

should have been cloud agnosic as it could have helped for multi-cloud or Hybrid cloud environment.

Pros

A very reliable and efficient technique for creating infrastructure stacks.

Cons

The service can be too expensive for small businesses.

Pros

Our go-to for important and big files that require massive distribution. Our tech team implemented this with ease and chose it over other alternatives.

Cons

Can't think of a contra, to be honest. Deployment was fast and they got to it almost immediately.

Pros

Amazon web services are best platformbest

Cons

It's are some where costs are high and it's complicated to understand

Pros

Really nice and powerful way of building infrastructure stacks.

Cons

A bit too complex to use sometimes (especially the IAM part).

Alternatives Considered

Reasons for Switching to AWS CloudFormation

Pros

we can automate provisioning and decommission as well

Cons

We didn’t find any difficulty in using cloud formation

Pros

It has a lot of features that were user friendly

Cons

Navigating and understanding how to use it was confusing

Pros

It has templates for infrastructure as code.which helps me to save time.

Cons

There can be tutorials powered by AWS itself. So that anyone with basic knowledge can also have ease of access

Pros

I really appreciated the way AWS CloudFormation simplifies infrastructure management by using templates. It allows for consistent and repeatable deployments, which saves time and reduces errors. I also liked how it integrates seamlessly with other AWS services, making it easier to manage resources as code

Cons

The steep learning curve and vague error messages, especially with complex templates, are what I liked least about AWS CloudFormation.

Pros

I can define my infrastructure in code so that making it easier to manage and reproduce.
We can also use Yaml or Json to describe our AWS resources.

Cons

When a update fails in it, error messages are vague, finding the root cause of an issue is requires to Check CloudWatch Logs or manually check stats.

Pros

its interface is very good and easy to navigate

Cons

sometimes it is slow so that time delay sucks.

Pros

We use cloudformation to create and manage collection of related AWS resources in an way human intervention would not be required and things can be automated.
When we deploy stack of services they will charge us only for the resources consumed by us.

Cons

Template syntax is it JSON or YAML can have learing curve when someone new to this comes into picture .
With YAML syntax we have to be carful cause it is based on tabs and spaces

Pros

It’s very convenient to use. It has user friendly surface.

Cons

There are a lot of functions that require more training.

Pros

It was easy to upload and save data. Simple and effective.

Cons

Too expensive for the service if your a small business

Pros

It is a great product to create and use the resources.

Cons

Sometimes it can be complicated to use and require experience.

Pros

It's so easy to handle for different resources quickly and consistently.

Cons

it isn't easy to work with in multi-region and multi-account scenarios.