In general, devops tooling makes management of cloud resources and services programmatic. You put in effort now, in order to save effort later. One effort save

In general, devops tooling makes management of cloud resources and services programmatic. You put in effort now, in order to save effort later. One effort saved is the ability to scale up/down. Another effort saved is source of truth / documentive. When you've got the infrastructure recorded "as code", then you don't have to worry about knowledge being lost if the devops engineer leaves. (You don't have to worry if the devops engineer made changes no one knows about). The tools might not be valuable for all cases, sure; e.g. if you're always going to remember what changes you made, and it's just your server.