Cloud-Hosted Agent

Cloud hosted agents can be used when you do not want -

• To install the pre-requisite software required by the agent (i.e. Java)
• To run the agent on your own machines or if you do not have any servers
• The Agent / Workers to download and scan applications on cloud
• A default cloud agent will be created at part of the initial setup

Configure Cloud Hosted Agent

1. Navigate to Global Settings -> Job Types
2. Edit Anypoint Code Analysis Job and set the Client Id and Secret of the Connect Apps which should be used to connect with the Anypoint Platform
3. Once the settings are saved, the Cloud Agent will be able to connect with the Anypoint Platform and execute the configured schedules
4. Once the credentials are configured, navigate to Global Settings -> Agents , and make sure the agent status is RUNNING
5. Re-log in, and start configuring the schedules

AWS job types (from 26.4.1) need no credentials under Job Types. Each AWS account's access key is entered on its AWS organization; see Organizations

Scaling Cloud Hosted Agents

Cloud agents that are started by a container platform can register themselves instead of being created in advance. Set AGENT_WRAPPER_SECRET on the IZ Server and start each agent with --agentWrapperSecret and an optional --deploymentInstanceId. Each new instance either reuses a stopped agent or is created as a new cloud-hosted agent with Default Workers Count workers.

From 26.4.1 the agent image no longer contains a built-in bootstrap secret. AGENT_WRAPPER_SECRET must be set on the server, and every auto-registering agent must be started with the same value, for example FALCON_AGENT_OPTS=--serviceUrl "https://<HOST>" --agentWrapperSecret "<AGENT_WRAPPER_SECRET>". A wrong or missing value is refused with Invalid agent token / secret. Agents started with their own agent id and secret from Download Agent do not use it.

See Also

• Agent Job Types
• Self-Hosted Agent