Amazon Web Services (AWS), established in 2006, is focused on providing essential infrastructure services to businesses globally in the form of cloud computing. The key advantage offered through cloud computing, particularly via AWS, is its capacity to shift fixed infrastructure expenses into flexible costs. Businesses have been able to forgo extensive planning and procurement of servers and other Information Technology (IT) resources, owing to AWS. AWS seeks to provide businesses with prompt and cost-effective access to resources using Amazon's expertise and economies of scale, as and when their business requires. Currently, AWS offers a robust, scalable, economic infrastructure platform on the cloud powering an extensive array of businesses worldwide. It operates across numerous industries with data center locations in various parts of the globe including U.S., Europe, Singapore, and Japan.
Do You Manage Peer Insights at Amazon Web Services (AWS)?
Access Vendor Portal to update and manage your profile.
- We like the fact that we don't need to use any third-party providers since CloudFormation is enough for all our AWS services needs - Automatic rolling back of failed changes is another feature that we love, and it has saved us a couple of times - It also helps us control who can create, update and delete specific resources by applying IAM roles - We also found that it keeps things consistent across different environments
I like the ability to control the versions. Change sets help you review updates before applying them.
The following are the key aspects of the service that I like: Consistency of deployment and speed at which environments can be spun up, thus removing human error. The ability to use version control, such that templates can be stored in github and therefore tracked. It is a native tool available through AWS, therefore no need for vendor integration and such like. And finally, the ability to manage costs from one centralized location.
- We noticed that working with larger and complex templates becomes hard to read if we don't use macros or nesting - We also found that debugging sometimes requires manual intervention because the errors are vague - There should be some feature for creating reusable modules and sharing between teams
Templates grow complex fast and are hard to read. Stack failures can be hard to debug. Rollbacks take time and sometimes leave resources in a failed state.
Nothing, since it works extremely well and as expected.