I-ALiRT - vpn tunnel#1334
Draft
laspsandoval wants to merge 10 commits into
Draft
Conversation
Contributor
Author
|
I think we won't need this: d) The following networks/prefixes requiring access to NOAA resources will be routed to NOAA N-Wave via static routing by LASP: if we use BGP |
|
@laspsandoval This is a great fix for security purposes, but the system (LASP's IMAP? AWS infrastructure) still won't be covered by an SSP. Is Rachel going to add the AWS infrastructure to LASP's institutional SSP? |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds I-ALiRT Site-to-Site VPN infrastructure for NOAA N-Wave connectivity and wires it into the SDS CDK deployment.
Changes:
- Adds a Virtual Private Gateway and public subnet route propagation.
- Adds a new I-ALiRT VPN construct for NOAA customer gateways and VPN connections.
- Retrieves VPN PSK/router IP configuration and adds a placeholder for NOAA ECS access rules.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
sds_data_manager/utils/stackbuilder.py |
Retrieves NOAA VPN configuration and instantiates the VPN construct. |
sds_data_manager/constructs/networking_construct.py |
Adds VGW creation, VPC attachment, and route propagation. |
sds_data_manager/constructs/ialirt_vpn_construct.py |
Defines NOAA customer gateways, VPN connections, and tunnel crypto settings. |
sds_data_manager/constructs/ialirt_processing_construct.py |
Adds a TODO placeholder for NOAA security group ingress. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Items to provide to NOAA:
Items NOAA provides us:
- Step 1: NOAA sends data
The packet has:
- Step 2: NOAA's border router encrypts the packet
The router has a rule: Traffic destined for the I-ALiRT EIP goes through the VPN tunnel
The router wraps the original packet in an encrypted IPSec envelope. The original packet is now sealed inside. The outer envelope has:
- Step 3: Travels across public internet
- Step 4: AWS VPN Gateway decrypts the packet
The AWS VPN Gateway receives the outer envelope and decrypts it using the pre-shared key (PSK stored in Secrets Manager under
noaa-vpn-psk)The outer envelope is discarded. The original inner packet is restored:
The VPN Gateway hands the packet into VPC.
- Step 5: VPC route table directs the packet to Internet Gateway
- Step 6: Internet Gateway translates EIP to private IP
- Step 7: Container receives packet
Testing
Deployed a minimal version of the VPN infrastructure to a personal AWS account and verified the IPSec tunnel comes up successfully. Used an EC2 instance running strongSwan as a stand-in for NOAA's border
router, configured with the same IKEv2/AES-256/SHA2-256/DH group14 parameters specified in the NOAA N-Wave ICD. The AWS console confirmed IPSEC IS UP on Tunnel 1, validating that the crypto settings and CDK
construct are correct.