Skip to content

fix(vpc): use elastic IP for tunnel connection when available #6306

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
danielsharvey wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

fix(vpc): use elastic IP for tunnel connection when available #6306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions platform/src/components/aws/vpc.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -680,14 +680,17 @@ export class Vpc extends Component implements Link.Linkable {
self.registerOutputs({
_tunnel: all([
self.bastionInstance,
self.elasticIps,
self.privateKeyValue,
self._privateSubnets,
self._publicSubnets,
]).apply(
([bastion, privateKeyValue, privateSubnets, publicSubnets]) => {
([bastion, elasticIps, privateKeyValue, privateSubnets, publicSubnets]) => {
if (!bastion) return;
return {
ip: bastion.publicIp,
// if we have elastic IPs, use the first one (NAT instance IP will be replaced
// by EIP after creation) with fallback to bastion public IP (should not happen)
ip: elasticIps.length ? elasticIps[0].publicIp : bastion.publicIp,
username: "ec2-user",
privateKey: privateKeyValue!,
subnets: [...privateSubnets, ...publicSubnets].map(
Expand Down