Cloud Intelligence Dashboards Framework for AWS Organization

According to the Shared Responsibility Model AWS is responsible for «Management of the Cloud”, while a customer is responsible for Security and Operations in the Cloud + attention to costs as AWS provides virtually unlimited capacity on the «pay as you go» model. There are native AWS tools like AWS Trusted Advisor, AWS Cost Explorer, […]

Simulating failures in Amazon Aurora MySQL / PostgreSQL

image header

Clouds allow us to design highly-available and fault-tolerant systems quite easily. Moreover, we can use managed services (for example, databases) to reduce the operational overhead and focus on our business logic. Design and implementation are not enough; we should also test how our system tolerates failures and continuously improves. In this post, we will look […]

Determining data sentiment in the Amazon Aurora database using Amazon Comprehend

headline image

Problem statement Collecting customer feedback is essential for every business. But collecting is not enough. We must understand and react to them to improve our product and grow the business. Processing feedback manually was a common thing earlier, and many companies still do it nowadays, but we live in the era of machine learning, and […]

Retired third-party CloudFormation extensions. Registering a private extension.

Problem statement A long time ago, we used public third-party CloudFormation extensions to deploy the EKS cluster with deployed Helm charts as part of a single CloudFormation template. AWS introduced many cool things since then, for example, EKS add-ons, so such an approach may not be entirely relevant nowadays. But in our case, the customer […]

Monitoring Kubernetes jobs status in Amazon EKS. Cronitor or Prometheus

Problem statement In the previous post, «How we migrated applications from Heroku to AWS» I described the migration planning, process, and problems encountered. Once we migrated, operations and monitoring became a cornerstone. Just for general understanding, here is what we got after the migration: EKS cluster with several node groups, a set of controllers (Cluster […]

How we migrated applications from Heroku to AWS. Issues and limitations from AWS and Heroku sides.

image header

Inputs and requirements Our customer had a production-running application in Heroku, consisting of several containerized Web applications and APIs (dynos), PostgreSQL database, Redis, RabbitMQ, and Jobs (Workers) running depending on a message queue in RabbitMQ. The business decision was made to migrate to AWS because Heroku became too expensive, and Automat-it was chosen to design […]