Lab Manual

Ex.1:

Creating a Cloud Organization with Role-based Access Control (RBAC) can vary based on the cloud
platform or open-source solution you choose. Below, I’ll outline how you can achieve this on AWS and
Google Cloud.

AWS:

1. Create an AWS Organization:

- Sign in to AWS Management Console.

- Open the AWS Organizations console.

- Choose “Create organization” and follow the steps.

2. Set Up Accounts:

- Create member accounts within the organization.

3. Implement RBAC with AWS Identity and Access Management (IAM):

- Define IAM roles for different roles (e.g., Admin, Developer, Operator).

- Attach policies to roles to grant specific permissions.

Google Cloud:

1. Create a Google Cloud Organization:

- Open the Cloud Console.

- In the Google Cloud Console, go to the Organization page.

- Choose “Create Organization” and follow the instructions.

2. Set Up GCP Projects:

- Create projects under the organization.

3. Implement RBAC with Identity and Access Management (IAM):

- Roles could include roles like Owner, Editor, and Viewer.

Open Source Cloud Solutions (e.g., OpenStack):

1. Deploy OpenStack:

- Install and configure OpenStack components.

2. Configure Projects:

- Create projects within OpenStack.

3. Implement RBAC:

- Leverage Keystone, the identity service in OpenStack, to define roles.

- Assign roles to users for specific projects.

Remember, OpenStack, Eucalyptus, and OpenNebula have different deployment and configuration
processes. Ensure to refer to their specific documentation for detailed steps.

Choose the solution based on your requirements, scalability, and familiarity with the platform. Each has
its strengths and use cases.

Ex.2:

Creating a cost model for a web application involves estimating expenses associated with various
cloud services. Here's a simplified example for AWS, but the general approach applies to other cloud
providers as well. The cost-benefit analysis involves weighing the costs against the benefits to make
informed decisions.

Cost Model for AWS Web Application:

1. Compute Resources:
 - EC2 Instances:

- Estimate the number and type of instances needed.

- Consider On-Demand, Reserved, or Spot instances.

2. Storage:

- Amazon S3:

- Estimate storage needs for static assets.

- Consider data transfer costs.

3. Database:

- Amazon RDS or DynamoDB:

- Estimate database size and throughput requirements.

- Consider reserved instances for cost savings.

4. Content Delivery:

- Amazon CloudFront:

- Estimate data transfer and request costs.

- Consider geographical distribution needs.

5. Load Balancing:

- Elastic Load Balancer (ELB):

- Estimate costs based on the number of requests and data processed.

6. Monitoring and Logging:

- Amazon CloudWatch and AWS CloudTrail:

- Estimate costs for monitoring and logging services.

7. Security:

- AWS WAF, AWS Shield:

8. Networking:

- VPC, AWS Direct Connect:

- Estimate costs for networking resources.

9. Management Tools:

- AWS Systems Manager:

- Estimate costs for management and automation.

Cost-Benefit Analysis:

1. Benefits:

- Increased Scalability: Consider the ability to scale resources based on demand.

- Pay-as-You-Go: Cloud services often follow a pay-as-you-go model, providing flexibility.

- Managed Services: Outsourcing infrastructure management can reduce operational overhead.

2. Costs:

- Initial Setup: Consider the costs associated with initial setup and migration.

- Ongoing Operational Costs: Compute, storage, and data transfer costs.

- Training: Factor in training costs for teams unfamiliar with the cloud platform.

3. Scenarios:

- Analyze different usage scenarios to understand how costs vary with demand.

- Consider potential growth and its impact on costs.

4. Alternative Solutions:

- Explore alternative services or providers to identify potential cost savings.

- Assess the risk and compliance factors associated with each service and their impact on costs.

Remember, this is a simplified model, and actual costs may vary. It's crucial to regularly review and adjust
the cost model based on evolving application requirements and cloud service pricing changes.

Ex.3:

Creating alerts for cloud resource usage involves setting up monitoring and defining conditions that
trigger notifications. Below are general steps for AWS and Google Cloud, but the process may vary
slightly depending on the specific services you're using:

AWS:

1. Amazon CloudWatch:

- Navigate to the CloudWatch console.

- Create an alarm.

- Define conditions (e.g., CPU utilization, network activity).

- Set the threshold for triggering the alarm.

- Configure actions, such as sending a notification to an SNS topic or triggering an Auto Scaling policy.

Google Cloud:

1. Stackdriver Monitoring:

- Go to the Cloud Console and navigate to Monitoring.

