AWS in the Cloud computing

Day 2

Amazon Web Services (AWS) has a rich history that has evolved over the years. Here's a brief overview of the key milestones in the history of AWS:

History of AWS

2002-2003: Inception and Early Development
- The idea for AWS began in 2002 when Amazon's internal infrastructure team started working on a platform to provide services for their e-commerce business.
- Development of what would later become AWS started in 2003.
2004: Launch of SQS (Simple Queue Service)
- Amazon SQS, a distributed message queuing service, was the first service to be launched as part of AWS in 2004.
2006: Launch of Amazon S3 and EC2
- Amazon S3 (Simple Storage Service) and Amazon EC2 (Elastic Compute Cloud) were officially launched, marking the beginning of AWS as a comprehensive cloud services provider.
- These services allowed users to store and retrieve data in the cloud (S3) and run virtual servers in the cloud (EC2).
2007: Expansion of Service Offerings
- AWS continued to expand its service offerings with the launch of services like Amazon SimpleDB and Amazon Simple Queue Service (SQS).
2009: Introduction of AWS Management Console
- AWS introduced the AWS Management Console, a web-based interface for managing AWS services.
2010: Elastic Beanstalk and Virtual Private Cloud (VPC)
- AWS Elastic Beanstalk, a platform as a service (PaaS) offering, was launched to simplify the deployment and management of applications.
- Amazon VPC allowed users to provision a logically isolated section of the AWS Cloud where they could launch resources in a virtual network.
2011: Growth and Global Expansion
- AWS continued to expand globally with the opening of data centers in various regions around the world.
2013: AWS Marketplace and Redshift
- AWS Marketplace was introduced, allowing third-party vendors to sell their software to AWS users.
- Amazon Redshift, a fully managed data warehouse service, was launched.
2015: Lambda and Aurora
- AWS Lambda, a serverless computing service, was introduced.
- Amazon Aurora, a MySQL-compatible relational database engine, was launched.
2017: AWS Snowball Edge and DeepLens
- AWS Snowball Edge, a data transfer device with on-board storage and compute capabilities, was introduced.
- AWS DeepLens, a deep learning-enabled video camera, was launched.
2019: Ground Station and Wavelength
- AWS Ground Station, a fully managed service for controlling satellite communications, was introduced.
- AWS Wavelength brought AWS services to the edge of the 5G network.
2020-2021: Continued Innovation and Response to COVID-19
- AWS continued to innovate with the launch of services like Amazon Kendra (a machine learning-powered search service) and AWS Proton (a fully managed deployment service for container and serverless applications).
- During the COVID-19 pandemic, AWS played a crucial role in supporting organizations with cloud services for remote work, education, and healthcare.
2022 and Beyond: Ongoing Innovation
- AWS continues to evolve and innovate, expanding its portfolio of services and global infrastructure to meet the growing demands of businesses and developers.

AWS Play significant role in shaping the cloud computing industry

AWS has played a significant role in shaping the cloud computing industry and has become a key player in providing a wide range of scalable and reliable cloud services.

As of my last knowledge update in January 2022, I don't have the most recent and specific numbers for AWS cloud in terms of users, revenue, or other metrics. However, I can provide some general facts and figures based on information available up to that point:

Market Dominance:
- AWS has been a dominant force in the cloud computing market, holding a substantial share. It is considered one of the largest and most widely used cloud platforms globally.
Services Offered:
- AWS offers a vast array of services, covering computing power, storage, databases, machine learning, analytics, Internet of Things (IoT), security, and more. The platform continues to expand its service offerings.
Global Infrastructure:
- AWS has a global network of data centers, referred to as Availability Zones, located in multiple geographic regions. Each region consists of multiple Availability Zones for redundancy and fault tolerance.
Customers:
- AWS serves a diverse customer base, including startups, enterprises, government organizations, and non-profits. Many well-known companies and organizations use AWS for their cloud computing needs.
Revenue:
- AWS has been a significant revenue generator for Amazon. It has contributed significantly to the overall financial performance of the company.
Elasticity and Scalability:
- One of the key features of AWS is its elasticity and scalability. Users can easily scale resources up or down based on demand, paying only for what they use.
Certifications and Training:
- AWS offers a variety of certifications for individuals to demonstrate their expertise in using AWS services. Training and certification programs are available for different roles and skill levels.
Sustainability Initiatives:
- AWS has been working on sustainability initiatives, including commitments to using renewable energy. The company has set goals for achieving a certain percentage of renewable energy usage in its data centers.
Partnerships and Ecosystem:
- AWS has a robust partner ecosystem, including independent software vendors (ISVs), system integrators, and technology partners. This ecosystem enhances the capabilities and offerings available to AWS users.

For the most up-to-date and specific information regarding AWS's current statistics, financials, and other metrics, it's recommended to refer to the latest reports and announcements from Amazon Web Services or reputable financial news sources.

AWS USE CASE

Amazon Web Services (AWS) is a versatile cloud platform that caters to a wide range of use cases across various industries. Here are some common AWS use cases:

Web Hosting:
- AWS provides scalable and cost-effective solutions for hosting websites and web applications. Amazon EC2 instances and Amazon S3 for storage are commonly used for web hosting.
Data Storage and Backup:
- Amazon S3 is a popular choice for object storage, providing scalable and durable storage for data backup, archival, and data lakes. Amazon Glacier is often used for low-cost, long-term archival storage.
Compute Power and Virtual Servers:
- Amazon EC2 offers resizable compute capacity in the cloud. It is widely used for running virtual servers and applications, and users can choose instances with varying compute power and memory.
Database Management:
- AWS provides managed database services such as Amazon RDS (Relational Database Service), Amazon DynamoDB (NoSQL database), and Amazon Redshift (data warehousing). These services simplify database management tasks.
Content Delivery:
- Amazon CloudFront is a content delivery network (CDN) that securely delivers data, videos, applications, and APIs to customers globally with low latency and high transfer speeds.
Machine Learning and AI:
- AWS offers a suite of machine learning services, including Amazon SageMaker for building, training, and deploying machine learning models. AI services like Amazon Rekognition and Amazon Polly are used for image and text analysis, as well as text-to-speech capabilities.
Internet of Things (IoT):
- AWS IoT services enable the connection, management, and analysis of IoT devices and their data. It includes services like AWS IoT Core, which securely connects devices to the cloud.
Analytics and Big Data:
- Amazon EMR (Elastic MapReduce) is used for processing large datasets using popular frameworks such as Apache Spark and Apache Hadoop. Amazon Athena and Amazon Redshift are used for querying and analyzing big data.
DevOps and Continuous Integration/Continuous Deployment (CI/CD):
- AWS provides services like AWS CodePipeline, AWS CodeBuild, and AWS CodeDeploy to facilitate the automation of software release processes and enable continuous integration and deployment.
Security and Identity Management:
- AWS Identity and Access Management (IAM) allows users to control access to AWS services securely. AWS Key Management Service (KMS) is used for managing encryption keys, ensuring data security.
Virtual Private Cloud (VPC):
- AWS VPC enables users to launch Amazon Web Services resources in a logically isolated section of the AWS Cloud. It provides control over the virtual networking environment, including IP address ranges, subnets, and route tables.
Healthcare and Life Sciences:
- AWS is used in healthcare for storing and analyzing patient data, running applications for telehealth, and facilitating research in life sciences.

These are just a few examples, and the versatility of AWS allows it to address a wide array of use cases across industries, including finance, education, gaming, media, and more. Organizations can leverage AWS to build scalable, flexible, and cost-effective solutions tailored to their specific needs.

Global infrastructure

As of my last knowledge update in January 2022, Amazon Web Services (AWS) has a global infrastructure that consists of multiple geographic regions and availability zones. Keep in mind that AWS may have expanded its infrastructure since then. Here's a general overview of AWS global infrastructure:

Regions:

Geographic Regions: AWS divides the world into geographic regions, such as North America, Europe, Asia Pacific, etc.
Availability Zones: Each region is composed of multiple Availability Zones (AZs), which are essentially data centers with redundant power, networking, and cooling. AZs are isolated from each other to provide fault tolerance.

Global Reach:

AWS has a presence in numerous countries and continues to expand its global footprint to meet the growing demand for cloud services.

Notable Regions (as of 2022):

North America:
- US East (N. Virginia)
- US East (Ohio)
- US West (N. California)
- US West (Oregon)
- Canada (Central)
Europe:
- Europe (Ireland)
- Europe (Frankfurt)
- Europe (London)
- Europe (Paris)
- Europe (Stockholm)
Asia Pacific:
- Asia Pacific (Mumbai)
- Asia Pacific (Seoul)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
South America:
- South America (Sao Paulo)
Middle East:
- Middle East (Bahrain)
Africa:
- Africa (Cape Town)

Specialized Regions:

In addition to standard regions, AWS introduced specialized regions like the AWS GovCloud (US) region, designed to host sensitive workloads for U.S. government agencies and other customers.

Edge Locations:

AWS has a global network of Edge Locations for its content delivery service, Amazon CloudFront. These Edge Locations help deliver content with low latency by caching data closer to end-users.

Global Accelerators:

AWS Global Accelerator is a service that uses static IP addresses (Anycast) to route traffic over the AWS global network to the optimal AWS endpoint based on health, geography, and routing policies.

Wavelength Zones:

Wavelength Zones bring AWS services to the edge of 5G networks, reducing latency for applications that require ultra-low latency.

Local Zones:

AWS Local Zones are extension locations of AWS regions, providing low-latency access to AWS services in metropolitan areas.

It's essential to check the AWS official website or documentation for the most up-to-date and specific information on AWS's global infrastructure, as the company regularly adds new regions and services to meet customer needs.

Availability Zones

Amazon Web Services (AWS) Availability Zones (AZs) are isolated data centers within a geographic region, providing redundancy, fault tolerance, and low-latency connectivity. Each Availability Zone is essentially a separate facility with its own power, cooling, and networking infrastructure. The concept of Availability Zones is crucial for building highly available and resilient applications on the AWS cloud.

Here are key points about AWS Availability Zones:

Definition:
- Availability Zones are distinct locations within a region that are engineered to be isolated from failures in other Availability Zones. They are connected through a high-speed, low-latency network.
Purpose:
- The primary purpose of Availability Zones is to provide fault tolerance. If one Availability Zone experiences a failure, the other Availability Zones in the region should continue to operate.
Redundancy:
- AWS designs its data centers in such a way that failures in one zone do not affect the others. This ensures redundancy and resilience for applications hosted in the cloud.
Regions and Availability Zones:
- AWS regions are composed of multiple Availability Zones. For example, the US East (N. Virginia) region may consist of multiple Availability Zones like us-east-1a, us-east-1b, and so on.
Connected Through Low-Latency Links:
- Availability Zones within a region are connected through fast, private fiber-optic links, enabling low-latency communication between them.
Independent Power and Cooling:
- Each Availability Zone has its own independent power source, cooling systems, and physical security measures.
Multi-AZ Deployments:
- Users can design their applications to run in multiple Availability Zones for enhanced availability. This is often referred to as a Multi-AZ deployment.
High Availability and Disaster Recovery:
- Availability Zones are a fundamental building block for achieving high availability and disaster recovery in the AWS cloud. By distributing resources across multiple zones, applications can continue to operate even if one zone becomes unavailable.
Services Distributed Across Zones:
- Many AWS services automatically distribute resources across multiple Availability Zones to enhance reliability. For example, Amazon RDS (Relational Database Service) allows users to create Multi-AZ database deployments.
Edge Locations vs. Availability Zones:
- Edge Locations, used by Amazon CloudFront, are different from Availability Zones. Edge Locations are part of Amazon CloudFront's content delivery network and are used for caching content close to end-users to reduce latency.
Local Zones and Wavelength:
- AWS has introduced Local Zones and Wavelength Zones to bring AWS services closer to end-users and 5G networks, respectively. These are extensions of existing regions, providing additional options for low-latency applications.

Understanding and leveraging AWS Availability Zones are essential for architects and developers aiming to build resilient and highly available applications in the cloud. It's important to note that AWS continues to expand its global infrastructure, adding new regions and Availability Zones over time.

AWS- A Point of Presence

In the context of Amazon Web Services (AWS), a "Point of Presence" (PoP) typically refers to locations within a network infrastructure where AWS has a presence to enhance the delivery of its services. Points of Presence are part of the broader AWS global network strategy to ensure low-latency, high-performance access to AWS services for end-users.

Key points about AWS Points of Presence:

Edge Locations:
- AWS Edge Locations are often considered Points of Presence. These locations are part of Amazon CloudFront, AWS's content delivery network (CDN). Edge Locations are distributed globally and are strategically located to cache and deliver content (such as images, videos, and other static assets) closer to end-users.
Amazon CloudFront:
- CloudFront uses a network of Edge Locations to cache and serve content to users with low latency. When a user requests content, it is served from the nearest Edge Location, reducing the time it takes for the content to reach the user.
Global Accelerator:
- AWS Global Accelerator is another service that utilizes Points of Presence. It uses static IP addresses (Anycast) to route traffic over the AWS global network to the optimal AWS endpoint based on health, geography, and routing policies.
Direct Connect Locations:
- AWS Direct Connect provides dedicated network connections from on-premises data centers to AWS. Direct Connect Locations, where customers can connect to the AWS network, can also be considered as Points of Presence.
Wavelength Zones and Local Zones:
- AWS Wavelength Zones, designed for low-latency applications that require 5G connectivity, and Local Zones, which are extensions of AWS regions, can be considered as Points of Presence to bring AWS services closer to end-users.
Internet Exchange Points (IXPs):
- AWS may have Points of Presence at Internet Exchange Points to improve the connectivity between its network and other networks on the internet.
Low-Latency Connectivity:
- The presence of Points of Presence in various locations allows AWS to offer low-latency connectivity for services that require fast access, such as content delivery, real-time applications, and more.

Understanding the locations of AWS Points of Presence is crucial for optimizing the performance and reliability of applications hosted on AWS. It allows organizations to leverage AWS services efficiently by reducing latency and ensuring a better user experience for their applications. Keep in mind that AWS's network infrastructure evolves, so it's advisable to check the most recent documentation for the latest information on AWS Points of Presence.

Identity and Access Management (IAM)

In Amazon Web Services (AWS), Identity and Access Management (IAM) is a service that allows you to manage access to AWS resources securely. IAM enables you to create and manage users, groups, and permissions to control who can access various AWS resources and what actions they can perform.

Here's an overview of IAM users and groups:

IAM User:

Definition:
- An IAM user is an entity that represents a person or an application (such as a server or an app) that interacts with AWS services.
Attributes:
- IAM users have a set of security credentials (access key and secret key) that are used to interact with AWS programmatically through APIs, SDKs, or the AWS Command Line Interface (CLI).
- Users can also have a password for accessing the AWS Management Console.
Access Permissions:
- IAM users are granted permissions by attaching policies directly to the user or by adding them to IAM groups. Policies define what actions are allowed or denied for specific AWS resources.
Individual Identity:
- IAM users are typically created for individual people or for specific applications, allowing for more granular control over access.
Examples:
- Examples of IAM users could include individual developers, administrators, or service accounts that need programmatic access to AWS resources.

IAM Group:

Definition:
- An IAM group is a collection of IAM users. You can use groups to specify permissions for multiple users, making it easier to manage access control.
Attributes:
- A group has its own set of policies that are attached to the group. When a user is added to a group, they inherit the permissions granted by the group's policies.
Access Permissions:
- Groups are a way to simplify the management of access policies by applying them to multiple users simultaneously. This is especially useful when users share common access requirements.
Efficient Policy Management:
- Instead of attaching policies to individual users, you can attach policies to groups, making it more efficient to manage permissions for multiple users with similar access needs.
Examples:
- Examples of IAM groups could include groups for different departments, teams, or roles within an organization. For instance, you might have a group for administrators, developers, or marketing personnel.

By using IAM users and groups, you can implement the principle of least privilege, ensuring that each user or group has only the permissions necessary to perform their specific tasks. This helps enhance security and maintain a well-organized access control structure in your AWS environment.

IAM PERMISIONS

IAM (Identity and Access Management) permissions in Amazon Web Services (AWS) define what actions users, groups, and roles are allowed or denied to perform on AWS resources. Permissions are assigned through IAM policies, which are JSON documents that specify the permissions.

Here are key concepts related to IAM permissions:

1. IAM Policies:

An IAM policy is a document that defines permissions. It consists of a set of statements that specify actions, resources, and the effect (Allow or Deny).
Policies can be attached to IAM users, groups, and roles.

2. Actions:

Actions in IAM policies represent the specific operations that can be performed on AWS resources. For example, "s3:ListBucket" is an action that allows listing the objects in an Amazon S3 bucket.

3. Resources:

Resources in IAM policies specify the AWS resources to which the actions apply. Resources can be specific (e.g., an Amazon S3 bucket) or use wildcards (e.g., "*" to represent all resources).

4. Effect:

The "Effect" in IAM policies can be either "Allow" or "Deny." It determines whether the specified actions are allowed or denied.

5. Principals:

IAM policies are attached to IAM principals, which can be IAM users, groups, or roles. The principal is the entity that is granted or denied permissions.

6. Permission Boundaries:

IAM users and roles can have permission boundaries, which are an advanced feature that sets the maximum permissions a user or role can have. This helps control the maximum level of access.

7. Managed Policies:

AWS provides managed policies, which are pre-built policies that cover common use cases. These can be attached to users, groups, or roles.
Examples include AWS managed policies for Amazon S3 read-only access or AWS managed policies for administrator access.

8. Inline Policies:

In addition to managed policies, you can create inline policies directly attached to IAM users, groups, or roles. Inline policies are defined directly within the IAM entity and are part of the entity's configuration.

9. Policy Conditions:

IAM policies can include conditions that specify when the policy's permissions are in effect. For example, a policy might only allow actions if the request comes from a specific IP address or during a specific time period.

10. Policy Versioning:

IAM policies support versioning. When you make changes to a policy, AWS creates a new version, allowing you to roll back to previous versions if needed.

11. Least Privilege Principle:

Following the principle of least privilege, IAM permissions should be granted at the minimum level necessary for users and roles to perform their tasks. This enhances security by reducing the potential impact of accidental or intentional misuse.

Example IAM Policy:

Here is a simplified example of an IAM policy that allows read-only access to an S3 bucket

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::example-bucket/*"
    }
  ]
}

In this example, the policy allows the "s3:GetObject" action on objects within the specified S3 bucket.

IAM policies play a crucial role in securing AWS resources by controlling access based on the principle of least privilege. They are flexible and granular, allowing organizations to tailor access permissions to their specific requirements.

Creating an IAM (Identity and Access Management) user in AWS involves several steps. IAM allows you to manage access to AWS services and resources securely. Here's a step-by-step guide to creating an IAM user:

Open your web browser and navigate to the AWS Management Console.
Sign in with your AWS account credentials.

Step 2: Access IAM Service

Once signed in, locate and select the "Services" dropdown in the top left corner of the console.
In the "Security, Identity, & Compliance" section, select "IAM" to access the IAM dashboard.

Step 3: Navigate to "Users" Section

In the IAM dashboard, select "Users" from the left navigation pane.

Step 4: Click "Add user"

Click the "Add user" button to start creating a new IAM user.

Step 5: Configure User Details

In the "User name" field, enter a unique name for the user.
Choose the type of access:
- Programmatic access: Allows the user to interact with AWS services using the AWS CLI, SDKs, or other development tools.
- AWS Management Console access: Allows the user to sign in to the AWS Management Console.

Step 6: Set Permissions

In the "Set permissions" step:
- Choose "Attach existing policies directly" to attach one or more existing IAM policies to the user.
- OR choose "Add user to group" to add the user to one or more IAM groups that already have policies attached.

Step 7: Tags (Optional)

You can add tags to the user (optional). Tags are key-value pairs that can help you organize and identify users.

Step 8: Review

Review the configured settings for the IAM user. If everything looks correct, click "Create user."

Step 9: Success

You will see a confirmation screen indicating that the user has been successfully created. This screen will display the user's access key ID and secret access key if you chose to create programmatic access.

Additional Steps (If Enabling Console Access):

If you enabled AWS Management Console access, you will have an option to set a password for the user. Choose either "Autogenerated password" or "Custom password."
You can also force the user to reset their password on their first sign-in (recommended for security).

Important Notes:

Access Key ID and Secret Access Key:
- If you created programmatic access, the access key ID and secret access key are provided during the user creation process. Make sure to save these credentials securely.
Console Access:
- If you enabled AWS Management Console access, the user can sign in using the console URL, and you should provide them with the necessary information.

After creating the IAM user, you can fine-tune permissions, add the user to groups, and make additional configurations as needed based on your organization's security and access requirements.

IAM roles in Amazon Web Services

IAM roles in Amazon Web Services (AWS) are entities that define a set of permissions for making AWS service requests. IAM roles are not associated with a specific user or group; instead, they are assumed by AWS resources, such as EC2 instances, Lambda functions, or AWS services, to obtain temporary security credentials for access to AWS resources.

Here are key concepts related to IAM roles:

1. Purpose of IAM Roles:

IAM roles are used to grant permissions to AWS services, applications, or users from other AWS accounts.
They are commonly used for delegation and cross-account access.

2. Assume Role:

When a role is created, it defines who can assume the role and what permissions are granted upon assuming the role.
IAM roles can be assumed programmatically using the AWS CLI, SDKs, or by services like EC2 instances.

3. Temporary Security Credentials:

When a role is assumed, it generates temporary security credentials that are used for making AWS service requests.
These temporary credentials have a limited duration, typically ranging from a few minutes to several hours.

4. Cross-Account Access:

IAM roles enable cross-account access. This means that a user or resource in one AWS account can assume a role in another AWS account.

5. Inline Policies:

IAM roles can have inline policies directly attached to them. These policies define what actions can be performed when someone assumes the role.

6. Managed Policies:

Roles can also be associated with managed policies, which are a set of permissions that can be reused across multiple roles.

7. Trusted Entities:

A role has a trusted entity, which can be an AWS service or an AWS account. It defines who or what is allowed to assume the role.

8. IAM Role Trust Relationship Example:

The trust relationship defines which entities (accounts, users, or services) are allowed to assume the role. Here's a simplified example of a trust relationship JSON:

  jsonCopy code{
    "Effect": "Allow",
    "Principal": {
      "Service": "ec2.amazonaws.com"
    },
    "Action": "sts:AssumeRole"
  }

Steps to Create an IAM Role:

Sign in to the AWS Management Console.
Navigate to IAM:
- Go to the IAM console and select "Roles" from the left navigation pane.
Create a Role:
- Click on the "Create role" button.
Select Type of Trusted Entity:
- Choose the trusted entity type (e.g., AWS service, another AWS account, or SSO identity provider).
Choose a Use Case or Service:
- Depending on the type of trusted entity, select the use case or service that will assume the role.
Permissions:
- Attach policies to the role, either by selecting managed policies or by creating inline policies.
Tags (Optional):
- Add tags to the role for organizational purposes.
Review:
- Review the configuration, provide a name for the role, and click "Create role."
Access Temporary Security Credentials:
- Once the role is created, entities can assume the role to obtain temporary security credentials and access resources based on the defined permissions.

IAM roles are a fundamental aspect of AWS security and access control, particularly in scenarios involving cross-account access and delegation of permissions to AWS resources. They provide a secure and flexible way to manage access within an AWS environment.

AWS GLOBAL SERVICE AND REGION SERVICE

In Amazon Web Services (AWS), there are two primary categories of services based on their deployment scope: global services and regional services.

1. Global Services:

Definition:

Global services in AWS are services that are not tied to a specific AWS region. They are designed to be globally distributed, providing a consistent experience and functionality across the entire AWS infrastructure.

Key Characteristics:

Single Global Endpoint: Global services typically have a single global endpoint, and users can access these services from any AWS region.
Consistent Functionality: The functionality and features of global services remain consistent regardless of the AWS region.
Managed Globally: These services are managed centrally on a global scale by AWS.

Examples of Global Services:

IAM (Identity and Access Management):
- IAM is a global service that manages access to AWS services and resources.
Route 53 (Domain Name System - DNS):
- Route 53 is a scalable and highly available DNS web service with global coverage.
CloudFront (Content Delivery Network - CDN):
- CloudFront is a content delivery network with edge locations worldwide, providing low-latency content delivery.
WAF (Web Application Firewall):
- AWS WAF is a web application firewall service that protects web applications from common web exploits.
AWS Global Accelerator:
- Global Accelerator is a service that uses static IP addresses to route traffic over the AWS global network to optimize availability and performance.

2. Regional Services: