The solution was designed to serve managed Chef/Puppet to customers, unfortunately, all of them will reach End of Life withe the end of May 2024. During the time of writing this article (1-half of March), you can read about it on the public service page. OpsWorks. So as a summary, nice solution unfortunately based on Chef/Puppet, not a SaltStack, also the idea of stacks could be a blocker for a multi-cloud... - Source: dev.to / 2 months ago

AWS OpsWorks is a configuration management service that uses Chef, an automation platform that treats server configurations as code. OpsWorks uses Chef to automate how servers are configured, deployed, and managed across your Amazon Elastic Compute Cloud (Amazon EC2) instances or on-premises compute environments. OpsWorks has two offerings, AWS Opsworks for Chef Automate, and AWS OpsWorks Stacks. For more... - Source: dev.to / 2 months ago

EBS - 30GB per month of General Purpose (SSD) or Magnetic(12mo). - Source: dev.to / over 1 year ago

The nodes created and used within the cluster are largely dependent on your use case. For this project I setup a node group with two nodes, r5a.large EC2 instances, each with a 400GB Elastic Block Storage (EBS) volume that I'll be setting up for persistent storage. I'm not doing any autoscaling - yet, but you may want to explore that avenue. - Source: dev.to / over 1 year ago

The database storage piece is covered by EBS instances. This is where the data actually lives—your disk storage and file system. (EBS stands for Elastic Block Store). - Source: dev.to / almost 2 years ago

Currently, the only supported cloud driver is AWS EBS, more coming. CSI driver has a really simple interface:. - Source: dev.to / about 2 years ago

Ahh, that makes sense. I have never used or even really looked into EBS, so I'm unfamiliar with the various options/etc. I was pulling my info from their main EBS page:. Source: over 2 years ago