This thread is permanently archived
AWS is not a fun environment
| How is AWS different from having a vps somewhere? I have never used AWS for complete lack of interest but I have used vps several times. They basically give you a means to install an os to start with and you are on your own from there to do anything you want which does not cross the limits of what the hoster has set you can do.
But AWS with API and extended documentation and frontend vs. backend layers... What is that for, precious?
| Mmm currently I’m setting up a lambda function that touches a few nosql tables when it through an api endpoint and building up the CD pipeline so that when a change to develop it automatically runs tests deploy to dev environment, runs integration tests and waits for approval before deploying to production. Literally all the services are managed so that I don’t have to do like anything for provisioning. But it’s not very fun as there are a lot of hidden details they don’t tell you
| It’s namely managed services. I don’t have to set up a build server, or environment. Create the nosql tables. And it’s pay as you go. So in terms of my lambda if it runs for 2sec then that’s all I pay for compute wise. And it scales up based on demand.
| I see. Like setting up legolike atomic units/processes which connect to each other via API acording to the logic you have defined somewhere. That is what is interpreted from AWS and it carries along with that workflow, returning the end result, probably meaningless to AWS but exactly what you require.
Seems nice actually.
| Problem is the documents are usually out of date, they only give the simplest of examples, for cloud formation the will tell you a field wants type string but not tell you the values it can take, the console is not that fun to work with for some services because it’s based on how each team implemented it. Also there are over 120 services now. And cloud formation the Infrastructure as code has way more resources to build out your infrastructure with button click
| The latest cloud formation user guide is 2000 pages and like I said give only simple examples for each type of resource.
| I understand. Updating things often at the api and interfacing level is never a good thing. It breaks the idea of what they are for on the first place. APIs ideally should never change and realistically should change as rarely as possible. You end up rebuilding again and again.
| AWS doesn't even update their documentation, and their AWS Academy shit is outdated af.
This thread is permanently archived
| Fucking shitty documentation, nothing freaking works with cloud formation, and their frontend console designers should be ashamed especially the one who made the console for API gateway. That whole team needs to be fired