Integrating Conjur Cloud with GitHub Actions (cloud runners) — does Edge make sense here?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Integrating Conjur Cloud with GitHub Actions (cloud runners) — does Edge make sense here?

L3 Networker

I'm integrating GitHub Actions with Conjur Cloud to fetch secrets in pipelines. I'm only using GitHub's own cloud-hosted runners (not self-hosted).

My question: in this scenario, does it make sense to deploy an Edge instance, or is the recommended approach to connect runners directly to Conjur Cloud (SaaS) via JWT/OIDC authentication?

My understanding is that Edge is meant for fixed workloads that need low latency or offline access, which doesn't apply to ephemeral GitHub-hosted runners. Has anyone made this architecture call before, or is there an official CyberArk recommendation on this?

I'm also thinking about resilience: if all pipelines depend on Conjur Cloud (SaaS) being reachable, what happens during scheduled maintenance or an outage? Has anyone actually hit downtime on Conjur Cloud/Secrets Manager SaaS that broke their CI/CD pipelines? If so, how long did it last, and is there a published SLA or maintenance window policy I should plan around?

2 REPLIES 2

L4 Transporter

Hi @l b​ CyberArk's Conjur/GitHub integration documentation is centered around JWT/OIDC authentication from GitHub Actions directly to Conjur, including examples that explicitly use GitHub's OIDC token claims and even reference

runner_environment: github-hosted

.GitHub - cyberark/conjur-action: GitHub Action for secured CyberArk Conjur secret retrieval and impo...

L3 Networker

Thanks for the reply, @PY ,

I want to make sure my two original questions don't get lost:

Edge vs. SaaS, is there an official recommendation, or just documentation precedent? The conjur-action example shows direct JWT/OIDC works technically, but I haven't seen anything that explicitly states Edge is not recommended for ephemeral, cloud-hosted runners (vs. just "not necessary"). Is there a CyberArk architecture guideline that draws this line explicitly (e.g., "Edge is for X, direct SaaS auth is for Y")?

 

Resilience / SLA, this is the part I really need input on. If every pipeline depends on Conjur Cloud (SaaS) being reachable at runtime, what's the blast radius during a scheduled maintenance window or an unplanned outage? Specifically:

  • Is there a published SLA or maintenance window policy for Conjur Cloud / Secrets Manager SaaS I can reference when presenting this architecture internally?

Has anyone here actually experienced downtime that broke CI/CD pipelines relying on direct Conjur Cloud auth? If so, roughly how long did it last?

  • 27 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!