Well, in summary,
the anticlimax is that Ansible adds essentially no additional
networking complexity to your environment.
Hopefully, you already are good with DNS, so you understand that.
So that's going to help you get your inventory set up with DNS names as
appropriate and aliases within Ansible if necessary.
As far as the TCP/IP protocol stack, it's all garden variety stuff,
either SSH or Windows RM.
Nonetheless, always go the extra mile for security.
Good example of this is when you're using WinRM remoting,
you can either do it with HTTP or HTTPS.
Now TLS is going to require you to stand up a public key
infrastructure or PKI because you're not going to want to
use self‑signed certificates, but that's going the extra mile.
Frankly, you may not have a choice if you have compliance audits to deal with.
Anyway, I want to thank you so much for staying with me.
I appreciate you.
I couldn't do what I do without you.
Let's put it that way.
If you want to look at my other Pluralsight courses,
I created a short name, timw.info/ps. And if you want to engage with me,
that's fine.
My work email is tim‑warner@pluralsight.com.
Thanks again.
I wish you all the best.