Connect Cloudflare Documentation to ECA
Give ECA governed access to Cloudflare Documentation’s 2 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Documentation to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Cloudflare Documentation in Runlayer
Add Cloudflare Documentation from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Cloudflare Documentation’s 2 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Cloudflare Documentation
Sign in the way Cloudflare Documentation requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Documentation from ECA
Cloudflare Documentation’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
2 Cloudflare Documentation tools in ECA
Runlayer policy decides which of these ECA users can call.
Migrate pages to workers guide
Migrate pages to workers guide.
Search Cloudflare Documentation
Search the Cloudflare documentation.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Documentation call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more