AWS Data Services
The course is part of this learning path
To be prepared for the AWS Certified Cloud Practitioner Exam, this course will enable you to demonstrate Amazon Simple Storage Service (S3), Amazon Glacier, Amazon Elastic Block Store (EBS) and Amazon CloudFront storage solutions, and help you identify when to apply AWS solutions to common business scenarios.
This course covers a range of different services, including:
- Amazon Simple Storage Service (S3)
- Amazon Elastic Block Storage (EBS)
- Amazon Glacier
- Amazon RDS
- Amazon DynamoDB, ElastiCache, and Redshift
- Amazon CloudFront
- AWS Import/Export Disk
- AWS Import/Export Snowball
- AWS Storage Gateway
By the end of this course, you should be able to:
- Describe the basic functions that each storage service performs within a cloud solution
- Recognize basic components and features of each storage service
- Identify which storage service would be most appropriate to a general use case
- Understand how each service utilizes the benefits of cloud computing, such as scalability or elasticity
This course is designed for:
- Anyone preparing for the AWS Certified Cloud Practitioner
- Managers, sales professionals, and other non-technical roles
Before taking this course, you should have a general understanding of basic cloud computing concepts.
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
Hello and welcome to this lecture focusing on the AWS Snowball service. Essentially this service is used to securely transfer large amounts of data and I'm talking out of petabyte scale here, in and out of AWS. Either from your on-premise data center to Amazon S3 or from Amazon S3 back to your data center using a physical appliance, known as a snowball.
The snowball appliance comes as either a 50 terabyte or 80 terabyte storage device, depending on your region. Currently the 50 terabyte version is only available within the US regions. The appliance is dust, water, and tamper resistant and can even withstand an eight and a half G jolt from within its own external shipping container and so it's been built to code with a lot of stress conditions to ensure the durability of your data. The snowball appliance has been designed to allow for high-speed data transfer thanks to a range of interfaces allowing you to select the most appropriate connection for your needs. Onboard the snowball appliance, the following I/O 10 gigabit interfaces are available, RJ45 using CAT6, SFP Copper, and SFP Optical.
By default, all data transferred to a snowball appliance is automatically encrypted using 256-bit encryption keys generated from KMS, the Key Management Service. Whilst on the topic of security, it also features end to end tracking using an E-Ink shipping label. This ensures that when the device leaves your premises, it is sent to the right AWS facility. The appliance can also be tracked using the AWS Simple Notification Service with text messages or via the AWS Management Console. From a compliance perspective, AWS Snowball is also HIPAA compliant allowing you to transfer protected health information in and out of S3. When the transfer of data is complete by the inter S3 or into a customer's data center and the appliance is sent back to AWS, it is then the responsibility of AWS to ensure that data held in the snowball appliance is deleted and removed. To control this process AWS conforms to standards and guidelines set by NIST, the National Institute of Standard and Technology, to ensure this is performed and controlled and that all traces of data are removed from the media.
When sending or retrieving data, snowball appliances can be aggregated together. For example, if you needed to retrieve 400 terabytes of data from S3 then your data will be sent by five 80 terabyte snowball appliances. So, from a disaster recovery perspective when might you need to use AWS Snowball? Well it all depends on how much data you need to get back from S3 to your own corporate data center and how quickly you can do that. On the other hand, how much data you need to get into S3. This'll depend on the connection you have to AWS from your data center. You may have direct-connect connections, a VPN, or just an internet connection. And if you need to restore multiple petabytes of data, this could take weeks or even months to complete. As a general rule, if your data retrieval will take longer than a week using your existing connection method, then you should consider using AWS Snowball. Your global location will effect specific shipping times and so more information on this can be found using the link on the screen.
If you did decide to use AWS Snowball to retrieve your data in the event of a disaster, the process to use AWS Snowball is a fairly simple process. At a high level this is how it looks. Firstly, you need to create an export job from within the AWS Management Console. Within this job you can dictate shipping details, the S3 bucket, and the data to exported security mechanisms such as the KMS key for data encryption and also notifications. You will then receive delivery of your snowball appliance. You can now connect the appliance to your local corporate network. Firstly, use the ports to connect the appliance to your network whilst it's powered off. Next power on the device and the E Ink display will let you know that it's ready. You can then configure the network settings of the device, such as the IP address, to enable communications. From here you are now ready to start transferring the data. To do this you must first gain specific access credential via a manifest file through the management console, which has to be downloaded. You must then install the snowball Client software and you can now begin transferring data using the client software once authenticated with the manifest file. When the data transfer is complete, you can disconnect the snowball appliance. The appliance must then be returned to AWS using specified shipping carriers. It's important to note that all snowball appliances are the property of AWS and the E Ink label will display the return address.
Much like many other AWS pricing for storage, any data transferred into AWS does not incur a data transfer charge. However, you are charged for the normal Amazon S3 data charges, as discussed in a previous lecture. For each data transfer job, there is a charge in additional to shipping costs associated to the job. As I mentioned previously, there are two sizes of snowball. For the 50 terabyte snowball, there is a $200 charge and for the 80 terabyte, it's $250 unless it's in the Singapore region which will then be $320. You are allowed the snowball for 10 days in total. Any delays requiring additional days incur further charges between $15 to $20, depending on the region. The data transfer charges out of Amazon S3 to different regions is priced as follows. And the shipping will vary depending on your chosen carrier. For further information on this, please visit the following link.
About the Author
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.