[bedrockagentcorecontrol-controller] GatewayTarget: support the managed `connector` MCP target type

[AlJohri]

Is your feature request related to a problem?

GatewayTarget (v1.11.0) exposes only apiGateway, lambda, mcpServer, openAPISchema, and smithyModel under targetConfiguration.mcp — not the managed connector type. This makes AWS-managed connectors, e.g. the Web Search tool, impossible to provision declaratively. Gateway + the IAM role already work through ACK, but the target must be created out-of-band, breaking a GitOps workflow.

Describe the solution you'd like

Add the connector shape (already in the CreateGatewayTarget API / current boto3 model) to spec.targetConfiguration.mcp:

"targetConfiguration": {
  "mcp": {
    "connector": {
      "source": { "connectorId": "web-search" },
      "configurations": [{ "name": "WebSearch", "parameterValues": {} }]
    }
  }
}

Since the shape already exists upstream, this looks like a regen against a newer SDK model rather than net-new modeling.

Describe alternatives you've considered

Creating the target out-of-band via aws bedrock-agentcore-control create-gateway-target (or the boto3 SDK) — works but defeats declarative management. The same gap exists in hashicorp/aws's aws_bedrockagentcore_gateway_target, so there's no declarative alternative today.

References

The equivalent gap is already tracked on the Terraform side:

• Issue: hashicorp/terraform-provider-aws#48503 — Add support for connector target configuration
• PR: hashicorp/terraform-provider-aws#48706 — add connector MCP target configuration

[github-actions]

Hello @AlJohri 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[AlJohri]

Opened a draft PR implementing this: aws-controllers-k8s/bedrockagentcorecontrol-controller#40

It un-ignores the Connector MCP target type and models the required
ConnectorConfiguration.ParameterValues document as a JSON string (marshaled
in hooks, same pattern as the lambda tool-schema fields). Validated end-to-end
against live AWS with the web search connector (create + parameterValues
update reconcile cleanly to READY/Synced).