AWS CloudFormation

Avantages

Une utilisation parfaite pour une bonne utilisation des donnée

Inconvénients

Un peu technique comme utilisation mais quand on l’a en mains c’est top

Avantages

1. AWS CloudFormation offers me a spectacular platform to build and provision my organization's infrastructure requirements.

2. It provides me the feature of automation with various DevOps software seamlessly.

3. The compliance standards followed for each resource creation is top notch.

4. I can create, modify or delete the stack which is derived from my CloudFormation Template with ease.

5. It brilliantly integrated with multiple third-party software such as Git, Jenkins, Ansible, Docker, Kubernetes through its fascinating API functionality.

Inconvénients

1. Once you create the stack in CloudFormation, you won't be able to change the name of the stack.

2. Deep understanding about the usage of scripts is required in order to establish connection with other resources.

3. For troubleshooting, the tracking of error logs in the associated CloudWatch entries is quite challenging in CloudFormation.

Avantages

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

Inconvénients

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 envisagées 

Terraform

Pourquoi choisir AWS CloudFormation 

Much better IaC tool, cloud agnostic and supports multi-cloud deployments.

Logiciel antérieur 

Terraform

Pourquoi passer à AWS CloudFormation

Not this time.

Avantages

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.

Inconvénients

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.

Avantages

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.

Inconvénients

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

Alternatives envisagées 

Terraform

Pourquoi passer à AWS CloudFormation

We have clear strategy that we will be using only AWS cloud. Cloudformation is better compared to Terraform when it comes to state management of the infra, the possibility of rollback and the transactional nature. In Terraform we have to explicitly maintain the state in S3 bucket. Cloudformation takes care of this as it is managed service. Being transactional , we are guaranteed that the infra will always be in consistent state.

Avantages

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

Inconvénients

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

Avantages

It is very easy to use for new users and it's very easy to explain for the freshers. Since we have integrated AWS with other apps to upload and download our inputs and outputs, it works well with integration as well.

Inconvénients

Nothing much as a negative but sometimes if the servers get down we won't be able to start our Jupiter notebook to run our codes.

Avantages

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.

Inconvénients

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

Avantages

aws cloud formation can creates cloud infrastructure using declarative method without manual intervention.This helps creating cloud infra irrespective of AWS UI updates .It enable resource creation with simple commands and templates, enable complex cloud infrastructure creations and troubleshooting guide. There is large aws support to solve issue related to cloudformation template.

Inconvénients

Template creation can be excausting due to interconnecting components when multiple resources are used and they are interlinked to transfer data within the resource.
Managing and viewing budget and cost of resources utilized would not be available at ease and would need to login to console to view billing details.
Creating resources can take time as compared to creating resources in UI as it becomes more interactive experience for developer to exactly view what cloud resources are created and there interlinked components.

Avantages

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

Inconvénients

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

Avantages

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

Inconvénients

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

Avantages

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.

Inconvénients

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.

Avantages

Deep integration with almost every AWS service.
Infrastructure as Code (IaC): Reproducible, version-controlled infrastructure deployments.
Easily track, update, and delete resources as a unit.
Drift Detection and Identifies changes outside of templates.
No Additional Cost and It’s free, you only pay for the AWS resources you create.

Inconvénients

Templates can get large and hard to manage.
Slow Deployments: Especially when updating or deleting complex stacks.
Limited Looping/Logic: Lacks the flexibility of programming languages (compared to CDK or Terraform).
Syntax and behavior (e.g., rollback, conditions) can be tricky for newcomers.

Avantages

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

Inconvénients

Template size limitations deal with large setups

Avantages

AWS CloudFormation's best feature is infrastructure as code (IaC), allowing automated, repeatable deployments with version control. It simplifies resource management and reduces manual errors.

Inconvénients

CloudFormation can be slow and inflexible, especially with stack updates and rollbacks. Debugging errors can also be challenging due to cryptic messages.

Avantages

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

Inconvénients

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

Avantages

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

Inconvénients

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

Avantages

we can automate provisioning and decommission as well

Inconvénients

We didn’t find any difficulty in using cloud formation

Avantages

It has a lot of features that were user friendly

Inconvénients

Navigating and understanding how to use it was confusing

Avantages

It's a fast way to create infrastructure in AWS. Also, since Cloudformation can be setup in multiple stacks, it is easy to maintain.

Inconvénients

Many times the CloudFormation deployment fails after trying for a long time, which is frustrating. Also, the error messages are not easy to understand.

Avantages

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.

Inconvénients

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

Avantages

Template builder, Infrastructure Provisioning, Stack Visibility, History and Tracking.

Inconvénients

Sometimes stacks takes time to delete due to correlation of resources. Need to delete resources manually.

Avantages

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

Inconvénients

Need support for multi cloud Infrastructure configurations similar to Terraform tool

Avantages

For streaming purposes, I'm using it to build a clustering solution. It is the greatest tool for delivering packages, especially because the AWS CloudFormation template includes settings for Lambda, Sagemaker, and other services.

Inconvénients

There is nothing wrong with this tool, but there is a need for development in terms of setting dependencies between two stacks.

Avantages

The feature that are most impactful is the compatibility with multiple services. You can simple write a template and deploy entire environments in minutes form servers to databases. If you use Amazon's CDK you can take it a step further and write infrastructure as code in languages like typescript or python. The CDK then deploys directly to cloudformation.

Inconvénients

What I like least about cloudformation are the error messages. Occasionally they can be a bit vague, which of course makes debugging take longer than it should. This happens most often when permissions/roles are off.