I use my own CA to create SSL certs for services in my infra. These certs are signed directly by my CA. 

It comes to me that this is likely a weak strategy, as if the cert was to be compromised, I need to create new ones from the one CA. If the CA gets compromised, game over as every service will need to be updated.

So my understanding is that the typical way to 'protect' oneself and 'dilute' concern is to create a chain of certificates, and sign the service certificates with the end of the chain, so that if the signer gets compromised, the next level up can be used to create a new signing cert. 

Do I get that right?

What I'd like to do then is create my own cert chain. 

The whole TLS/SSL stuff is still a bit hazy to me, but as I can see, one first create a master key, with `openssl genrsa` then create a self-signed certificate using that key with `openssl req -x509 -new` to create the CA.

Then I can create new keys, and certificate signing requests with `openssl req -new -key' and sign the request with my CA with`openssl x509 -req -CA ca.pem ...`

So, to create a certificate chain, what am supposed to do? 

Do I simply create a new key, new signing request, and sign it with the last signed certificate instead of the CA? And so on until I have enough levels of protection, then sign all cert/key pairs with the lowest level cert? 

This stuff is confusing and I'd like to get it right ;-)

Everything I find only about TLS is overwhelmingly complicated, while the 'simple' tutorials are obscure.
I'm looking through the openssl man-pages but I'd like to get a simple explanation of the process, then I'll make sure to get each step right.

Thanks for your insight.