In the previous four posts, I explained AWS Landing Zone in general, the structure of AWS organization, and basic security
Problem statement A modern microservices architecture allows a large application to be separated into smaller independent parts, with each part
Problem statement Sometimes companies have complicated business logic that requires a custom scheduler or autoscaler in a Kubernetes cluster. The
Problem statement Many organizations try to achieve higher development release velocity, especially in a competitive environment. Moreover, in a big
Problem statement Security in a cloud contains many layers, so it can be quite challenging to cover everything, especially if
Problem statement There are many different and interesting DevOps tools on the market nowadays. Companies can use and combine them
Problem statement Kubernetes secret is not the best place to keep sensitive data. Even though EKS supports adding KMS envelope
Problem statement Using a multi-account AWS environment was mentioned many times in previous posts as the best practice for companies
Problem statement Using multiple AWS accounts is one of guidelines to set up a well-architected environment. By using multiple accounts,
Security is essential for every organization, that’s why Automat-it pays great attention to it during project delivery and well-architected review.