This series of posts discusses making informed decisions when choosing to implement open-source tools on AWS services, adopt managed AWS services to satisfy the same needs, or use a combination of both. We look at key considerations for evaluating open-source software and AWS services using the perspectives of a startup company and a mature company as examples.
Time to value for AWS services is extremely short and limited to the time to instantiate or configure the service for your use.
Consider the following: Open-source tools on AWS services combine these considerations; the customer is responsible for the open-source implementation and the configuration of the AWS services it consumes.
AWS is responsible for the operation of the AWS Cloud and the managed AWS services.