Written Labs – Logging and Monitoring – ANS-C01 Study Guide
Written Labs
Written Lab 5.1: Enable CloudWatch Detailed Monitoring for an Instance That Has Already Been Enabled
- Open the Amazon EC2 console at https://console.aws.amazon.com/ec2.
- In the navigation pane, choose Instances.
- Select the instance and choose Actions, Monitoring, Manage, and Detailed Monitoring.
- On the Detailed Monitoring detail page, for Detailed Monitoring, select the Enable check box.
- Click Save.
Written Lab 5.2: Enable CloudWatch Logging from the Web Console
- Open the AWS Management Console (https://console.aws.amazon.com) and sign in to your AWS account.
- Navigate to the CloudWatch service by either searching for CloudWatch in the search bar or locating it under the Management & Governance section.
- In the CloudWatch dashboard, click Logs in the left navigation menu to access the CloudWatch Logs interface.
- Click the Actions button and select Create Log Group to create a new log group.
- Enter a unique name for your log group in the Log Group Name field. For example, enter MyApplicationLogs.
- Specify a Retention (Days) value to determine how long log data will be retained in the log group. The default retention period is indefinite, but you can set a specific number of days based on your requirements.
- Click the Create button to create the log group.
- Once the log group is created, you can click its name to access its details and configure log streams.
Written Lab 5.3: Enable CloudWatch Alarms from the Web Console
- Open the AWS Management Console (https://console.aws.amazon.com) and sign in to your AWS account.
- Navigate to the CloudWatch service by either searching for CloudWatch in the search bar or locating it under the Management & Governance section.
- Click Alarms in the left navigation pane.
- Click the Create Alarm button.
- Select the metric for which you want to create an alarm. You can choose from a list of available services and metrics.
- Specify the conditions for the alarm, such as the threshold value, comparison operator (greater than, less than, etc.), and the duration for which the condition must persist.
- Select the metric for the alarm.
- Choose the specific metric dimension for the alarm if applicable.
- Define any additional filters or dimensions based on your requirements.
- Specify the actions that should be taken when the alarm state is triggered. These actions can include sending notifications, triggering autoscaling actions, or invoking AWS Lambda functions.
- Configure the appropriate action settings, such as email addresses for notification or selecting specific AWS resources to act upon.
- Choose the notification options for the alarm. This includes specifying the Amazon SNS topic or an email address to receive the alarm notifications.
- Review the alarm configuration to ensure all settings are accurate.
- Provide a meaningful name and optional description for the alarm.
- Click the Create Alarm button to create the alarm.
Written Lab 5.4: Create a VPC Reachability Analyzer from the Web Console
- Open the AWS Management Console (https://console.aws.amazon.com) and sign in to your AWS account.
- Navigate to the VPC Reachability Analyzer service by either searching for Reachability Analyzer in the search bar or locating it under the Networking & Content Delivery section.
- Click Create Analyzer to begin the configuration process.
- Provide a name and description for the analyzer.
- Choose the AWS region where your resources are located and where you want the analyzer created.
- Choose the source and destination components for analysis such as a VPC, subnet, security group, or instance.
- Choose the traffic direction for analysis, either inbound, outbound, or bidirectional.
- Specify the protocol and port range you want to analyze.
- Select the VPC Flow Logs or AWS PrivateLink analysis method.
- Review the analyzer configuration and review the settings.
- Click Create Analyzer.