Backup of EBS volumes
We can backup the data on our Amazon EBS volumes,regardless of volume type,by taking point- in-time snapshots.
Snapshots are incremental backups,which means that only the blocks on the device that have changed since your most recent snapshot are saved.
Data for the snapshot is stored using Amazon S3 technology
While snapshots are stored using Amazon S3 technology,they are stored in AWS-controlled storage and not in your account’s Amazon S3 buckets.
Snapshots are constrained to the region in which they are created,meaning you can use them to create new volumes only in the same region.
If you need to restore a snapshot in a different region,you can copy a snapshot to another region.
Snapshots can also be used to increase the size of an Amazon EBS volume
To increase the size of an Amazon EBS volume,take a snapshot of the volume,then create a new volume of the desired size from the snapshot.Replace the original volume with the new volume.
To create a snapshot of volumes,select the particular volume from theVolume Management dashboard.Click on the Actions tab and select the Create Snapshot option.
Give a Name and Description for the Snapshot.
- Snapshot of an Encrypted root volume is going to be an encrypted one.
- we can share the snapshots,but the snapshot must be an un encrypted.
We can go to Snapshot dashboard to verify the snapshot creation.
The above are the options available for snapshot.
Delete: we can delete the selected snapshot with this option.
Create Volume:We can create a new volume from this snapshot,while creating the new snapshot, we can change the volume type or increase the size if we want.
Create Image: We can create an AMI from this snapshot.
Copy: We can copy the snapshot from one region to another region.
Modify Permissions:We can share the snapshots with specific AWS account user or made available to public,but this option will not enable if our snapshot is an encrypted.
Creating an AMI
An Amazon Machine Image(AMI) provides the information required to launch a virtual server in the cloud.You specify an AMI when you launch an instance,and you can launch as many instances from the AMI as you need.You can also launch instances from as many different AMIs as you need.
A template for the root volume for the instance
Launch permissions that control which AWS accounts can use the AMI to launch instances.
To create an AMI,Select the root volume’s Snapshot,then select Create Image option
Name: Provide a suitable and meaning full name for your AMI.
Description: Provide a suitable description for your new AMI.
Architecture: We can either choose between i 386 (32 bit) or x 86_64 (64 bit).
Root device name: Enter a suitable name for your root device volume.
Virtualization type:We can choose whether the instances launched from this particular AMI will support Para virtualization(PV) or Hardware Virtual Machine(HVM)virtualization.
Xen is an hyper visor that runs on metal (the pc / server) and then hosts virtual machines called domains.
PV domain is a para virtualized domain,that means the operating system has been modified to run under Xen,and there’s no need to actually emulate hardware.This should be the most efficient way to go,performance wise.
RAM disk ID,Kernel ID:We can select and provide your AMI with its own RAM disk ID(ARI)and Kernel ID(AKI);however,in this case I have opted to keep the default ones.
Block Device Mappings:We can use this dialog to it here expand root volume’s size or add additional volumes to it.We can change the Volume Type from General Purpose(SSD)to Provisioned IOPS(SSD)or Magnetic as per our AMI’s requirements.
Click on Create to complete the AMI creation process.The new AMI will take a few minutes to spin up.
We can select the AMI and choose Launch option to launch a new instance.We will get the instance launch wizard.
AMI are regional,if required we can copy AMI to another region with Copy option.
We can share the AMI to any other AWS account user so we can make it public.
Every AMI will associate with a Snapshot
AMI are registered with the AWS accounts,if you no longer required any AMI,you can select De register option under Actions.
We can not delete the Snapshot if it is associated with an AMI
More Information :https://www.fgrade.com/aws/