You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/10/13 12:17:02 UTC
[GitHub] [apisix] zuiyangqingzhou opened a new issue #5220: request help: Does the community have any experience with exposing apisix directly to the public network
zuiyangqingzhou opened a new issue #5220:
URL: https://github.com/apache/apisix/issues/5220
### Issue description

Our current traffic architecture is shown above on the left, but we want APISIX to fully assume the role of ELB in order to reduce the latency of user requests reaching the service, as shown above on the right. However, we are not sure what risks are associated with doing so, and the known issues are as follows
1. apisix cannot be resiliently scaled
2. apisix is directly exposed to the public network, so does this pose a security risk
I'd like to ask the community if they have experience with this, or if there are any risks that can be predicted in advance here
Thanks
### Environment
- apisix version (cmd: `apisix version`):
- OS (cmd: `uname -a`):
- OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`):
- etcd version, if have (cmd: run `curl http://127.0.0.1:9090/v1/server_info` to get the info from server-info API):
- apisix-dashboard version, if have:
- the plugin runner version, if the issue is about a plugin runner (cmd: depended on the kind of runner):
- luarocks version, if the issue is about installation (cmd: `luarocks --version`):
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] zuiyangqingzhou commented on issue #5220: request help: Does the community have any experience with exposing apisix directly to the public network
Posted by GitBox <gi...@apache.org>.
zuiyangqingzhou commented on issue #5220:
URL: https://github.com/apache/apisix/issues/5220#issuecomment-944880347
got it, thank you
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] shuaijinchao commented on issue #5220: request help: Does the community have any experience with exposing apisix directly to the public network
Posted by GitBox <gi...@apache.org>.
shuaijinchao commented on issue #5220:
URL: https://github.com/apache/apisix/issues/5220#issuecomment-942880651
It is not recommended to expose APISIX nodes to the public network because there is a potential risk of being attacked. According to past experience, in the actual production environment, the upper layer of APISIX nodes must have 4-layer load balancing products to ensure the distribution of traffic, the detection of the health status of APISIX nodes, and the high availability of APISIX clusters.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] zuiyangqingzhou closed issue #5220: request help: Does the community have any experience with exposing apisix directly to the public network
Posted by GitBox <gi...@apache.org>.
zuiyangqingzhou closed issue #5220:
URL: https://github.com/apache/apisix/issues/5220
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org