- Joined
- Jul 4, 2006
- Messages
- 5,128
- Location
- Lincoln, Nebraska
- Display Name
Display name:
Jason W (FlyNE)
Many many things to weigh, obviously. But the "one-stop shop" aspect of what you posted outweighs everything for me. I don't have time to manage a sendgrid account in addition to AWS. Nor encryption keys. Nor WAF. Nor a CDN provider. As it stands now I could create one login and grant complete access to the entire (self-contained) environment. Simplicity over extreme cost savings. At least when the "extreme costs savings" would likely equate to less than 10%/year.Not so bad, then. Have you actually seen any value in GuardDuty? We've been fighting among ourselves about the value (or lack thereof) of trying to shim a traditional IPS in to the AWS network model, and GuardDuty would seem to provide some of that function, even though we can't use our own intelligence sources. Then again, being limited to what effectively looks like reputation-based lists (IP/domain) seems a bit low in the value-add department for the price.
[semi-coherent ramble]
My only thought for costs savings would be to investigate some of the purpose-built VPS hosts. AWS/Azure/etc just don't make financial sense when all you're doing is VPS/IaaS colocation. They absolutely shine when you're taking advantage of the P/SaaS options in conjunction with or replacing IaaS, though! The big disadvantage to the purpose VPS hosts is that it wouldn't be one-stop shopping anymore, leading to more complicated administration and maintenance of supporting and supported resources, fostering additional risk to the service, of course. Since I'm still a few pots of coffee away from fully functional this morning, I could probably convince myself back and forth on this one a few more times.
[/semi-coherent ramble]
P.S. I have no gripes with how you're doing it, more curious than anything. The site's never down when I bother to check in, and the community clearly feels the same since you can collect a couple of years worth of funding in a couple of months!
Add to that the fact that managing AWS accounts and resources is *squarely* in the middle of what I do...so I'm able to apply already acquired (and paid for) skills to my volunteerism for PoA. That's what won.
Sounds like you've assembled totally reasonable thoughts on things. The current setup is where I've landed.