Skip to content

Deployment Fixes - Node 24 and OpenCTI ingress open - #1695

Merged
nickviola merged 2 commits into
developfrom
jb-lz-deployment-fixes-10-30-2026
Nov 5, 2026
Merged

nickviola merged 2 commits into
developfrom
jb-lz-deployment-fixes-10-30-2026

Conversation

@jayjaybunce

Copy link
Copy Markdown
Contributor

🗣 Description

Upon deploying to CAWS Staging today (Friday Oct 30), two issues were discovered:

  1. serverless-esbuild does not support node 26. Serverless-esbuild. Serverless-esbuild is a plugin used by oss-serverless to deploy the frontend application to lambda. While oss-serverless officially supports Node26, the plugin required to build and run the React app as a Lambda only supports Node24.
  2. OpenCTI ingress CIDRS on 443 were opened to 0.0.0.0/0 to allow all ingress IPs. This needed to be reflected in OpenCTI terraform configuration.

Changes Made
Updated runtime in frontent/serverless.yml to nodejs24.x
Updated Node version in frontent/package.json

Updated OpenCTI ingress CIDR on port 443 to 0.0.0.0/0

The changes mentioned above have already been deployed, the purpose of this PR is simply to bring the repo up to date with these changes so we don't need to make these changes again prior to the next CAWS deployment.

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All future TODOs are captured in issues, which are referenced in code comments.
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
  • Tests have been added and/or modified to cover the changes in this PR.
  • AI was used for research and/or understanding purposes while creating this pull request.
  • AI was used to generate code in this PR (either fully or in part).
    • I attest that I understand the AI-generated code and its functionality.
    • I am comfortable answering questions about the implementation of the AI-generated code.
  • All new and existing tests pass.
  • Bump major, minor, patch, pre-release, and/or build versions as appropriate via the bump_version script if this repository is versioned and the changes in this PR warrant a version bump.
  • Create a pre-release (necessary if and only if the pre-release version was bumped).

✅ Pre-merge checklist

  • Revert dependencies to default branches.
  • Finalize version.

✅ Post-merge checklist

  • Create a release (necessary if and only if the version was bumped).

@rapidray12 rapidray12 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolves cve-2026-111497

@nickviola
nickviola merged commit 5edf5ac into develop Nov 5, 2026
24 of 25 checks passed
@nickviola
nickviola deleted the jb-lz-deployment-fixes-10-30-2026 branch November 5, 2026 19:30

This branch was successfully deployed

1 inactive deployment
integration — beed0cfb Deployed Oct 30, 2026 by jayjaybunce via integration #1041
staging — beed0cfb Deployed Oct 30, 2026 by jayjaybunce via staging #1041
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants