4 ms·

I don't think I've ever handled so much data I'd need to increase data throughput. How much are we talking? Like petabytes? (Do you just stroll in with on a hu

by vladde 2y ago

I don't think I've ever handled so much data I'd need to increase data throughput. How much are we talking? Like petabytes? (Do you just stroll in with on a huge disk array?)

bombcar 2y ago
I don't think it's really so much about throughput as it is about avoiding any ingress chargers at all.
- IanCal 2y ago
  Does aws charge ingress? I've got a good connection for the UK but still about a 100 meg upload. I have external drives that are 4TB, so if everything goes perfectly that could take about two full days to upload.
- kondro 2y ago
  AWS doesn't charge for ingress.
  - canucker2016 2y ago
    FTA: "There will be no per GB charge for the data transfer if you upload data into AWS Regions in the same continent of your location." N.B. I'm not contradicting the parent, but reframing the concept - it seems that the Data Transfer Terminal is ALREADY in AWS so ingress isn't a thing since your data is ALREADY in AWS as soon as you connect the optic fiber cable to whatever storage you've brought onsite. But since you're only renting the connection, your data can't stay forever in AWS unless you copy to S3 or somewhere else in AWS.
unsnap_biceps 2y ago
They mention it as a way to take your snowball and upload it and walk out and continue using it without shipping it back and forth. Those look to go into the 210 TB range of raw storage. In the past, at some companies I was at, I could see using something like this once a quarter to upload full quarterly backups, depending on the price per hour.
Joe8Bit 2y ago
In a previous role we used their (first party) physical transfer appliances to upload ~600PB of video into S3. It was a complex logistical exercise to take it from the physical SANs, but the AWS specialists we worked with were great and it went without a hitch.
KaiserPro 2y ago
I think it depends on your network connection. We used a snowball a couple of times to either move data from S3 to or it. In some cases its because we didn't have enough local storage to shuffle the data, or because we only had a 100 meg net link and a couple of TBs to move.

by vladde 2y ago

I don't think I've ever handled so much data I'd need to increase data throughput. How much are we talking? Like petabytes? (Do you just stroll in with on a huge disk array?)

bombcar 2y ago

I don't think it's really so much about throughput as it is about avoiding any ingress chargers at all.

IanCal 2y ago
Does aws charge ingress? I've got a good connection for the UK but still about a 100 meg upload. I have external drives that are 4TB, so if everything goes perfectly that could take about two full days to upload.
kondro 2y ago
AWS doesn't charge for ingress.
- canucker2016 2y ago
  FTA: "There will be no per GB charge for the data transfer if you upload data into AWS Regions in the same continent of your location." N.B. I'm not contradicting the parent, but reframing the concept - it seems that the Data Transfer Terminal is ALREADY in AWS so ingress isn't a thing since your data is ALREADY in AWS as soon as you connect the optic fiber cable to whatever storage you've brought onsite. But since you're only renting the connection, your data can't stay forever in AWS unless you copy to S3 or somewhere else in AWS.

unsnap_biceps 2y ago

They mention it as a way to take your snowball and upload it and walk out and continue using it without shipping it back and forth. Those look to go into the 210 TB range of raw storage. In the past, at some companies I was at, I could see using something like this once a quarter to upload full quarterly backups, depending on the price per hour.

Joe8Bit 2y ago

In a previous role we used their (first party) physical transfer appliances to upload ~600PB of video into S3. It was a complex logistical exercise to take it from the physical SANs, but the AWS specialists we worked with were great and it went without a hitch.

KaiserPro 2y ago

I think it depends on your network connection. We used a snowball a couple of times to either move data from S3 to or it. In some cases its because we didn't have enough local storage to shuffle the data, or because we only had a 100 meg net link and a couple of TBs to move.