Ec2_ebs_snapshots

New

You can create an EBS Snapshot of an EBS Volume at any time. It does not have to be currently attached to a running server instance.

• Nickname - By default, a name for the new EBS Snapshot will be constructed with the following syntax: VolumeName YYMMDD-HHMM
• Volume - The name of the volume that you're going to take a snapshot of.
• Description - A brief description of the new snapshot. This description is metadata that's specific to RightScale and cannot be viewed outside of the RightScale platform.
• Aws description - A brief description that is tied to the snapshot itself. This description can be viewed outside of the RightScale platform.

Index

An EBS Snapshot represents an EBS volume at a particular point in time. You can create a snapshot regardless of whether or not a volume is attached to an instance. When a snapshot is saved to S3, it receives a timestamp and a unique AWS ID (e.g. snap-9cea0df5). Snapshots consist of a series of data blocks that are incrementally saved to S3. Create clones of volumes from any snapshot. You cannot attach the same volume to multiple instances. Instead, you must first take a snapshot of the volume. Then create a clone of the volume from the snapshot and specify the appropriate availability zone.

Similar to AMIs, you can also share EBS Snapshots with other AWS accounts or make them publicly available. Do not be alarmed if you see snapshots listed that do not belong to your account. Snapshots that were created from your account will be labeled "me" under the Owner column. You will also see several publicly available Snapshots from Amazon. In all other cases, the AWS Account Number of the sharing account will be listed.

To find snapshots that belong to your account, filter by Owner: you

• Create a volume - Create a new volume based on a snapshot.
• Delete - Permanently delete a snapshot. You can also use the select checkboxes to delete multiple or all snapshots.

- -

Show

View general information about the snapshot including its unique AWS ID, the volume from which the snapshot was created, and the time it took to complete the snapshot. You can also provide a description or a tag to help better identify a group of related snapshots. If you launch a snapshot, an exact replica of the volume (that was snapshot) will be created. You can also permanently delete a snapshot from your S3 bucket or add machine tags.

Info tab

The Info tab shows basic information about the EBS Snapshot.

Action buttons

• Launch - Create an EBS Volume from a snapshot.
• Register EBS Image - Create an AWS EC2 Image from an EBS snapshot.
• Delete - Delete the snapshot.
• Add - Input another owner id to share the snapshot with another user.
• Make snapshot public - make the snapshot public for all other users within the account.

Fields

• Description - User-defined description of the snapshot.
• Tag(s) - Private tags that you've added to the snapshot.
• Aws id - The unique identification number of the snapshot.
• Owner - The AWS account number that created the snapshot.
• Ownership - The ownership status of the snapshot. The snapshot will be listed as "imported" unless you created the snapshot.
• Volume - The name of the volume that you're going to take a snapshot of.
• Volume Size - The minimum size of the volume that will be created from the snapshot in GB. When you create a volume from the snapshot you can specify a larger volume.
• Status - You can only use a snapshot to create a volume if its status is completed.
• Started at - The timestamp of when the snapshot started to be created.
• Took - The length in time that it took to finish creating the snapshot.
• Created by - User who created the snapshot.
• Current - The current sharing status of the snapshot.
• Change - Change the sharing settings of the snapshot.

Servers tab

The Servers tab displays a list of all servers that have been configured to use this snapshot to create and attach a volume at boot time.

Action Buttons

• Attach to server on boot time - When you attach a snapshot to a server, a volume of that snapshot will be created and attached to the server instance (at boot time).