What Is IAAS
Infrastructure as a service (IaaS) is an instant computing infrastructure, provisioned and managed over the Internet. Quickly scale up and down with demand and pay only for what you use.
What is EC2?
Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides secure, resizable compute capacity in the cloud. It is designed to make web-scale cloud computing easier for developers. Amazon EC2’s simple web service interface allows you to obtain and configure capacity with minimal friction.
What is VPC?
Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can use both IPv4 and IPv6 in your VPC for secure and easy access to resources and applications.
What is Role?
An IAM role is an IAM entity that defines a set of permissions for making AWS service requests. IAM roles are not associated with a specific user or group. Instead, trusted entities assume roles, such as IAM users, applications, or AWS services such as EC2.
What is EBS & Types of EBS?
Amazon Elastic Block Store (Amazon EBS) provides persistent block storage volumes for use with Amazon EC2 instances in the AWS Cloud. Each Amazon EBS volume is automatically replicated within its Availability Zone to protect you from component failure, offering high availability and durability. Amazon EBS volumes offer the consistent and low-latency performance needed to run your workloads. With Amazon EBS, you can scale your usage up or down within minutes – all while paying a low price for only what you provision.
The following table describes the use cases and performance characteristics for each volume type:
|Solid-State Drives (SSD)||Hard disk Drives (HDD)|
|Volume Type||General Purpose SSD (||Provisioned IOPS SSD (||Throughput Optimized HDD (||Cold HDD (|
|Description||General purpose SSD volume that balances price and performance for a wide variety of workloads||Highest-performance SSD volume for mission-critical low-latency or high-throughput workloads||Low cost HDD volume designed for frequently accessed, throughput-intensive workloads||Lowest cost HDD volume designed for less frequently accessed workloads|
|Volume Size||1 GiB – 16 TiB||4 GiB – 16 TiB||500 GiB – 16 TiB||500 GiB – 16 TiB|
|Max. Throughput/Volume||160 MiB/s||500 MiB/s†||500 MiB/s||250 MiB/s|
|Max. Throughput/Instance††||1,750 MiB/s||1,750 MiB/s||1,750 MiB/s||1,750 MiB/s|
|Dominant Performance Attribute||IOPS||IOPS||MiB/s||MiB/s|
Difference between T2 & M4 EC2 instances
Command to copy S3 object on EC2 instance?
aws s3 sync s3://<bucket name> /home/ec2-user
What is Peering?
Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services (AWS) resources into a virtual network that you’ve defined. A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IPv4 addresses or IPv6 addresses.
Difference between AMI and Snapshot?
An Amazon Machine Image (AMI) is a special type of virtual appliance that is used to create a virtual machine within the Amazon Elastic Compute Cloud (“EC2”). It serves as the basic unit of deployment for services delivered using EC2.
When a snapshot is created from a volume with an AWS Marketplace product code, the product code is propagated to the snapshot. You can take a snapshot of an attached volume that is in use. However, snapshots only capture data that has been written to your Amazon EBS volume at the time the snapshot command is issued.
What are Route table Entries In VPC?
A route table contains a set of rules, called routes, that are used to determine where network traffic is directed.
Each subnet in your VPC must be associated with a route table; the table controls the routing for the subnet. A subnet can only be associated with one route table at a time, but you can associate multiple subnets with the same route table.
So the entry in route table defines how the traffic will follow
Below are some exam entry
Provisional IOPS max. capacity?
How to download a file from AWS S3 with version in Command line?
To list out a particular file version use below command and you will get ObjectVersionId
aws s3api list-object-versions --bucket bucketname --prefix folder/test/default.json --output json
aws s3api get-object --bucket bucketname --key folder/test/default.json D:/verions/default.json --version-id Cu9ksraX_OOpbAtobdlYuNPCoJFY4N3S
How To Connect To AWS RDS?
Difference Between Elastic IP Address And Public IP Address?
An Elastic IP is essentially tied to your AWS account in that AZ. You can freely associate it with any AWS instance. The public IP you get when an instance is created (and you opt to give it a public IP) is ephemeral – if you stop that instance, when you start it up you’ll get another random public IP. It might be the same one you got before, but that would just be coincidence. Elastic IP is “permanent” in the sense that you own it and you associate it to a specific AWS instance ID.
Pricing for elastic IP address?
You can have one Elastic IP (EIP) address associated with a running instance at no charge. If you associate additional EIPs with that instance, you will be charged for each additional EIP associated with that instance per hour on a pro rata basis. Additional EIPs are only available in Amazon VPC.
Types of ELB & their Functioning
- Application Load Balancer: An Application Load Balancer makes routing decisions at the application layer (HTTP/HTTPS), supports path-based routing, and can route requests to one or more ports on each container instance in your cluster. Application Load Balancers support dynamic host port mapping. For example, if your task’s container definition specifies port 80 for an NGINX container port, and port 0 for the host port, then the host port is dynamically chosen from the ephemeral port range of the container instance (such as 32768 to 61000 on the latest Amazon ECS-optimized AMI). When the task is launched, the NGINX container is registered with the Application Load Balancer as an instance ID and port combination, and traffic is distributed to the instance ID and port corresponding to that container. This dynamic mapping allows you to have multiple tasks from a single service on the same container instance.
- Network Load Balancer: A Network Load Balancer makes routing decisions at the transport layer (TCP/SSL). It can handle millions of requests per second. After the load balancer receives a connection, it selects a target from the target group for the default rule using a flow hash routing algorithm. It attempts to open a TCP connection to the selected target on the port specified in the listener configuration. It forwards the request without modifying the headers. Network Load Balancers support dynamic host port mapping. For example, if your task’s container definition specifies port 80 for an NGINX container port, and port 0 for the host port, then the host port is dynamically chosen from the ephemeral port range of the container instance (such as 32768 to 61000 on the latest Amazon ECS-optimized AMI). When the task is launched, the NGINX container is registered with the Network Load Balancer as an instance ID and port combination, and traffic is distributed to the instance ID and port corresponding to that container. This dynamic mapping allows you to have multiple tasks from a single service on the same container instance.
- Classic Load Balancer: A Classic Load Balancer makes routing decisions at either the transport layer (TCP/SSL) or the application layer (HTTP/HTTPS). Classic Load Balancers currently require a fixed relationship between the load balancer port and the container instance port. For example, it is possible to map the load balancer port 80 to the container instance port 3030 and the load balancer port 4040 to the container instance port 4040. However, it is not possible to map the load balancer port 80 to port 3030 on one container instance and port 4040 on another container instance. This static mapping requires that your cluster has at least as many container instances as the desired count of a single service that uses a Classic Load Balancer.
We are adding more question, please keep visiting for more