Skip to content

Latest commit

 

History

History
79 lines (46 loc) · 4.36 KB

File metadata and controls

79 lines (46 loc) · 4.36 KB

Week 0 — Billing and Architecture

Required Homework

I completed all the required tasks in the TODO list in the Students Portal. Here is a breakdown of all the things I did.

Screenshot

Firstly, I had already set up all the prerequisites that was told to do so like setting up Gitpod, Lucid charts, etc

I watched all the videos in the playlist and understood what the Week 0 is all about since I missed the live class. These include the recording of the live class, video about pricing and free tier by Chirag Nayyar, video by Ashish Rajan/Cloud Security Podcast and all the extra videos by Andrew.

Then I recreated the Recreate Conceptual Diagram and the Logical Architectural Diagram in Lucid Charts. I tried to make it in a different layout.

Recreate Conceptual Diagram:

Screenshot

Lucid Charts link

Logical Architectural Diagram:

Screenshot

Lucid Charts link

Once I was done with that, I went to the AWS console and created an IAM user with admin privileges. I already have an AWS account and an IAM user with admin privileges that I use to experiment an learn. I created a new one specifically for the bootcamp. After creating the user, I enabled MFA as well.

Screenshot

Then I checked out CloudShell.

Screenshot

I used the AWS console to generate Access Key.

Screenshot

I used the GitPod integration in my GitGub to take me directly to the GitHub Workspace and updated the yaml file to add the task that automatically installs AWS cli each time I open the GitPod workspace.

Screenshot

I used these commands to set these credentials for the current bash terminal:

export AWS_ACCESS_KEY_ID="my_ID"
export AWS_SECRET_ACCESS_KEY="my_secret_key"
export AWS_DEFAULT_REGION=us-east-1

Then ran these commands to make GitPod remember these credentials if I relaunch my workspace:

gp env AWS_ACCESS_KEY_ID="my_ID"
gp env AWS_SECRET_ACCESS_KEY="my_secret_key"
gp env AWS_DEFAULT_REGION=us-east-1

Then I used the AWS console to create two Budgets.

One Monthly Cost Budget with 3 Alerts. Alerts: When the Actual cost is greater than 85% of the budgeted amount (10$), when the Actual cost is greater than 100% of the budgeted amount (10$), when the forecasted cost is greater than 100% of the budgeted amount (10$).

Screenshot

One Monthly Credit Budget with 3 Alerts. Alerts: When the Actual credit usage is greater than 85% of the budgeted amount (10$), when the Actual credit usage is greater than 100% of the budgeted amount (10$), when the forecasted credit usage is greater than 100% of the budgeted amount (10$).

Screenshot

Later, I created a CloudWatch Billing Alert which sends an Email notification through SNS when the Estimated Charges Threshold is greater than 10$.

Screenshot

Homework Challenges

I am currently doing the 100 Days of Cloud challenge and in that I have experimented with the AWS Well Architected Framework and the opened a support ticket and requested for a service increase before.

AWS Well Architected Framework

Increase service limits/quotas in AWS