EC2 Access:-
| EC2 Access | → To access instances, you need a key I and Key pair Name. → You Can download the Private key Only Once. → The Public Key is Saved by AWS to match it to the Key pair name, and the Private key is when you try to login to the EC2 instances. → Without Key pair you Cannot access instances via RDP or SSH. → There are 20 EC2 instances Soft Limit per region, you Can Submit a Request to AWS to increase it. |
Ec2 Status Check:-
| Ec2 Status Check
|
→ By default AWS EC2 Service performs automated Status checks every minute. → This is done on every running EC2 instance to identify any Hw or software issue. → Status check is built into the AWS EC2 instance. → They Cannot be Configured, deleted, or disabled. → EC2 Services Can Send its metric Data to AWS Cloudwatch every 5 minutes (enabled by default). → Enabled detailed monitoring is Chargeable and Sends matric every 1 minute. → You are not charged for EC2 instances, if they are stopped, however, attached EBS Volumes incur charges. |
| When you stop an EBS Backed EC2 Instance | → Instances perform a Shutdown. → state changes from Running Stopping. → EBS Volumes remain attached to the instance. → Any data cached in RAM or instances store volume is gone. → Instances retain its private IPv4 or any IPv6 address. → Instances releases its public LPv4 address back to Aws Pool. → Instances Retain their Elastic IP address. |
| EC2 Termination | → when you terminate a Running instance the instance stakes change as follows. Running → shutting down → Terminated. → During the shutting down and Terminated states, you do not incur Charges. → By default EBS Root Devices Volumes have been deleted Automatically when the EC2 instances are terminated. → Any additional (non-boot/boot) Vokimes attached to the instances by default, persist after the instance is terminated. → You Can Modify both behaviors by Modifying the ‘Delete on Termination’ attribute of any EBS Volumes during instances launch or while Running. → Enable EC2 Termination Protection against accidental Termination. |
EC2 Metadeta:-
| EC2 Metadeta
|
This is instance data that you can use to configure or manage the instance. eg:- IPv4 addresses, [Pu6 addresses, DNS hostname, AMI-id, Instance ID, Instance Type, local hostname, public keys, Security groups.→ Metadata Can be Only viewed from within the instance itself ie you have to log in to the instance. → Metadata is not protected by encryption, anyone that has access to the instance.→ Can view this data To View instance Metadata, GET http://169254169254/latest/Metadata |
Instances User data:-
| Instances User data | → data Supplied by the User at instance launch in the form of a Script to be executed during the instance boot. → User data is limited to 16 KB. → You Can Change User data, by Stopping EC2 first. → User data is not encrypted. |
Elastic Block Storage (NAS)
| Elastic Block Storage (NAS) | → The storage is called (EBS block volume) and the instance is called EBS Backed Instance. → Most Common Replicate with A-Z. → EBS Volumes attached at launch are deleted when the instance terminates.→ EBS Volumes attached to a running instance are not deleted when the instance is terminated but are detached with data interact. |
Instance Storage (CDAS)
| Instance Storage (CDAS) | → Physically attach to the host Server. → Data not lost when os is Rebooted.Data lost when: → Underlying drive fails. → Instance is stopped or terminated. → You Can’t detach or attach to another. Do not Rely on for Valuable long-term data. |