Skip to content

docs(byoc): state standing EKS admin access and unsigned ECR image copies - #6483

Closed
ashwinamardeep-ashwin wants to merge 1 commit into
mainfrom
docs/byoc-accuracy-2026-10-posture
Closed

ashwinamardeep-ashwin wants to merge 1 commit into
mainfrom
docs/byoc-accuracy-2026-10-posture

Conversation

@ashwinamardeep-ashwin

Copy link
Copy Markdown
Contributor

Needs review: Arthur Stromquist, Romain Priour

Summary

Posture statements (class B): the existing text is technically true but omits a capability a security reviewer would consider material. Kept separate from the factual-corrections PR so it can be reviewed on its own. Verified against langchain-ai/langchainplus @ 9ae4a56; evidence line numbers refer to the internal sweep byoc-checkmarx-evidence.md (2026-10-05).

File Line Old New Evidence
src/langsmith/byoc-faq.mdx 105 ("Can LangChain read my traces or database contents?") describes only the AWS data-API restrictions adds: "Operating the cluster also requires standing administrative Kubernetes access: the role is granted the AWS-managed AmazonEKSClusterAdminPolicy on the EKS cluster through an EKS access entry. Every API call made with it is recorded in the EKS audit logs in your account, and you can revoke the access entry at any time." V1.a: langsmith-aws-eks-composition.tpl:973-1037 AccessEntry for $provisioningRoleArn (= crossplaneRoleArn) + AccessPolicyAssociation AmazonEKSClusterAdminPolicy, accessScope.type: cluster (116, 134-161, 193)
src/langsmith/byoc-architecture.mdx 61 ("How least privilege is enforced") same new bullet with the same sentence same
src/langsmith/byoc-architecture.mdx 86 "Container images are pulled read-only from LangChain's control plane ECR repositories through VPC endpoints." adds: the ECR copies carry no cosign signatures or SBOM attestations; links Verifying image signatures V2.b: copy_byoc_ecr_images.yaml uses docker buildx imagetools create from internal langsmith-prod/* repos; no cosign copy/crane/.sig/.att (366, 395-398, 401)

Reviewer notes

  • The FAQ answer still opens with "No." With cluster-scoped AmazonEKSClusterAdminPolicy, pods/exec and secrets get/list are implied (evidence V1.b, line 189), so reviewers may want to soften that "No." This PR adds the sentence only and does not change the answer.
  • Wording follows the published BYOC Security Overview phrasing on standing administrative Kubernetes access.

Test plan

  • Vale prose lint (CI lint-prose); not run locally, Vale is not installed on this machine
  • Anchor /langsmith/self-host-mirroring-images#verifying-image-signatures resolves

…pies

Posture statements for security reviewers, verified against code:

- byoc-faq.mdx and byoc-architecture.mdx: the cross-account role is
  granted AmazonEKSClusterAdminPolicy at cluster scope through an EKS
  access entry, so operating the cluster requires standing administrative
  Kubernetes access. It is logged in EKS audit logs in the customer
  account and revocable by the customer.
- byoc-architecture.mdx: the byoc-* ECR copies are produced with
  `docker buildx imagetools create` and carry no cosign signatures or
  SBOM attestations; point to the Docker Hub verification page.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions github-actions Bot added langsmith For docs changes to LangSmith internal labels Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Mintlify preview branch generated: preview-docsby-1791319236-3be7a15

Site preview: https://langchain-5e9cc07a-preview-docsby-1791319236-3be7a15.mintlify.site

Important

Preview links may take a few minutes to start working while the deployment finishes.

Changed documentation pages (preview deep links):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal langsmith For docs changes to LangSmith

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant