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

It is user-friendly and easy to setup and start using.

Inconvénients

When it connected it was slow and I had a difficult time with QuickBooks working in the environment.

Avantages

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.

Inconvénients

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.

Avantages

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

Inconvénients

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

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

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

Inconvénients

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

Avantages

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.

Inconvénients

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.

Avantages

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.

Inconvénients

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

Avantages

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

Inconvénients

There are a lot of functions that require more training.

Avantages

Everything about this software is amazing and super helpful

Inconvénients

there was honestly nothing that i disliked about this

Avantages

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

Inconvénients

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

Pourquoi choisir AWS CloudFormation 

Logiciel antérieur 

Pourquoi passer à AWS CloudFormation

Avantages

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

Inconvénients

Too expensive for the service if your a small business

Avantages

CloudFront distribution has great performance with very minimal loading times for users.

Inconvénients

Setting up CloudFront was a bit overwhelming at first, mainly because the AWS interface is packed with many options. If you’re new to AWS, it can feel like there’s a lot of jargon to wrap your head around. It was kind of confusing figuring out how to link it with my S3 buckets.

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

It's powerful for managing the cloud using one dashboard

Inconvénients

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

Avantages

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.

Inconvénients

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.

Avantages

Agility and change management are the key features which helps daily. Also having code controlling things always gives more confidence which is great

Inconvénients

Too many options but if we master some limited features we could really use this more efficiently

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

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

Being able to spin up resources on AWS cloud through a template is one feature that would always stand out for me. CloudFormation enables one to automate the entire build process when spinning up a new server or resources with predefined configuration in your template.

Inconvénients

You have to be well vast with YAML to be able to use this, while this shouldn't be much of a big deal for software developers, it does make template configuration a bit confusing for those without programming experience.

Avantages

I can deploy complex infrastructure stack on AWS using code. We can use the source file to spin up another environment within minutes.

Inconvénients

Only supports AWS services. Sometimes rollback feature does not work correctly, I have to find and delete the resources manually.

Avantages

AWS cloud formation is a great service offering. What I like the most is that I can set up any form of cloud tech stack for my projects and automate my entire deployment lifecycle.

Inconvénients

AWS Cloud Formation is great but sometimes if I create a few resources using cloud formation and then later if I delete those resources directly then the resource configuration lying inside cloud formation glitches, ideally it should detect that the underlying resource no longer exists and it should give an option to recreate the resource or delete the entire resource.

Avantages

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

Inconvénients

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

Avantages

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

Inconvénients

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