You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request] Integrate Network Connectivity Center (NCC) #58
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)
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?
Activity
WandLZhang commentedon Sep 13, 2026
I have an NCC version of this stage in a fork. One stage, topology picked by dataset.
It needs
net-vpc-factory, whichmodules/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-factoryand pinning the rest. Or movemodules/to v54 for the networking set. Or I backport the stage to current interfaces. Which do you want?