PlainID supports an AWS Bedrock AgentCore Gateway Policy Orchestration Point (POP) in the Integrations Workspace. The POP receives the tool inventories and tool calls the Authorizer reports from your Amazon Bedrock AgentCore Gateway, and shows you the MCP servers, tools, and agents the Platform discovers there.
Each gateway has one POP.
Prerequisites
Before you start, ensure you have:
- The Authorizer stack deployed with
DiscoveryEnabledset totrue, so you have itsDiscoveryRoleArnandDiscoveryExternalIdoutputs. See [Configuring the Amazon Bedrock AgentCore Gateway Authorizer](LINK: AgentCore configuration) for more information. - Your AWS Account ID, Region, and gateway ID.
- An existing Application and a Policies Workspace in your PlainID Environment.
Creating the POP
To create the POP:
- In the Integrations Workspace, create a new POP and select AWS Bedrock AgentCore Gateway. See Managing POPs for more information.
- Enter the connection details described in the table below.
- Link an existing Application and a Policies Workspace. The Platform selects the Agent Registry as the linked Identities Workspace automatically.
- Save the POP.
- The Certificate download window opens. Select Download to save the certificate files to your computer, then select Done. You can select Download again while the window stays open.
To read the stack outputs, run:
aws cloudformation describe-stacks --stack-name plainid-agentcore-authz-<gateway-id> \
--query "Stacks[0].Outputs[?starts_with(OutputKey,'Discovery')].[OutputKey,OutputValue]" --output text
Connection Details
| Field | Description |
|---|---|
| Account ID | The AWS account that contains your gateway. |
| Region | The AWS Region of your gateway. |
| Role ARN | The DiscoveryRoleArn stack output. PlainID assumes this role to list your gateway's targets. |
| External ID | The DiscoveryExternalId stack output. |
| Gateway ID | Your gateway ID, for example acme-tools-a1b2c3d4e5. It must match the stack's GatewayIdentifier. |
You can change the External ID and Gateway ID after you create the POP. All other fields are fixed at creation.
The role allows only listing the targets of this one gateway, and only PlainID's discovery service can assume it, with the External ID. A stack update keeps the External ID. If you delete the stack or turn off DiscoveryEnabled, the stack deletes the role and External ID. When you deploy again, enter the new outputs in the POP.
Working with the Certificate
The POP issues a client certificate that the Authorizer presents each time it reports to PlainID. The certificate is valid for one year from the day you create the POP.
Storing the Certificate
Store the certificate and its private key as Parameter Store parameters, then turn on reporting:
- Store the certificate as
collector_cert_pemand the private key ascollector_key_pem. See Step 3 in [Configuring the Amazon Bedrock AgentCore Gateway Authorizer](LINK: AgentCore configuration#step-3) for the commands. - To report tool calls as well, update the stack with
TransactionalEnabled=true.
The stack, the POP, and the certificate must all belong to the same gateway. If they don't match, nothing reports an error, but the POP shows the gateway's targets with no tools.
Getting a New Certificate
Get a new certificate before the current one expires, or if you lose the files.
To get a new certificate:
- In the Integrations Workspace, open the ⋮ menu on the AWS Bedrock AgentCore Gateway POP card.
- Select Download Certificate. The Platform generates a new certificate and downloads it to your computer.
- Store the new files with
put-parameter --overwrite. The Authorizer picks them up withinCredentialsReloadSeconds(five minutes by default).
Viewing Discovered Objects
After the Authorizer starts reporting, open the POP to see what the Platform discovered:
- Observability opens by default and shows the traffic the Authorizer reports.
- Vendor Objects lists the MCP servers, tools, and agents the Platform discovered through the gateway.
Notes
- The Platform discovers tools only when an agent calls
tools/listor runs a semantic search through the gateway.