Re:Ask HN: AWS users, is simplifying AWS a problem worth sol...
by quintes on Friday May 27, 2022 @04:31PM
(#31534523)
Depending on the needs of your clients then that could be a simple digitalocean or heroku, but as they grow out and demand additional services will you be able to offer those or will they have to migrate?
On networking, you could set it up for them but would it be opinionated, ie your way only, or provide the flexibility of AWS and azure networking, vpc, gateways, transits and topology flex, and if not the client may feel constrained.
To better help you then I think you should draft up the service you intend to deliver and test if the market wants that, vs competitor offerings vs AWS scale. And I mean lofi don’t build, test the well defined proposition.
Re:Ask HN: AWS users, is simplifying AWS a problem worth sol...
by kamrani on Saturday May 28, 2022 @01:27AM
(#31537844)
Well to be clear, my question was to provide the service on your own AWS account. This way, you'll have access to all those extra services whenever you need them, and at the same time you can benefit from all the simplicity of such a PaaS experience.
The service connects to your AWS account and builds stuff for you in your own account, if it makes sense.
This can mean hosting static websites, applications on ECS, EKS, database, and Redis. Also it includes all the necessary underlying networking set up.
The rest of services are usually provided in their simplest possible form anyway.