> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-continuous-delivery/ai-agents-deployment/aws-agent-core/step-reference/traffic-shift-step.md).

# Traffic shift step

The traffic shift step routes a percentage of traffic to the revision produced by the deploy step. Add a step for each stage of the canary, for example 10 percent, 25 percent, 50 percent, and 100 percent.

The step type is `ShiftAwsAgentCoreTraffic`. This step requires an AgentCore Gateway on the infrastructure definition, and without a gateway the step rejects with `AGENT.AWS.GATEWAY_NOT_CONFIGURED`. Configure the following fields:

* **Container Registry:** A Harness connector for the registry that hosts the plugin image.
* **Image:** The traffic shift plugin image, `harness/aws-agentcore-plugin:1.0.0-linux-amd64`.
* **Target Revision ID:** The revision produced by the deploy step, `<+steps.Deploy_Aws_Agent_Core_Revision.agentDeployment.revisionId>`.
* **Weight (%):** The percentage of traffic to route to the target revision for this shift.

  <figure><img src="/files/v940r99f7N1LexLOExTP" alt="Shift AWS Agent Core Traffic step parameters showing image, target revision ID, and weight"><figcaption><p>Click to view full size</p></figcaption></figure>