akeyless-agentcore-rta
Akeyless Agentic Runtime Authority (ARA / RTA) for AWS Bedrock AgentCore.
Agents call list-secrets, query-db, service-execute, and list-sub-tools. Credentials stay on your Akeyless Gateway — tool responses contain paths, metadata, and query/action results only.
Not the secrets-fetch library. For get_secret() / pulling secret values into the agent, use akeyless-agentcore-runtime. You can use both in one architecture (bootstrap via secrets runtime; DB/cloud via this package).
| Concern | This package (RTA) | Secrets runtime |
|---|---|---|
| Goal | Do work with secrets | Fetch secret values |
| Tools | list-secrets, query-db, service-execute, list-sub-tools | list / get secret |
| Credentials in agent | Never | Yes (values returned) |
| Gateway | Required customer GW with ARA | SaaS API or GW OK |
Requirements
- Python 3.10+
- Akeyless Gateway with ARA enabled (not
api.akeyless.io) - Auth method your AgentCore role can use (production: AWS IAM cloud identity)
Install (local)
cd bedrock-agentcore-akeyless-rta
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[mcp,dev]"
Quick start — client
from akeyless_agentcore_rta import AkeylessRtaClient
client = AkeylessRtaClient() # reads AKEYLESS_* env
for s in client.list_secrets():
print(s.name, s.target_type) # never prints credentials
rows = client.query_db("SELECT 1", secret_name="/prod/db/readonly")
print(rows.results)
Quick start — MCP on AgentCore
# env (required)
export AKEYLESS_GATEWAY_URL=https://gw.example.com:8000
export AKEYLESS_ACCESS_ID=p-xxxxx
export AKEYLESS_ACCESS_TYPE=aws_iam # or access_key locally
python examples/mcp-server/server.py
# AgentCore: protocol MCP → examples/mcp-server/server.py
Environment
| Variable | Required | Notes |
|---|---|---|
AKEYLESS_GATEWAY_URL |
Yes | Customer GW (https://gw:8000 or …/api/v2). Public SaaS rejected. |
AKEYLESS_ACCESS_ID |
Yes* | Auth method access id |
AKEYLESS_ACCESS_TYPE |
No | Default aws_iam. Also: access_key, oidc, saml, jwt, … |
AKEYLESS_ACCESS_KEY |
For access_key | Local/dev only |
| (OIDC/SAML) | — | Browser login to Gateway; needs Access ID only |
AKEYLESS_AGENT_ID |
No | Default bedrock-agentcore |
AKEYLESS_MCP_ID |
No | Default akeyless-agentcore-rta |
AKEYLESS_DEFAULT_SECRET_NAME |
No | Optional default path for execute tools |
* Or AKEYLESS_TOKEN for a pre-issued session token.
Docs
| Guide | Description |
|---|---|
| Akeyless setup | Auth method, ARA RBAC, chicken-and-egg IAM bind |
| AgentCore deploy | MCP protocol, envVars, invoke |
| Security | Checklist |
| Maintainer guide | Branch protection, approvals, PyPI environment |
| Publishing to PyPI | Trusted publishing setup |
| Contributing | Development setup |
Repository: github.com/akeyless-community/bedrock-agentcore-akeyless-rta
Development
pip install -e ".[mcp,dev]"
pytest
Run pytest inside this package directory so the workspace root does not collect unrelated tests.
Related
- Secrets at runtime (values in agent):
akeyless-agentcore-runtime - Product docs: Agentic Runtime Authority
Metadata
Release files for akeyless-agentcore-rta 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| akeyless_agentcore_rta-0.1.0.tar.gz | 23.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| akeyless_agentcore_rta-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.5 kB
Release files / akeyless_agentcore_rta-0.1.0.tar.gz
| Download URL | akeyless_agentcore_rta-0.1.0.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93700283208ad0d0f988abab8b7f77e643af6bd99968a093869ed4587de038b5
|
|
BLAKE2b-256 checksum How to use checksums |
9871af6c37ea7b56a284a8ec6b5b9e4892fa99416604cd9c0c5e383250551c3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / akeyless_agentcore_rta-0.1.0-py3-none-any.whl
| Download URL | akeyless_agentcore_rta-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a612712bf276646b49511c7d1a664656aa1197b72e7d990dba06889104973aa4
|
|
BLAKE2b-256 checksum How to use checksums |
ea6d1498c6082d5834edbd3808f7df4f95f49f8c6d96c80e501124903c80e583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for akeyless-agentcore-rta 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for akeyless_agentcore_rta-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.