- Create a new alert policy.

- Define conditions based on metrics (e.g., CPU usage, disk I/O).

- Set a threshold for triggering the alert.

- Configure notification channels, such as email, SMS, or a Pub/Sub topic.

Open Source Cloud Solutions (e.g., OpenStack):

- Deploy Prometheus for monitoring.

- Define alerting rules in Prometheus.

- Set up Alertmanager to handle alerts.

- Configure notification channels in Alertmanager.

General Steps:

1. Define Metrics:

- Identify key metrics relevant to your resource usage (e.g., CPU, memory, storage).

2. Set Thresholds:

- Determine acceptable thresholds or limits for each metric.

3. Configure Alerts:

- Use the cloud provider's monitoring system to create alerts based on defined thresholds.

4. Notification Channels:

- Set up notification channels (e.g., email, messaging services) to receive alerts.

5. Testing:

- Test the alerts to ensure they trigger as expected.

6. Fine-Tuning:

- Refine alerting rules and thresholds based on actual usage patterns.

By implementing these steps, you can proactively monitor and receive alerts for abnormal or critical
resource usage, helping you manage your cloud infrastructure more effectively.
Ex.4:

Certainly! Here's a general guide for setting up billing alerts for your Cloud Organization, using
AWS as an example:

AWS Billing Alerts:

Aim:

Objective:

Implement billing alerts to monitor and manage costs within the AWS Cloud Organization.

Producer:

-Team Members: Billing administrators, Finance team, Cloud administrators.

Program:

1. Access AWS Billing Dashboard:

- Sign in to the AWS Management Console.

- Navigate to the Billing & Cost Management Dashboard.

2. Set up Budgets:

- Choose "Budgets" from the left-hand menu.

- Create a new budget specifying the cost or usage amount, time period, and alert thresholds.

3. Configure Notifications:

- Define notification settings, including email addresses for alert recipients.

- Choose the severity level for notifications.

4. Activate Budget:

- Review and activate the budget to start monitoring costs.

- Configured Billing Budgets: Budgets set up to monitor specific cost or usage patterns.

Notification Channels:Configured to receive alerts through email or other preferred methods.

Result:

-Proactive Cost Monitoring: The system will trigger alerts when costs exceed defined thresholds.

-Timely Management Actions: Enables the finance team and administrators to take timely actions to
control and optimize costs.

This process ensures that your Cloud Organization can proactively manage and monitor costs, helping
prevent unexpected expenses and promoting financial transparency. Keep in mind that the exact steps
may vary slightly based on the cloud provider and their specific services.

Ex.5:

Comparing the cost of hosting a simple web application across AWS, Azure, and GCP involves
considering various factors. Let's outline a basic comparison, but keep in mind that costs can vary
based on specific requirements and usage patterns.

Criteria for Comparison:

1. Compute Costs (VM Instances):

- AWS EC2 (Amazon Elastic Compute Cloud)

- Azure VMs

- GCP Compute Engine

2. Storage Costs:

- AWS S3 (Simple Storage Service)

- Azure Blob Storage

- GCP Cloud Storage

- AWS RDS (Relational Database Service)

- Azure SQL Database

- GCP Cloud SQL

4. Content Delivery Network (CDN) Costs:

- AWS CloudFront

- Azure CDN

- GCP Cloud CDN

5. Data Transfer Costs:

- Costs associated with data transfer within and outside the cloud provider's network.

6. Monitoring and Logging Costs:

- AWS CloudWatch and AWS CloudTrail

- Azure Monitor and Azure Log Analytics

- GCP Stackdriver

Considerations:

1. Usage Patterns:

- Evaluate the expected usage patterns to estimate resource consumption.

2. Geographical Location:

- Consider the geographical distribution of your users and the availability of data centers in relevant
regions.

3. Service Level Agreements (SLAs):

4. Support and Documentation:

- Assess the quality of support and available documentation.

5. Additional Services:

- Explore additional services provided by each cloud provider that may benefit your application.

Suggestion:

-AWS: Often considered robust with a wide range of services, suitable for various application sizes and
complexities.

- Azure:Known for its integration with Microsoft technologies, suitable for businesses heavily invested in
the Microsoft ecosystem.

- GCP:Recognized for its simplicity and strengths in data analytics and machine learning.

Final Consideration:

Choose the cloud provider that aligns best with your application's requirements, your team's expertise,
and the overall goals of your project. Additionally, conduct a detailed cost analysis based on your specific
usage patterns to make an informed decision.