AWS DevOps Pro Certification Blog Post Series: AWS Config and Managed Services

This is part of the blog post series: AWS DevOps Pro Certification

Caveat emptor

Using AWS costs money, some of these services may not be part of the AWS Free Tier. You can keep costs down by tearing down anything you've created whilst learning, but it's still possible to run up a hefty bill so pay attention to the instances you setup!

I'm very lucky to be able to use my employer's AWS account. You should ask your place of work if a similar arrangement can be made as part of your study.

Velocius quam asparagi conquantur

The format of the blog posts is liable to change as I try to refine my mental model of each domain, so be sure to revisit the blog posts on a regular basis.


I've decided to cover AWS Config and AWS Managed services together since it didn't seem to have two very short blog posts.

AWS Config is a service that allows you to assess, audit and evaluate the configuration of your AWS resources. At a very basic level, this allows you to audit and track changes made to your environment.

AWS Managed Service is a service where AWS managed and operate your infrastructure on AWS. That's right, AWS will run your infrastructure (with some caveats to discussed in the next section).

Additional resources:


AWS Config strong leans towards auditing, change control and compliance. There are some use cases in the next section, but this would help AWS users who are heavily regulated like financial organisations.

AWS Managed Service is generally aimed at large organisations (enterprises) that want a safer way to migrate from on-prem to cloud-based services. Whilst the service itself doesn't handle migration (this is handled by an AWS partner), you've probably had seen this scenario before:

You work for an enterprise organisation, and the powers that be want you to move to the cloud. They don't want to pay for an expert, so they expect you to learn on the job.

Months later, when the service goes up in smoke (because using one VPC and making it visible to the Internet seemed like a quick way to get things working). The powers that be finally hire the expert to design the cloud architecture from the ground up. Who then proceeds to berates you for not knowing your EC2s from your TF2s.

The key fact to take away from that vent (sorry) is that AWS will deliver an infrastructure that is based on their own best practice. You can concentrate on getting the continuous delivery pipeline working and making the necessary changes to your applications to get them working on AWS.

Eventually, you can take over this infrastructure, but this can be done when the team feels confident enough to do so.


Some of the suggested (by AWS) uses for AWS Config are:

AWS Managed Service is aimed at enterprises want to migrate to Cloud Services, but do not have to experience to do this themselves.


There are no practical sections for these two services.

Reminder: AWS Config will cost money if you decide to play around with it as it's not covered by the free tier.

API and CLI features and verbs

There's no section for AWS Managed Services because there's no API/CLI.

Whilst there is an API/CLI for AWS Config, the common consensus is that you just need to be aware of the service. If you have come across a question during the exam that did rely on knowing the API please let me know.

AWS DevOps Pro Certification Blog Post Series