Skip to content

AWS snow family

A. snowball : Data Migration

A.1 Snowball Edge (offline)

  • Use cases
  • large data cloud migrations,
  • DC decommission,

  • disaster recovery

  • Snowball devices (offline portable devices), max:

  • Snowball Edge Storage Optimized : 80 TB | 80 GB RAM | 40 cpu
  • Snowball Edge Compute Optimized : 42 TB | 416 GB RAM | 104 cpu
    • an optional GPU for use cases such as advanced machine learning and full-motion video analysis.
    • These devices may also be rack mounted and clustered together to build larger, temporary installations 🎯
    • can run lambda@edge 👈
  • post device
  • send/upload to/from:
    • block volume / EBS
    • object storage / S3 / but not glacier storage class 👈
    • img.png
  • next, transfer over the stable directconnect network to destination acct's s3 / ebs

img.png

A.2 Snowball Cone (offline + online)

  • Small, portable, light (2 kg) devices
  • type:
  • Snowcone – 8 TB HDD | 4 GB RAM, 2cpu
  • Snowcone SSD – 14 TB SSD | 4 GB RAM, 2cpu
  • send option
  • post device (offline)
  • AWS DataSync (online)
    • to send/upload data to/from:
    • AWS EBS only
    • not s3 ❌ 👈
    • AWS DataSync agent is pre-installed
    • more

A.3 Snowball mobile (offline)

  • 100 PB + 100 PB + ... === upto 1 exabyte (1 Million TB)
  • driven back to an AWS Region where the data is loaded into S3 👈
  • does not offer a storage Clustering option 👈 
      - 1024 TB = 1 PB 
  - 1024 PB = 1 exabyte 
  - so it `1000,000 TB` or 1 Million TB
  • truck with
  • GPS
  • 24/7 video surveillance

summary

img_1.png

B. SNOW : Edge computing

  • edge : location which can produce data, but limited/no internet connectivity, so cannot compute.
  • img_2.png
  • same device as above.
  • run ec2 + lambda
  • long term deployment + 1 / 3 year saving
  • interact with aws-cli or AWS OpsHub(ui)