Repository navigation
Add Network Segment Access with Tunnel Endpoints pattern - #18
Merged
Merged
Conversation
added 8 commits
October 19, 2026 10:19
cfn-lint 1.51.4's spec rejects the CIDR resource configuration type and the Tunnel VPC endpoint type used by the network segment pattern. Bump both the CI job and the pre-commit hook to 1.57.2 (all repo templates pass). Comments trimmed to the essentials; no functional change to jobs, hooks, triggers or permissions.
Add the tunnel endpoint pattern to blueprint.yaml and its skill snapshot (SHA-256 and date refreshed), teach SKILLS.md and the skill about CIDR resource configurations and the pattern's exceptions (real IPs, non-overlapping VPCs, version floors), and add a pattern-selection heuristic for reaching a whole address range.
… and CONTRIBUTING - README: non-overlapping VPC exception, CIDR resource configuration in key concepts, tunnel endpoint cost line, access-logging scope. - CONVENTIONS: pattern-specific version floors, resource-configuration logging scope, managed-range exception. - CONTRIBUTING: cfn-lint 1.57.2 in the local tools table (lockstep with CI).
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.
What this PR adds
A new Advanced pattern, Network Segment Access with Tunnel Endpoints (
patterns/3-advanced_architectures/2-network_segment_tunnel_endpoint/), showing the CIDR-type VPC Lattice resource configuration consumed through an AWS PrivateLink tunnel VPC endpoint.Closes #15
New pattern
IN_VPC) and a CIDR resource configuration sharing two workload subnets, with a demo web host in each.innerprotoinherit) at boot and route the segment through it. Provider hosts need no changes.awsccfor the resource configuration and the tunnel endpoint, sincehashicorp/awsdoesn't support them yet ([Enhancement]: Support PrivateLink tunnel VPC endpoints for CIDR-type resource configurations hashicorp/terraform-provider-aws#50087). CloudFormation uses a small Lambda-backed custom resource to read the endpoint's per-AZ IPs.Repository changes
1.51.4→1.57.2(the older spec rejects theCIDRandTunneltypes); comments in both files shortened, no functional change.blueprint.yamland the skill snapshot;SKILLS.md,SKILL.mdandpattern-selection.mdupdated.README.md(VPC overlap exception, key concepts, costs),CONVENTIONS.md(pattern-specific version floors, logging scope, managed-range exception),CONTRIBUTING.md(cfn-lint version).Pattern-specific exceptions
10.0.0.0/16/10.1.0.0/16), because the consumer reaches the provider's real IP addresses.hashicorp/aws >= 6.50.0,hashicorp/awscc >= 1.103.0,aws-ia/vpc/aws = 4.9.0.Testing
eu-west-1:tunnel-endpoint.serviceactive,gnv0up toward the same-AZ endpoint IP, both segment hosts answer over HTTP, a non-shared port times out.make deploy/make undeploy)terraform fmt/validate/ tflint, terraform-docs drift, cfn-lint 1.57.2 (all repo templates), checkov (Terraform: 0 failed),validate-package.pyNot included
169.254.168.253): needs theTCP_UDPprotocol, which the CloudFormation schema (and soawscc) doesn't accept yet. The README documents the capability; the pattern will be updated once IaC supports it.