Agent service
Register an agent service that represents your AI agent and targets AWS Agent Core.
An agent service represents a single AI agent in Harness CD. It defines the agent identity, the target runtime, the container image the agent runs from, and any configuration variables the agent needs at runtime. This page shows you how to register an agent service that deploys to AWS Agent Core, the Amazon Bedrock AgentCore runtime.
For prerequisites, go to Before you begin on the overview.
Open Agent Services
Agent services live in the Continuous Delivery & GitOps module. Select Agent Services in the left navigation to open the listing page, which shows every agent service in the project. Use the search field to filter by name, and select any row to review or edit its configuration.
Register an agent service
To register an agent service, select New Agent Service on the listing page and complete the Register an Agent panel.
{/* IMAGE PLACEHOLDER: Register an Agent panel with AWS Agent Core selected, showing Image URI and Execution Role ARN fields (register-agent-aws.png) */}
In Agent name, enter a name for the agent. Harness generates the agent Id from the name. Select the edit icon next to the Id to change it before you save.
Under Deploy target, select AWS Agent Core to deploy the agent to Amazon Bedrock AgentCore.
In Image URI, enter the Amazon ECR URI of the agent container image, for example
123456789012.dkr.ecr.us-east-1.amazonaws.com/agent:1.0.0.In Execution Role ARN, enter the IAM role the agent assumes at runtime, for example
arn:aws:iam::123456789012:role/AgentCore. AgentCore uses this role to pull the image and run the agent.(Optional) Add config variables. Go to Add config variables for details.
(Optional) Expand Metadata to add a description and tags.
Select Save.
Add config variables
Config variables pass configuration to the agent at runtime. They correspond to the parameters defined in your AgentCore CLI project files, specifically agentcore/agentcore.json (project and agent configuration) and agentcore/aws-targets.json (AWS account and region targets). When you deploy through Harness instead of running agentcore deploy locally, config variables are how you supply those same parameters at deploy time. Go to Get started with the AgentCore CLI to review the full set of supported parameters.
To add a config variable, select Add variable and complete the panel:
Type: The variable type, either String, Number, or Secret. Plain values reach the agent environment as-is, and secret values resolve through the Harness secret manager at deploy time.
Name: The variable name.
Value: The variable value. For a secret, reference a Harness secret.
Set variable as required during runtime: Set to True to require a value at runtime.
Description: (Optional) A description of the variable.
{/* IMAGE PLACEHOLDER: New Variable panel showing Type, Name, Value, required, and Description fields (new-variable.png) */}
Review an agent service
Select an agent service from the listing page to open its details.
The Configuration tab shows the agent identity, the target platform and its settings, the platform config such as the image URI and execution role ARN, and any config variables. You can edit the configuration from this tab.
{/* IMAGE PLACEHOLDER: Agent service Configuration tab showing Identity, Target platform, Platform Config, and Config Variables (agent-service-configuration.png) */}
The Summary tab shows the agent details and the list of deployments that reference this agent service across environments. Referenced by shows the pipelines and other entities that use the agent service.
{/* IMAGE PLACEHOLDER: Agent service Summary tab showing About and the Deployments list (agent-service-summary.png) */}
Next steps
After you register an agent service, configure the environment for AWS Agent Core and build the deployment pipeline.
Last updated
Was this helpful?