A few options here, one is if your AWS deployment methodologies set hostnames that can be keyed off of for your server classes then you could build server classes from there. Alternatively, in deploymentclient.conf you could set clientName differently for different kinds of images and build your server classes based on matching those names. (This latter option is one that i'm thinking about pursuing while rolling out deployment servers. (hence this previous question).
That said, I would challenge @deepashri_123's assertion, Deployment Server is not necessarily always a best practice, and is very environment specific as to if it should be used. it is often the case where it is a better option, but existing considerations of network boundaries, security, and existing patterns could lead to other configuration management techniques Being in an environment where your control of the network is secondary to a cloud service provider, I would highly recommend that forwarders are configured to assert the identity of the deployment server's SSL certificate, lest a malicious actor tricks forwarders into installing their code. but maybe pre-baking is an ok option if redeploy is an acceptable time requirement for changes.
