Ugh this sounds like when I worked at Oracle/OCI. Some environments required a VPN, some a jumpbox, and some required logging into a virtual desktop, and then logging into a jumpbox. Just thinking about it gives me PTSD

▲

john_strinlai 2 hours ago | parent [-]

any sufficiently large organization that is around for a decade or two trends towards spaghetti-access

▲

alistairSH an hour ago | parent | next [-]

Yup, same boat here (mid-size company).

All the corporate stuff is behind Okta, so that easy enough.

But all the dev/test systems are a mix of SSO, individual logins, etc. At least they're all behind the same VPN (except when they aren't, but that's less common).

And of course, if you're a cloud engineer (vs "normal" software engineer), you also have to deal with AWS access, which is a whole different can of worms.

▲

benterix an hour ago | parent | prev [-]

And yet, somehow AWS managed to get this right-ish. They evolved, learned by making mistakes, and created de-facto standards (like object storage protocol) on the way, while at the same time supporting decades-old services. And I'm sure they'll withstand the current AI craze.

	▲	jen20 37 minutes ago \| parent [-]
		AWS had the benefit of not trying to retrofit IaaS on top of a (already bad) PaaS.