Using existing VPC

[julianblue]

Hi,

I am trying to deploy the stack using an existing vpc. The thought of line was to replace

https://github.com/developmentseed/eoapi-cdk/blob/main/integration_tests/cdk/app.py#L27-L35

and referencing the existing vpc by its id. I am facing issues getting this running. Are there any insights on how to do this ?

The aim is to not have publicly accessible endpoints, but internally accessible within the vpc.

Thanks in advance.

[frederichaase]

+1 This would be really useful!

[emileten]

Thanks for the discussion @julianblue !

Could you be more specific regarding this statement

I am facing issues getting this running.

What did you try exactly and what error did you get?

There is a well documented method to import an already existing VPC in a given stack, Vpc.from_lookup. Perhaps you have already tried without success?

[julianblue]

Hi @emileten ,
thanks for the quick reply. Additional changes such as vpc_subnet selection seemed to have been needed and we could not fully get it to run as expected. Is there an example app.py that uses an existing vpc and uses a custom domain name for the separate components (very similar to the eoapi dev deployed, but not publicly accessible) ?
Appreciate any insights here. Thanks.

[julianblue]

Hi @emileten ,
any updates here ? There seem to be some processes in the cdc that hinder the use of an existing vpc.
I appreciate any input.
Thanks

[emileten]

Hi @julianblue,

Is there an example app.py that uses an existing vpc

No, there is no example of eoapi-cdk constructs usage we have internally that makes use of an imported vpc. In the few example applications we have, we always create a new vpc.

That being said, we have an application that does not make use of the eoapi-cdk constructs but deploys the same infrastructure for the VEDA project (it just doesn't import the constructs and re-implements them within the app) . They import an existing VPC using the Vpc.from_lookup method that I mentioned above..

Additional changes such as vpc_subnet selection seemed to have been needed and we could not fully get it to run as expected.

Do you have a code snippet to show and perhaps the corresponding error ? I can take a quick look. I unfortunately won't have time to test things myself as I am caught up in other projects.

[julianblue]

Thanks @emileten . That helped.
As the cdk creates an http api-gateway, does this mean the endpoints currently can only be public ? Or am I missing something.