EXP NO:1

AIM

Create a Cloud Organization in AWS/Google Cloud/or any equivalent Open-Source cloud software
like Open Stack, Eucalyptus, Open Nebula with Role-based access control

PROCEDURE:

Create your organization

In this step, you sign into account 111111111111 as an administrator, create an organization with
that account as the management account.,

1.Sign into AWS as an administrator of account 111111111111 and open the AWS Organizations console.

2. On the introduction page, choose Create an organization.

3.In the confirmation dialog box, choose Create an organization.

Note

By default, the organization is created with all features enabled. You can also create the organization
with only consolidated billing features enabled.

AWS creates the organization and shows you the AWS accounts page. If you're on a different page,
then choose AWS accounts in the navigation pane on the left.
If the account you use has never had its email address verified by AWS, a verification email is automatically
sent to the address that is associated with your management account. There might be a delay before you
receive the verification email.
 Verify your email address within 24 hours. For more information, see Email address verification.

You now have an organization with your account as its only member. This is the management account of the
organization.
RESULT:

EXP NO:2

AIM:

Create a Cost-model for a web application using various services and do Cost-benefit analysis

Objective:

The objective of this lab is to create a cost model for a web application utilizing various AWS services.
Additionally, students will perform a cost-benefit analysis to evaluate the feasibility of the project.

Prerequired

An AWS account with access to the AWS Management Console.

Basic understanding of cloud computing concepts.

Lab Scenario:

Imagine you are tasked with designing a simple e-commerce web application using AWS services. Your
goal is to estimate the costs associated with deploying and maintaining this application.
Tasks:

Task 1: Identify Required AWS Services

1. List the AWS services you will need for your web application (e.g., EC2, RDS, S3, Lambda).

Task 2: Gather Pricing Information

1. Visit the AWS Pricing page (https://aws.amazon.com/pricing/) and navigate to the pricing details for the
services you identified.

2. Document the pricing details including any usage-based charges and tiers.

Task 3: Estimate Usage

1. Make educated estimates about the usage of each component (e.g., number of active users, data storage
requirements, expected traffic volume, API calls).

Task 4: Calculate Initial Costs

1. Determine any one-time setup costs (e.g., domain registration, SSL certificate purchase).

Task 5: Calculate Ongoing Costs

1. Estimate the recurring costs for each service (e.g., EC2 instance hourly rates, RDS monthly charges).

Task 6: Create a Sample Cost Model (Example)

Below is an example of how you might structure your cost model:

SERCICE USAGE COST TOTAL COST

EC2 2 instances $0.04/hr $28.8/month
RDS (MySQL) 1 db.t2. micro $0.20/1M $0.02/month
S3 100 GB storage $0.023/GB $2.3/month
Lambda 100,000 calls $0.20/1M $0.02/month
Total -- -- $63.72/month

Task 7: Conduct a Cost-benefit Analysis

1. Consider the benefits of the web application (e.g., revenue from sales, brand visibility).

2. Compare the estimated total monthly cost with the expected benefits.

3. Calculate the Net Benefit: `Net Benefit = Benefits - Costs`.

4. Calculate the Return on Investment (ROI): `ROI = (Net Benefit / Total Costs) * 100%`.

Task 8: Recommendations and Conclusion

1. Provide recommendations based on the cost-benefit analysis.

2. Summarize your findings and conclude whether the project is financially viable.
RESULT:

EXP NO:3

AIM:

To create alerts for usage of cloud resources in AWS, you can use AWS CloudWatch, which is a monitoring
and observability service provided by Amazon Web Services. CloudWatch allows you to collect and track
metrics, collect and monitor log files, and set alarms.

Here are the steps to create alerts for resource usage in AWS:

1. Sign into the AWS Management Console:

Go to the AWS Console (https://aws.amazon.com/console/).

Sign in with your AWS account credentials.

2. Navigate to CloudWatch:

In the AWS Console, search for "CloudWatch" in the search bar, or find it under "Management &
Governance" in the services list.
3. Create a CloudWatch Alarm:

- In the CloudWatch dashboard, click on "Alarms" in the left-hand menu.

- Click on the "Create Alarm" button.

4. Select a Metric:
 - You'll be prompted to choose a metric for your alarm. This could be a metric from an existing AWS
service (e.g., EC2, S3, RDS) or a custom metric.

5. Define Conditions:

- Set the conditions that will trigger the alarm. For example, if you're monitoring EC2 instance CPU
utilization, you can set a threshold like "CPU Utilization > 80% for 5 minutes."
6. Set Actions:

- Define what action(s) should be taken when the alarm state is triggered. You can choose to send a
notification, stop or terminate an instance, or run a specific AWS action using SNS (Simple Notification
Service) or other AWS services.
7. Configure Actions:

If you've chosen to send a notification, you'll need to set up the notification actions. This might involve
creating an SNS topic and subscribing to an email address or other endpoints to it.
8. Add a Name and Description:

- Give your alarm a name and optional description for easy identification.

9. Review and Create:

 - Review your settings and click "Create Alarm" to set up the alert.

10. Monitor Your Alarm:

- After creating the alarm, it will appear in the "Alarms" section of CloudWatch. You can manage, edit, or
delete alarms from this section.

RESULT:
EXP NO:4

AIM;

Create Billing alerts for your Cloud Organization

PROCEDURE:

Step 1: Go to your AWS Management Console.

Step 2: Now, go to your account and click on “My Billing Dashboard”.

Step 3: On your left-hand side now, you can see the option of “Billing preferences”. Click on “Billing

preferences”.

Step 4:

Here in “Billing preferences”, select “Receive Billing Alerts” and click on “Save preferences” button.
Step 5:
Now, open “Manage Billing Alerts” in the new tab. “Manage Billing Alerts” redirects you to Amazon
CloudWatch where we will be setting up our billing alerts.

Step 6:

Here, on the left-hand side go to the “Billing” section.

Step 7: Under the “Billing”, click on “Create alarm” button.

Step 8:

Now, you need to “Specify metric and conditions” in which the alarm gets triggered. Here, in Metric,

namespace is given as “AWS/Billing”, provide “Metric name” as your choice, give the desired “Currency”
for instance USD for US Dollars, then in “Statistic” select “Maximum” and finally select the “Period” in

which alarm should be generated.

Step 9:

Now, moving on to “Conditions”, we need to specify “Threshold type” as “Static” and give a condition as

“Whenever Estimated Charges is.” where you define the alarm condition. For instance, we will be selecting

“Greater/Equal” as we want to get a billing alarm when the estimated charge gets greater than/ equals to the

specified amount. After then, now you are required to specify “than…” where you define the threshold value

after which you want the alarm to get triggered. For example, we are providing an amount of 5 USD. Besides

them, we also need to make some additional configuration, i.e., “Datapoints to alarm” which has been

provided as “1 out of 1” and “Missing data treatment” as “Treat missing data as missing”.
Step 10: After specifying the metric and conditions, click on the “Next” button.
Step 11:

Now in the section of Configure Actions, the “Alarm state trigger” comprises three states. “In alarm”
is the state when the metric has crossed the specified Threshold. Similarly, the “OK” state, means all is well,
and “Insufficient data” means that the alarm has just started because of which there is not enough data
available to report an alarm state.
Step 12:

After providing “Alarm state trigger”, we are required to “Select and SNS topic” to define Simple

Notification Service which is a notification process to set the alarm. Here, you can select “Create new topic”

option.
 Step 13:
Now, in Select an SNS topic, select “Create a new topic”. Here, you are required to provide a
unique topic name. Then, provide your email address in the section named “Email endpoints that will receive
the notification…”
Step 14: Here, click on “Next” button.\

Step 15:
 In the section “Add name and description”, you are required to specify a unique name for “Alarm

name”. Also, you can mention “Alarm description” which is not mandatory. Then finally, you can click on

the “Next” button.

Step 16:

Here, you are required to “Preview and create” the Billing Alarm. Once you have verified
the setup process, you can now click on “Create alarm”.
Step 17: Since a message is being displayed on the top as “Some subscriptions are pending confirmation”,

click on “View SNS Subscriptions” as shown in the image below.

Step 18: After you get redirected to Amazon SNS, you can see that the confirmation is pending. So, go to

your Gmail account to confirm your subscription.

Step 19:

In your Gmail, click on “Confirm subscription” as shown below.

Step 20:
 Now, a message “your subscription has been confirmed” will show up. After then, you can go back
to Amazon SNS.

Step 21:

Here, in the Alarms section in CloudWatch, you can view that the status is in the “OK” state.

Step 22:
 On the left, click on “Billing” option as shown in the image. Here too, you can see that the status of

“FirstBillingAlarm” is in the “OK” state.

RESULT:

EXP NO: 5

AIM:

Compare Cloud cost for a simple web application across AWS, Azure and GCP and suggest the
best one

PROCEDURE:

Cloud storage pricing comparison

How do these major cloud providers differ in terms of storage pricing?

Here’s a comparison of prices in similar regions: AWS US East (Northern Virginia), Azure East US, and
Northern Virginia (us-east4) in Google Cloud Platform.

Cloud provider Storage (GB/Month)

Amazon S3 $0.023
Azure $0.021
Google Cloud Platform $0.023
Oracle Object Storage – Standard $0.0255

It’s clear that these cloud service providers compete closely with one another and have set similar
price ranges for storage services, with Azure standing out as the most cost-effective alternative. However, be
sure to check out other cost dimensions, such as data transfer or operations charges before picking the
storage service.

Also, pay attention to the provider’s approach to pricing changes.

Google Cloud Platform recently introduced significant price increases across various core services
around storage. Price hikes may affect other services and cloud providers considering the current
challenges like inflation rates running high around the world and supply chain issues.

Compute pricing comparison

Compute often ends up racking up a cloud bill, but it also presents the greatest opportunity for cost
optimization. That’s why it’s an essential element in every cloud pricing comparison.

We prepared this case study to show the incredible impact optimizing computer costs can have on your
bottom line.

Comparing cloud pricing – our example setup

To understand the pricing differences better, we’re going to compare virtual machines within similar regions
and with the same operating system.

The services analyzed are:

 AWS – Amazon Elastic Compute Cloud (EC2)

 Azure – Virtual Machines
 Google Cloud Platform – Compute Engine
 Oracle – Virtual Machines
Our example setup:

 Region: AWS US East (Northern Virginia), Azure East US, and Northern Virginia (us-east4) in
Google Cloud Platform.
 Operating System: Linux.
  vCPUs: 4.
Types of instances/VMs we will analyze:

 General purpose
 Compute optimized

We picked instances with four vCPUs and similar RAM (the only exception is the computer optimized
machine from Google Cloud Platform).

Here are the instances/VMs we selected for our cloud pricing comparison:

Cloud provider Instance type vCPU RAM (GB)

AWS general purpose t4g.xlarge 4 16
AWS compute
c6a.xlarge 4 8
optimized
Azure general purpose B4ms 4 16
Azure compute
F4s v2 4 8
optimized
Google Cloud Platform
e2-standard-4 4 16
general purpose
Google Cloud Platform
c2-standard-4 4 16
compute optimized
Oracle standard VM. Standard3.Flex 4 16
Oracle optimized VM. Optimized3.Flex 4 8

AWS vs. Azure vs. Google Cloud Platform: Comparing On-Demand pricing

Here’s the hourly On-Demand pricing of each of these cloud services across AWS, Azure, and Google
Cloud Platform.

Cloud pricing based on On-Demand rates

General purpose

Cloud provider Instance type Price

AWS t4g.xlarge $0.1344
Azure B4ms $0.166
Google Cloud Platform e2-standard-4 $0.150924
Oracle VM. Standard3.Flex $0.104
Compute optimized
Cloud provider Instance type Price
AWS c6a.xlarge $0.153
 Azure F4s v2 $0.1690
Google Cloud Platform c2-standard-4 $0.2351
Oracle VM. Optimized3.Flex $0.120

Takeaways:

 While Azure is the most expensive choice for general purpose instances, it’s one of the most cost-
effective alternatives to compute optimized instances.
 Google Cloud Platform offers the highest price for compute optimized instances, but this machine
has double the RAM of alternatives from AWS, Azure, and Oracle.

A note about chips and processors

Providers roll out virtual machines with different hardware and performance characteristics. As a result, you
might end up with an instance type that provides strong (and expensive!) performance your teams don’t
actually need.

Benchmarking is one way to see what you’re really paying for: you can run the same workload on each
machine and check its performance characteristics.

This approach might help you discover something interesting, just like we did. The chart below shows CPU
operation in AWS (t2.2xlarge with eight virtual cores) at varying times after several idle periods. Would you
expect such unpredictable CPU behavior within a single cloud provider?

Source: CAST AI

The 2022 Cloud Report from Cockroach Labs used this method to evaluate AWS, Azure, and Google Cloud
machines.2 One of their conclusions was that Google performs better than AWS and Azure. GCP instances
occupied 6 out of 10 spots in the top 10 instances in price-for-performance.

AWS vs. Azure vs. Google Cloud: Comparing discounted pricing with a 1-year upfront commitment
All three providers offer price discounts if you commit to using them for at least one year. This pricing
model is called Reserved Instances in AWS, Reserved Savings in Azure, and Committed use discounts in
Google Cloud.

The following tables compare the discounted pricing among AWS, Azure, and Google Cloud cloud services
with a one-year commitment period with an all-upfront payment.

Cloud pricing with a 1-year commitment

General purpose

Cloud provider Instance type Price Discount

AWS t4g.xlarge $0.084 41%
Azure B4ms $0.1118 32%
Google Cloud Platform e2-standard-4 $0.095092 37%
Oracle VM. Standard3.Flex $0.1038 1%
Compute optimized
Cloud provider Instance type Price Discount
AWS c6a.xlarge $0.1010 38%
Azure F4s v2 $0.1143 32%
Google Cloud Platform c2-standard-4 $0.14072 41%
Oracle VM. Optimized3.Flex $0.1198 1%
Takeaways:
 General-purpose instances with a 1-year commitment receive quite a similar discount rate in AWS
and Azure. Still, AWS offers a cheaper alternative.
 In both general purpose and compute optimized instances, Google Cloud Platform offers the
biggest discounts – still, it’s not the cheapest option. Note: the computer optimized GCP instance we
picked has 16 GB RAM, not 8 GB like the other instances.

CONCLUSION:

 If you are heavily invested in the Microsoft ecosystem (e.g., using Windows servers, Active
Directory, etc.), Azure might be the most seamless option.
 If your application requires strong data analytics or machine learning capabilities, or if you're
looking for competitive pricing, consider GCP.
 For a more generic, all-purpose solution with a broad range of services, AWS is a solid choice
and the mature platform might suit your needs best.
RESULT: