28 June 19
EC2 (Amazon Elastic Compute Cloud (Amazon EC2) enables “compute” in the cloud. Amazon EC2’s simple web service interface allows you to obtain and configure capacity with minimal friction. It provides you with complete control of your computing resources and lets you run on Amazon’s proven computing environment. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to quickly scale capacity, both up and down, as your computing requirements change.
Amazon EC2 currently supports all variety of operating systems i.e.
Amazon EC2 SLA (Service level agreement) is Monthly Uptime Percentage of at least 99.99% for EC2 and EBS within a Region.
Amazon EC2 proving different types of instances like,
The data stored on a local instance store will persist only as long as that instance is alive. However, data that is stored on an Amazon EBS volume will persist independently of the life of the instance. Therefore, amazon recommend that you to use the local instance store for temporary data and, for data requiring a higher level of durability.
AMI stands for Amazon Machine Image. It is a snapshot of the root filesystem. Commodity hardware servers have a bios that points the master boot record of the first block on a disk. A disk image though can sit anywhere physically on a disk, so Linux can boot from an arbitrary location on the EBS storage network.
Build a new AMI by first spinning up and instance from a trusted AMI. Then adding packages and components as required.
Autoscaling is a feature of amazon web service which allows you to configure and automatically provision and spin up new instances without the need for human intervention
Starting July 2018, all newly created EC2 resources will receive longer format IDs. The new format will only apply to newly created resources; your existing resources won’t be affected. Instances and volumes already use this ID format.
The new identifier format will follow the pattern of the current identifier format, but it will be longer. The new format will be , e.g. “vpc-1234123490abcdef0” for VPCs or “subnet-1234512340abcdef0” for subnets.
It typically takes less than 10 minutes from the deployment of the Run Instances call to the point where all requested instances begin their boot sequences. This time depends on a number of factors including: the number of instances you are launching the size of your AMI.