What is AWS OpsWorks?
Who uses AWS OpsWorks?
AWS OpsWorks Integrations
Why developers like AWS OpsWorks?
Here are some stack decisions, common use cases and reviews by companies and developers who chose AWS OpsWorks in their tech stack.
Stitch is run entirely on AWS. All of our transactional databases are run with Amazon RDS, and we rely on Amazon S3 for data persistence in various stages of our pipeline. Our product integrates with Amazon Redshift as a data destination, and we also use Redshift as an internal data warehouse (powered by Stitch, of course).
The majority of our services run on stateless Amazon EC2 instances that are managed by AWS OpsWorks. We recently introduced Kubernetes into our infrastructure to run the scheduled jobs that execute Singer code to extract data from various sources. Although we tend to be wary of shiny new toys, Kubernetes has proven to be a good fit for this problem, and its stability, strong community and helpful tooling have made it easy for us to incorporate into our operations.
AWS OpsWorks's Features
- AWS OpsWorks lets you model the different components of your application as layers in a stack, and maps your logical architecture to a physical architecture. You can see all resources associated with your application, and their status, in one place.
- AWS OpsWorks provides an event-driven configuration system with rich deployment tools that allow you to efficiently manage your applications over their lifetime, including support for customizable deployments, rollback, partial deployments, patch management, automatic instance scaling, and auto healing.
- AWS OpsWorks lets you define template configurations for your entire environment in a format that you can maintain and version just like your application source code.
- AWS OpsWorks supports any software that has a scripted installation. Because OpsWorks uses the Chef framework, you can bring your own recipes or leverage hundreds of community-built configurations.