Over the past few years, we have seen more and more
organizations of every size trying to adopt DevOps practices.
Successfully implementing DevOps practices is not easy.
Depending on the company's size, it can take several months or
even years. Every company has its own unique history, culture,
and way of working, and thus will implement it differently.
Today we will look how AWS provides various tools to help us
adopting to DevOps easily.
Suppose we want to create an application with microservices architecture and deploy it to servers. We want to implement this using DevOps practices. Let's see all the services AWS provides which will help us in fulfilling these requirements.
AWS CodeStar service enables us to develop, build, and deploy
applications on AWS. We can perform all the tasks in any
software development like project management, development,
integrated issue tracking, deployment, all in one place. We
can deploy entire continuous delivery toolchain in minutes.
Another perk is that here is no additional charge for using
AWS CodeStar. We only pay for AWS resources we use like
We will use this service to setup our code repository and project management dashboard.
AWS EC2 System Manager is a service which enables visibility
and control of whole infrastructure from single point. With
Systems Manager, you can group resources, like Amazon EC2
instances, Amazon S3 buckets, by application, view operational
data for monitoring and troubleshooting, and act on your
groups of resources. We can run single command on all grouped
instances without having to take SSH and run command on each
instance one by one.
In our case, we will need this to patch our production instance time to time without need to manually handle all the instances.
AWS Config continuously monitors and records your AWS resource
configurations. We can track relationships and resource
dependencies among resources. We can define competency rules
in Config for AWS resources to validate if they meet required
We will use this service to monitor whether our production instances have only port 443(https) and if they don't, they will be shown as non-compliant in our Config dashboard.
AWS X-Ray does what its name sounds. It is used as tracing service which help analyze and debug production applications. It is useful in our microservices architecture pattern as X-Ray provides an end-to-end view of requests as they travel through your application. So it is helpful for us as we can trace at exactly what component our request is failing.
"Managing daily releases of 20+ micro services across different environments has never been a breeze. Thanks to team Flentas for helping us implement automatic release pipelines on cloud."
Yogesh Tripathi, Head and VP, COE