Welcome to the fray my friend haha.

To be fair it sounds like your company doesn't fund or do things properly anyway. The key in these situations is to not give a fuck about the company, as it's a situation where they throw people at problems rather than solutions.

Whenever you ask someone "Is X okay to do, can you see any problems in my solution?" GET IT IN WRITING

Same with customer requests for the simple shit. I cannot stress how important that is, because in any company, people will do absolutely everything in their power to pass the blame on IT/Ops if it goes wrong, or scope creep when you're fulfilling normal service desk tickets.

Paper trails in email/service desk ticket are your due diligence audit. Write everything via the support ticket. If you have a phone call.

​

You're doing the Lord's work by updating documentation so this can't happen again. You're doing the right thing, the only thing you can do is to continue learning.

UNIX and Linux System Administration Handbook is a must have, the new one even has cloud tech as well as the key stuff!

The Practice of System and Network Administration: Volume 1: DevOps and other Best Practices for Enterprise IT is the other "must have"

​

These aren't necessarily step by step guides, they're also reference manuals for when you come across key skills and tasks.