0% found this document useful (0 votes)
6 views18 pages

Challenging Task AWS

Uploaded by

gkashvi026
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views18 pages

Challenging Task AWS

Uploaded by

gkashvi026
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

LABORATORY REPORT

CHALLENGING TASK
<AWS SOLUTIONS ARCHITECT >
<CSE3016 >
<A14+B11+B12+B13+E11+E12>
Submitted by

NAME: ANURAG DUBEY


REG. NO.: 22BCE10262

B TECH

Submitted to

Mr. Satyabrata Nath


Teaching Fellow

SCHOOL OF COMPUTER SCIENCE AND ENGINEERING


(SCOPE)
VIT BHOPAL UNIVERSITY
July-August 2025
1) Set up CloudWatch monitoring for AWS resources, create custom
metrics and alarms, analyse logs, and troubleshoot performance
issues using CloudWatch.

Step 1: Log In to AWS Console

Step 2: Navigate to CloudWatch


Step 3: Metrics view for an AWS resource
Step 4: Verify Automa c Matrics Collec on

Step 5: Open AWS CLI


STEP 6: Create Custom Metrices

STEP 7: Go to CloudWatch -> Alarms -> Create alarm

STEP 8: Select metrics


STEP 9: Configure Log Groups
STEP 10: Create Log Group
STEP 11: Performance Troubleshoo ng Strategies Create Comprehensive
Dashboards: Go to CloudWatch Dashboards Create dashboard

STEP 12: Anomaly Detec on Setup


aws cloudwatch put-anomaly-detector \
--namespace AWS/EC2 \
--metric-name CPUU liza on \
--dimensions Name=InstanceId,Value=i-1234567890abcdef0 \
--stat Average

- Log Analysis:
# Find correla ons between errors and performance
fields @ mestamp, @message, @dura on
| filter @message like /ERROR/ or @dura on > 5000
| sort @ mestamp desc
- Resource U liza on Analysis:
# Analyze resource pa erns
fields @ mestamp, @memory, @dura on
| filter @type = "REPORT"
| stats avg(@memory), avg(@dura on) by bin(1h)
2. Implement Mul -Factor Authen ca on (MFA) for AWS Accounts and
Enforce MFA Usage via IAM Policies, validate through CloudTrail Logs, and
Configure Op onal Login Alerts via SNS.

Step 1: Open the IAM service

Step 2 : Go to the sidebar, click "Users," and select a user and create a user
Step 3: Click the "Security creden als" tab. Under "Mul -Factor
Authen ca on (MFA)," choose "Manage" or "Assign MFA device."

Step 4: Create IAM Policy to ENFORCE MFA


Step 5: Create a Policy
Step 6: Open the JSON editor, (do not save):

Step 7: Simulate A aching Policy to a User/Group


 In “User Groups” or “Users,” click “Add Permissions.”

 Find the policy, select—but do not finish adding.


Step 8: Validate with CloudTrail Logs (Simulated)
 In AWS Console, open CloudTrail service.
 Look for events named ConsoleLogin. Filter by your test user and view
event details.
 Find the "MFAUsed" or "mfaAuthen cated" fields in the event JSON
for successful/failed login a empts.

Step 9: Simulate SNS Alert Setup for Login Event


 Open Amazon SNS in AWS Console.
 Click “Topics” → “Create topic.” Fill in topic name and select
“Standard.” Do not create—just preview.

 Click into your topic, choose “Create subscrip on.” Select “Email” as
protocol, fill any email (not yours), and screenshot but do not finish
crea on.

 Open CloudWatch/Event Bridge. Preview crea ng a rule on “AWS


Console Login” events to no fy SNS Topic.

You might also like