AWS SWT management work 1
- jim mason
- jimm1
Key Points
- AWS services can come at 3 layers: iaas, paas, saas
- Most references to AWS refer to paas - EC2 instances and the services that run on them
- EC2 instances can be Windows or Linux
- A low-cost iaas option is LightSail - a VPS server that is fixed price, low-cost with internet connectivity etc - easier to plan than EC2 costs
- Effective cost management of AWS resources and services is a HUGE issue for most companies
- EBS - elastic block storage - can be mounted and file system created for use. can be attached to any single instance
References
| Reference_description_with_linked_URLs_________________________________ | Notes_________________________________________________________ |
|---|---|
| AWS basics | my AWS concepts in confluence |
| https://aws.amazon.com/ | AWS |
| https://us-east-2.console.aws.amazon.com/console/home?region= us-east-2# | AWS account mgt console |
| https://us-east-2.console.aws.amazon.com/console/home?region= us-east-2# | AWS account mgt console - has good starting exercises |
| https://lightsail.aws.amazon.com/ls/webapp/create/instance? region=us-east-1 | AWS Lightsail home page |
AWS-Admin-Work
Environment Config Concepts
Environment logs
App Config Concepts
App logs
Network config
Security config
Certificate Mgt
Compute config
Storage config
App Deployment Options
CICD pipelines
App testing
Code conversion error
https://console.aws.amazon.com/console/home?region=us-east-1#
pSyn$pjm9yz3
RAC594585551661CAR
AWS and Lightsail
CFM - Cloud Financial Management - AWS - where cloud can pay off
https://37signals.com/podcast/leaving-the-cloud/
https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0
https://dev.37signals.com/our-cloud-spend-in-2022/
https://37signals.com/podcast/leaving-the-cloud/
- David’s piece, Why We’re Leaving the Cloud
- 0:59 - 37signals history with on-premise and cloud storage
- 8:26 - How cloud solutions don’t necessary reduce operations teams costs
- 10:58 - What types of companies are the best fit for cloud solutions
- 14:14 - 37signals costs for cloud solutions and potential savings with on-premise options
- 15:25 - Advantages of working with on-premise storage companies that are similar in size to 37signals
- 20:08 - What the transition might look like, including timing
- 26:02 - Advice for medium-sized companies that might be thinking about making the switch
Transcript
Kimberly (00:00): Welcome to Rework a podcast by 37signals about the better way to work and run your business. I’m Kimberly Rhodes, and in case you can’t tell already we’re changing things up a bit. Not only am I new around here, but today we’re switching gears from discussing concepts from the Rework book and diving into something a little more timely. David Heinemeier Hansson, co-founder of 37signals, recently wrote a post titled Why We’re Leaving The Cloud, which created quite a stir, so we thought we’d talk about it. Today I’m joined by David along with Eron Nicholson, 37signals director of operations. Hey guys, thanks for being here.
David (00:36): Thanks for hosting.
Kimberly (00:37): Blew up. David, you wrote this post, it is now all over the Twitter verse. Before we dive into it, what I do wanna know is I wanna make sure for the non-tech people like myself, we’re all on the same page. We’re talking about moving from cloud services like AWS and Google Cloud and hosting our software on our own servers. Is that correct?
David (00:57): That’s exactly right. So we have for many years had one foot in the camp of our own hardware, which is often called on-prem or on-premises where you own your own machines. You don’t necessarily own your own data center and all the other stuff that goes with it. You rent that stuff, but the hardware itself is often something you own. And then the other camp, which is the cloud that everyone knows about aws, Amazon’s GCP with Googles, and we have been running Hey almost well exclusively in the cloud. And we’ve been running summer Basecamp OnPrem with our own hardware and summer Basecamp in the cloud over time. And now I feel like we have enough experience with both sides of the fence to really know what we’re talking about, to objectively look at what’s worth it when, and we’re ready to make some decisions on the basis of that.
(01:52): And the funny thing is, I wrote this post up basically just sort of, oh yeah, this was a thing we’ve been talking about for a long time. Internally, we’ve set some guidelines internally of when we wanted to get off big tech, for example, that this plays into. And then we just had a wonderful meetup in Amsterdam where Eron and I sat down with the whole operations team and we were talking about basically how to do it. So I thought I’d just write this up and didn’t really realize I was tapping into something here, right? Like the hype cycle for cloud is now a decade plus old. And I think there are a lot of other companies like ours who are starting to have doubts as to whether the all cloud all the time is the right answer. They keep getting these astronomical bills.
(02:38): Perhaps they keep failing to realize some of the simplification benefits that they’ve been promised in the cloud. And maybe now they’re starting to ask questions about is this actually right for us? And I wanted to open that discussion by simply proudly stating, Hey, look, this is what we’re doing for our size business, which is a medium size business of some 80 plus employees with a 10 ish person operations team. And and over a hundred thousand customers. This doesn’t actually make sense for us. In a lot of our cases, we have this pretty predictable base load that doesn’t fluctuate wildly. We don’t have a, a Black Friday sales event for example, that spikes everything we have to be ready for. And at the same time, we also have quite a lot of competence at the company for running services in this way. So when those things are true, and you have the very long time horizon that we have, which is also a critical part, right?
https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0
Basecamp has had one foot in the cloud for well over a decade, and HEY has been running there exclusively since it was launched two years ago. We've run extensively in both Amazon's cloud and Google's cloud. We've run on bare virtual machines, we've run on Kubernetes. We've seen all the cloud has to offer, and tried most of it. It's finally time to conclude: Renting computers is (mostly) a bad deal for medium-sized companies like ours with stable growth. The savings promised in reduced complexity never materialized. So we're making our plans to leave.
https://dev.37signals.com/our-cloud-spend-in-2022/
But HEY runs almost entirely in the cloud (with the exception of certain email and image processing services, which run on our own hardware). Our usage of AWS for HEY includes running the full Rails application on Kubernetes clusters via EKS, MySQL database servers via Aurora RDS, Redis via Elasticache, and search via OpenSearch. Additionally, our other legacy apps also run on EKS, and use of RDS for the databases.