Since version 10.2 Jamf has supported an external source for patch management. It requires an external server to be the source for the data. This works great if you are internally hosted, however if you are hosted in the cloud it may be a problem. Is anyone doing this today from their cloud instance? I assume you would have to host a server at your site with the appropriate firewall rules?
Question
User added patch management for Jamf Cloud
+4
+6Hello,
"I assume you would have to host a server at your site with the appropriate firewall rules?" - Correct. You could also host it on AWS or another cloud provider.
https://github.com/brysontyrrell/StupidSimplePatchServer - Really simple one with no GUI. https://github.com/brysontyrrell/PatchServer - The full one with GUI.
You could use the simple one to actually host the patch definitions, and run the full one in a docker container on your machine to create the definitions. A dockerfile is included with the full server. Commands to deploy the simple one on AWS are included.
I have not yet set this up, but am testing it on my local machine in Docker.
+22There is also a free publicly available community patch server that anybody can host their own patch titles on that your titles have modification locked to only you so someone cant change your patch definitions, just use them if it applies. And as you may have guessed it, this was also built by the very kind, intelligent, handsome @brysontyrrell ;)
https://bryson3gps.wordpress.com/2018/04/17/communitypatch-com-beta/
+26We're fleshing out some topics on scalability and community curation/management in the #communitypatch channel on the MacAdmins Slack if anyone would like to chime in.
+19I am writing Beta 2 to reflect those workflow discussions. Should have it up soon.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.