Skip to content

[Feature Request] Integrate Network Connectivity Center (NCC) #58

Description

@aghassemlouei

Feature Description

Replace the use of shared VPC and VPC peering constructs with Network Connectivity Center (NCC) for centralized connectivity management.

Use Case

The current networking implementation does not leverage NCC, resulting in networking code that is split up by compliance regime rather than being a normalized, centralized capability.

Proposed Solution

Reformat the network portion of fast/stages to use NCC. Normalize the networking code so it is a single stage that takes the regime type (e.g., FedRAMP Moderate, IL5) as an input configuration variable.

Compliance & Deployment Context

  • Target Deployment Type(s):
    • US Region Restricted (e.g., Access Policy constraint)
    • FedRAMP Medium
    • FedRAMP High
    • DoD IL4
    • DoD IL5
    • All / General
  • Relevant NIST 800-53r5 Controls: SC-7 (Boundary Protection).

Reusability Check

Stellar Engine prioritizes reusability.

  • I have checked if this functionality can be achieved by extending an existing module or blueprint.
  • I have verified that this does not duplicate existing functionality.

Alternatives Considered

Maintaining the current state where networking logic is duplicated and hardcoded across different regime-specific folders.

Additional Context

N/A

Activity

  1. WandLZhang commented on Sep 13, 2026

    @WandLZhang
    Member

    I have an NCC version of this stage in a fork. One stage, topology picked by dataset.

    It needs net-vpc-factory, which modules/ doesn't have. The stage is written against FAST v54.2.0, so the 13 other modules it calls may not match your interfaces either.

    Cheapest fix is adding net-vpc-factory and pinning the rest. Or move modules/ to v54 for the networking set. Or I backport the stage to current interfaces. Which do you want?

  2. added
    Level of Effort - HighComplex task taking a week or more; consider breaking this down into smaller issues.
    Priority - MediumStandard features and non-blocking bugs; important for the current milestone but not urgent
    Scope - FastRelated to Fabric FAST deployment stages in the fast directory
    on Oct 13, 2026
  3. added
    Priority - HighCritical issues blocking development or users; urgent bugs or core features for release
    and removed
    Priority - MediumStandard features and non-blocking bugs; important for the current milestone but not urgent
    on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or requestLevel of Effort - HighComplex task taking a week or more; consider breaking this down into smaller issues.Priority - HighCritical issues blocking development or users; urgent bugs or core features for releaseScope - FastRelated to Fabric FAST deployment stages in the fast directory

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions