Exposing Kong Admin API to internal network
up vote
1
down vote
favorite
We have a Kong Gateway running within a VPC in AWS. Currently, the Admin API for the Kong Gateway is restricted to only localhost traffic using
export KONG_ADMIN_LISTEN="127.0.0.1:8001"
export KONG_ADMIN_LISTEN_SSL="127.0.0.1:8444"
We'd like to allow microservices within the same VPC to register their own routes when they get deployed. In order to do this we need to open up the KONG_ADMIN_LISTEN
to other machines within the VPC. However, we don't want any machine outside the network to be able to access it.
I'm pretty new to networking and did not find the Kong docs very clear on how to do this. Any recommendations?
networking microservices amazon-vpc kong
add a comment |
up vote
1
down vote
favorite
We have a Kong Gateway running within a VPC in AWS. Currently, the Admin API for the Kong Gateway is restricted to only localhost traffic using
export KONG_ADMIN_LISTEN="127.0.0.1:8001"
export KONG_ADMIN_LISTEN_SSL="127.0.0.1:8444"
We'd like to allow microservices within the same VPC to register their own routes when they get deployed. In order to do this we need to open up the KONG_ADMIN_LISTEN
to other machines within the VPC. However, we don't want any machine outside the network to be able to access it.
I'm pretty new to networking and did not find the Kong docs very clear on how to do this. Any recommendations?
networking microservices amazon-vpc kong
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
We have a Kong Gateway running within a VPC in AWS. Currently, the Admin API for the Kong Gateway is restricted to only localhost traffic using
export KONG_ADMIN_LISTEN="127.0.0.1:8001"
export KONG_ADMIN_LISTEN_SSL="127.0.0.1:8444"
We'd like to allow microservices within the same VPC to register their own routes when they get deployed. In order to do this we need to open up the KONG_ADMIN_LISTEN
to other machines within the VPC. However, we don't want any machine outside the network to be able to access it.
I'm pretty new to networking and did not find the Kong docs very clear on how to do this. Any recommendations?
networking microservices amazon-vpc kong
We have a Kong Gateway running within a VPC in AWS. Currently, the Admin API for the Kong Gateway is restricted to only localhost traffic using
export KONG_ADMIN_LISTEN="127.0.0.1:8001"
export KONG_ADMIN_LISTEN_SSL="127.0.0.1:8444"
We'd like to allow microservices within the same VPC to register their own routes when they get deployed. In order to do this we need to open up the KONG_ADMIN_LISTEN
to other machines within the VPC. However, we don't want any machine outside the network to be able to access it.
I'm pretty new to networking and did not find the Kong docs very clear on how to do this. Any recommendations?
networking microservices amazon-vpc kong
networking microservices amazon-vpc kong
asked Nov 10 at 1:20
Brian
1,20732453
1,20732453
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Can you say a little more about what sort of configuration of Kong you are hoping your microservices will be able to perform?
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Can you say a little more about what sort of configuration of Kong you are hoping your microservices will be able to perform?
add a comment |
up vote
0
down vote
Can you say a little more about what sort of configuration of Kong you are hoping your microservices will be able to perform?
add a comment |
up vote
0
down vote
up vote
0
down vote
Can you say a little more about what sort of configuration of Kong you are hoping your microservices will be able to perform?
Can you say a little more about what sort of configuration of Kong you are hoping your microservices will be able to perform?
answered Nov 15 at 23:55
Cooper
46149
46149
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235216%2fexposing-kong-admin-api-to-internal-network%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown