[–] 1 point 6 days ago

Yeah, it's insane what it costs. We spend about $20k/month and that's after a big oush to reduce costs.

I'm sure that's tiny compared to many but like I said we're only about 20 employees.

It's pervasive as well, all those SasS products are probably running on AWS or one of the other big ones and so their cloud bill is baked into the prices. You end up paying them a dozen different ways.

  • source
  • parent
  • context
  • [–] 9 points 6 days ago (3 children)

    I work for a really small company (20 people) that uses AWS. We discussed moving off and concluded it would be a multi year effort. I can't even imagine how much work this would involve

  • source
  • [–] 8 points 1 week ago

    Same here. Full time WFH since St Patrick's Day 2020. I've been to the office less than 10 times since. I've not worked a full day there once, if I do go, I travel on company time.

    I used to drive 16,000 miles a year, now it's more like 4,000.

  • source
  • parent
  • context
  • [–] 7 points 2 weeks ago

    Yeah i have to use W11 for work and the brand new Dell XPS, upper mid range, they gave me compared to my 2017 i3 with linux and all this is true.

    About the half the time i boot it and the network just doesn't connect. Wired or WiFi. Have to unplug the dock and reconnect it. DNS will drop for 10s at random.

    There's times my laptop shows it age like i was bulk processing a load of photos, just resizing, and it took several minutes when the newer cpu was probably several seconds but that's the hardware, not the software.

  • source
  • parent
  • context
  • [–] 5 points 2 weeks ago

    My wife claims pip and application is awful in every way. I cannot believe there is anyone that successfully gets pip who should not. I find it much more likely that there are many people who should get it but don't because their disability prevented them filling in the application.

  • source
  • parent
  • context
  •  

    We're using Terraform to manage our AWS infrastructure and the state itself is also in AWS. We've got 2 separate accounts for test and prod and each has an S3 bucket with the state files for those accounts.

    We're not setting up alternate regions for disaster recovery and it's got me wondering if the region the terraform S3 bucket is in goes down then we won't be able to deploy anything with terraform.

    So what's the best practice for this? Should we have a bucket in every region with the state files for the projects in that region but then that doesn't work for multi-region deployments.

    view more: next β€Ί