Understanding your AWS environment through AWS Config
With the number of services rising each year in AWS, it’s easy to comprehend how difficult it can be to understand what resources you might be running within your environment. How can you keep up with what instances you have running, where, what are they running, and are the resources still needed? You might be running an infrastructure that is no longer required and got overlooked among thousands of other virtual devices in production.
With a vast network of resources running within your account, do you have a clear understanding as to which resource is connected to which? What ENI is connected to which instance? Which subnet is that instance running in? Which subnets are connected to which VPCs? Do you have a logical mapping of infrastructure that quickly and easily allows you to identify a blast radius should an incident occur or visibility into resource dependencies should you change your configuration?
On top of...
