Skip to content

Conversation

@danielsharvey
Copy link

  • Add natSecurityGroup and bastionSecurityGroup to Vpc component properties
  • Return security group references from createNatInstances() and createBastion()
  • Update component state to track and persist security groups
  • Add documentation for new security group outputs

This allows users to reference and modify security groups for NAT and bastion instances when needed for custom networking configurations.

Addresses #6282.

- Add natSecurityGroup and bastionSecurityGroup to Vpc component properties
- Return security group references from createNatInstances() and createBastion()
- Update component state to track and persist security groups
- Add documentation for new security group outputs

This allows users to reference and modify security groups for NAT and
bastion instances when needed for custom networking configurations.

Addresses anomalyco#6282.
@vimtor vimtor self-assigned this Dec 17, 2025
@danielsharvey
Copy link
Author

I omitted reference handling - fixing now.

Add logic to import existing NAT instance and bastion security groups
when using an existing VPC. The security groups are tagged with
`sst:is-nat-sg` and `sst:is-bastion-sg` respectively, allowing them
to be discovered and imported into the Pulumi state.

Addresses anomalyco#6282.
Wrap the error throw inside vpcId.apply() to properly resolve the Pulumi
Output before displaying the VPC ID in the error message. This prevents
showing an unresolved Output object in the error text.
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.

2 participants