Accessing a private API Gateway via Basti

[danielbollom]

Hey there! I've been trying out Basti for connecting to RDS resources in a VPC over the last few days and it's been super easy to get up and running which has been awesome.

I've hit some issues with trying to set up a custom resource though, in this case a private API Gateway that lives in a VPC.

Two questions if you have a few minutes:

1. Should this be possible to get set up using custom resources?
2. If so, would a config like below be correct or is something missing?

  api-gw:
    target:
      customTargetVpc: <vpc id>
      customTargetHost: <api gateway domain>
      customTargetPort: 443
    localPort: 8080

Thanks so much!

[BohdanPetryshyn]

Hi @danielbollom 👋 I'm glad to hear that you found Basti helpful!

1. Using custom connection target, it's possible to connect to any resource in your VPC as long as it accepts traffic from the Basti EC2 instance. Unlike with the natively supported connection targets, you have to ensure the connectivity manually. A common mistake here is forgetting to set up a security group that would allow traffic from the Basti EC2 instance to the API Gateway (or the VPC endpoint).

2. The configuration looks correct 👌

[BohdanPetryshyn]

@danielbollom, please, let me know if configuring security groups helped you. If yes, please, mark the comment above as an answer

[danielbollom]

Sorry for the delay - fixing the security groups + making sure I had the right headers in my requests worked perfectly. Thanks for your help!

[BohdanPetryshyn]

@danielbollom, could you please mark my comment as answer? I removed my self-assigned mark