Targets are essentially the things you want your workflows to be able to communicate with. They come in a wide variety of different types depending on the product or platform you want to connect to. Targets can have an account key associated with them but an account key isn’t required. SecureX orchestration comes out of the box with some default targets configured.
Keep in mind that SecureX orchestration runs in a public cloud. This means that any target you want your workflows to communicate with must be accessible from the public internet. If you want to integrate an on-premise product into a workflow, check out the orchestration remote.
Targets come in a variety of different types. Keep in mind that if a target requires an account key, the account key type should match the target type.
|AWS Endpoint||Amazon Web Services APIs|
|Git Endpoint||Git repositories|
|Google Cloud Platform Endpoint||Google Cloud Platform|
|HTTP Endpoint||HTTP-based APIs|
|JDBC Database Server||MySQL, Microsoft SQL, Oracle, and SAP HANA database servers|
|Meraki Endpoint||Meraki devices|
|Microsoft Windows Endpoint||Windows-based hosts and servers|
|SMTP Endpoint||Sending email via SMTP|
|SNMP Endpoint||SNMP-based device management|
|Terminal Endpoint||SSH-based endpoints like switches and routers|
|Unix/Linux Endpoint||Unix/linux-based hosts and servers|
Target groups are a more advanced, but important, concept that allows your workflows to dynamically pick targets from a collection. Groups can contain multiple targets of the same type or mix and match different target types.