December 2020 Summaries

AWS Config is a comprehensive service offered by Amazon Web Services that provides users with a detailed view of their AWS resource inventory, configuration history, and change notifications, aiding in security and governance. It allows for continuous monitoring of resource configuration changes, sending alerts when modifications occur to ensure compliance with internal and regulatory standards. The service supports a wide array of AWS resources, such as EC2 instances, RDS databases, and Lambda functions, and integrates with other AWS services like Amazon S3 and Amazon CloudWatch for a unified overview. Users incur costs based on the number and type of AWS resources monitored, the volume of configuration items logged, and the data stored. To enable AWS Config, users must sign in to the AWS Management Console, access the AWS Config console, set up configurations for resource types, storage, notifications, and permissions, and then confirm to initiate monitoring.

On November 25, 2020, Amazon Web Services' US-EAST-1 Region experienced a multi-hour outage due to an addition of capacity to its Kinesis service, which exceeded the maximum number of allowed threads, affecting over 100 companies including Adobe, Flickr, Twilio, and Roku. The incident highlighted the vulnerabilities of relying on a single-region architecture, underscoring the importance of adopting multi-region disaster recovery (DR) strategies and potentially multi-cloud architectures to ensure business continuity. Best practices for preventing similar outages include using global DNS load balancers to distribute traffic across regions, implementing cross-region backups for critical data, and employing emerging techniques such as continuous simulation for proactive outage management. Tools like Lightlytics can help organizations map the impact of outages on business functionalities and validate multi-region strategies to ensure operational resilience in the face of regional disruptions.