Online SOA-C02 Questions Video

To analyze CloudWatch logs across multiple AWS Lambda functions for historical errors, the most operationally efficient way is to use AWS Glue and Amazon Athena.

AWS Glue and Amazon Athena:

AWS Glue can crawl the data in S3, creating a catalog that makes it queryable.

Amazon Athena allows you to run SQL queries on the data cataloged by AWS Glue.

Steps to Implement:

Set up an AWS Glue crawler to index the logs stored in S3.

Configure the crawler to create a table in the AWS Glue Data Catalog.

Use Amazon Athena to query the table for errors using SQL. Since errors have a common string prefix, you can use SQL queries to filter and find these errors.

AWS Glue

Amazon Athena

This is a classic decoupling scenario — SQS is used to buffer requests between frontend (producer) and backend (consumer) to handle sudden traffic spikes.

From SQS documentation:

SQS is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications.

This approach ensures messages are not lost and the backend can process at its own pace.

To support a wide variety of cloud storage workloads, Amazon EFS offers two performance modes, General Purpose mode and Max I/O mode. You choose a file system's performance mode when you create it, and it cannot be changed. If the PercentIOLimit percentage returned was at or near 100 percent for a significant amount of time during the test, your application should use the Max I/O performance mode.

To automate the initialization of additional EBS volumes on Windows EC2 instances, the most effective approach is to integrate initialization scripts within the instance so that they execute upon startup:

Configure Initialization Script: Use a Windows PowerShell script (InitializeDisks.ps1) to initialize and format the additional EBS volumes. The script can assign drive letters based on configurations specified in DriveLetterMappingConfig.json.

Automate at Launch: Ensure that the PowerShell script runs automatically upon instance startup. This can be configured through Windows Task Scheduler or by setting it up in the startup folder.

Create a Custom AMI: Once the instance is configured with the script and successfully initializes the disks on startup, create a new AMI from this setup. This AMI can then be used to launch new instances that will automatically initialize their additional EBS volumes with no manual intervention required.

This method leverages native Windows tools and AWS capabilities to automate EBS volume initialization, enhancing operational efficiency without additional external dependencies.