Attaching and detaching an agent runtime cloud

Before you can deploy an agent to a specific region, you must attach a runtime agent cloud to an environment. A runtime cloud is the regional infrastructure that executes your agent. An environment is the logical grouping that organizes where it runs. Attaching the two tells Agent Garden which regional cloud handles your agent traffic.

Similar to Integration, Agent Garden displays two types of environments: Production and Test.

• Test - where you can test your agent in the Agent Designer test conversational interface.
• Production - where you deploy your agent so it can run in agentic workflows and conversational experiences.

To detach a runtime cloud from an environment, you must first remove all agent deployments from that environment. If you are detaching a test environment, the runtime cloud will no longer appear as an option in the Test panel.

Default environments

Agent Garden automatically pulls your existing environments from Integration. In addition to environments from Integration, Agent Garden provides two default environments:

• North America Platform: Agent Garden Production and Agent Garden Testing environments are both pre-attached to USA East Agent Garden Cloud 01.
• European Platform: Agent Garden Production and Agent Garden Testing environments are both pre-attached to GBR Agent Garden Cloud 01.

Agents deployed before May 2, 2025 are automatically deployed in the Agent Garden Production environment. The runtime cloud depends on your Boomi Platform location:

• North America Platform: USA East Agent Garden Cloud 01
• European Platform: GBR Agent Garden Cloud 01

Important Considerations

• Agent Garden lists environments existing in Integration. You cannot create environments in Agent Garden.
• You can only attach one runtime cloud to one production environment and one test environment at a time.
• You can only attach agent runtime clouds created by Boomi. You cannot modify them.
• To switch a runtime cloud, you must first delete all agent deployments on that environment.
• Test environments allow you to test your agent in the Agent Designer in a specific region. You cannot deploy an agent to a test environment. Agents automatically run in the selected runtime cloud when you test it.

Environment statuses

• Active - The environment is attached to a runtime cloud and accepts deployments.
• Detached - The environment has no runtime cloud attached and cannot accept deployments. Attached a runtime cloud to activate it.
• Deleted - The environment in Integration is deleted. Existing deployments continue to run, but the environment cannot accept new deployments. Delete all agent deployments to remove this environment from Agent Garden.

Attach a runtime cloud

You can also change the existing attached runtime cloud using these steps.

1. Navigate to Environments.
2. Select Configure Runtime.
3. Select the Environment Name.
4. Select an available Runtime Agent Garden Cloud. Each runtime can only be attached to one environment at a time.
5. Select Save.

Detaching a runtime cloud with no deployed agents

Before you can detach an environment, you must remove any deployed agents from the environment.

note

Detaching a test runtime cloud makes the cloud unavailable in the cloud selection drop-down during agent testing.

1. Navigate to Environments.
2. Select the Action icon in the environment.
3. Select Detach runtime.

Detaching a production runtime cloud with deployed agents

Before you can detach a runtime, you must delete all deployed agents running in that runtime cloud.

1. Navigate to Packages and Deployments.
2. Select Deployments.
3. In Actions, select Delete.
4. Navigate to Environments.
5. Select the Action icon in the environment.
6. Select Detach runtime.

Next steps

• Package and deploy an agent to an environment. Refer to Packaging and deploying an agent for a step-by-step guide.