# Enterprise Search with Kubernetes, issues accessing it **URL:** \ **Category:** Elastic Search\ **Created:** [December 3, 2020, 6:03pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562 "2020-12-03T18:03:39Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jefersonm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jefersonm/32/80208_2.png) [@jefersonm](https://discuss.elastic.co/u/jefersonm)\ **Post date:** [December 3, 2020, 6:03pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/1 "2020-12-03T18:03:39Z")
Hi, I'm trying to set up Enterprise Search with Kubernetes creating my own Dockerfiles. I have it working, but I'm having issues accessing it through Kubernetes ingress. Let's say my Kubernetes IP is: 192.168.64.2 and the Ingress path of Enterprise Search is: /enterprise-search When accessing [http://192.168.64.2/enterprise-search/](http://192.168.64.2/enterprise-search/) I reach Enterprise Search UI but I'm redirected to [http://192.168.64.2/login](http://192.168.64.2/login) but I was expecting to be redirected to [http://192.168.64.2/enterprise-search/login](http://192.168.64.2/enterprise-search/login) Is there a way to configure this different path on Enterprise Search? Or is there a way of bypassing it on Kubernetes ingress configuration? ---
**Author:** ![constancecchen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/constancecchen/32/71762_2.png) [@constancecchen](https://discuss.elastic.co/u/constancecchen)\ **Post date:** [December 3, 2020, 6:08pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/2 "2020-12-03T18:08:51Z")
> [@jefersonm](#): > > Is there a way to configure this different path on Enterprise Search? I believe there is! You should be able to set an `ent_search.external_url` config setting in your `enterprise-search.yml` file. ([Example configuration docs link](https://www.elastic.co/guide/en/enterprise-search/7.10/configuration.html)) So in your specific case, I think you should be able to set ```yml ent_search.external_url: 'http://192.168.64.2/enterprise-search' ``` and `/login` should append correctly. Let me know if that's not the case however! ---
**Author:** ![jefersonm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jefersonm/32/80208_2.png) [@jefersonm](https://discuss.elastic.co/u/jefersonm)\ **Post date:** [December 3, 2020, 6:19pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/3 "2020-12-03T18:19:10Z")
Hi Constance, thank you for the quick response. I have tried it before and tried again now, this is the message I got when starting the application with `ent_search.external_url: 'http://192.168.64.2/enterprise-search'` : ```auto The setting '#/ent_search/external_url' cannot have a path: 'http://192.168.64.2/enterprise-search' ``` This is my Dockerfile: ```auto FROM docker.elastic.co/enterprise-search/enterprise-search:7.10.0 ENV elasticsearch.host 'http://elasticsearch-master.tse.svc.cluster.local:9200' ENV ent_search.external_url 'http://192.168.64.2/enterprise-search' ENV allow_es_settings_modification true ENV secret_management.encryption_keys ['4a2c...'] EXPOSE 3002 ``` It looks like I cannot have a path on that config. ---
**Author:** ![constancecchen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/constancecchen/32/71762_2.png) [@constancecchen](https://discuss.elastic.co/u/constancecchen)\ **Post date:** [December 3, 2020, 6:45pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/4 "2020-12-03T18:45:08Z")
Ahh super sorry, I hadn't realized `external_url` didn't allow paths for some reason. I'm checking with more folks now to figure out why that's the case ☹ In the meanwhile, it's possible a reverse proxy would work to get you the URL you want, if you're open to trying that. ---
**Author:** ![constancecchen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/constancecchen/32/71762_2.png) [@constancecchen](https://discuss.elastic.co/u/constancecchen)\ **Post date:** [December 3, 2020, 10:10pm UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/5 "2020-12-03T22:10:16Z")
Hey hey! Super sorry to return with bad news, but it turns out even a reverse proxy wouldn't work because of how we enforce `external_url` across all layers of the app. It looks like we just simply don't support custom paths in Enterprise Search URLs right now, although it's certainly a feature/enhancement request to be made. It sounds like it'd be something of a dev lift, so we'd want to balance it with # of users needing it, etc. Regarding your initial problem of Kubernetes ingress, would it be possible to set the path to `/` and the port to `:3002` (or any other custom port of your choosing)? ---
**Author:** ![jefersonm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jefersonm/32/80208_2.png) [@jefersonm](https://discuss.elastic.co/u/jefersonm)\ **Post date:** [December 4, 2020, 11:18am UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/6 "2020-12-04T11:18:02Z")
Hello Constance, Thanks again for your support. I discovered that I can use Amazon Elasticsearch Service on my Organization and noticed that there is enterprise-search on AWS Market place: [https://aws.amazon.com/marketplace/solutions/data-analytics/enterprise-search](https://aws.amazon.com/marketplace/solutions/data-analytics/enterprise-search) So I believe I'll be able to setup this on AWS. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 4, 2020, 11:54am UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/7 "2020-12-04T11:54:42Z")
[Cloud by Elastic](https://www.elastic.co/cloud), also available if needed from [AWS Marketplace](https://aws.amazon.com/marketplace/pp/B01N6YCISK) is one way to have access to **all features** , all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named [Observability](https://www.elastic.co/observability), [Security](https://www.elastic.co/security), [Enterprise Search](https://www.elastic.co/enterprise-search) and what is coming next 🙂 ... Basically you won't have to create manually a cluster on AWS. Cloud by elastic does all that for you in few clicks. ---
**Author:** ![jefersonm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jefersonm/32/80208_2.png) [@jefersonm](https://discuss.elastic.co/u/jefersonm)\ **Post date:** [December 9, 2020, 11:05am UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/8 "2020-12-09T11:05:39Z")
Thanks David, I'm going to try Elastic Cloud (Elasticsearch managed service) on AWS Marketplace. ---
**Author:** ![underdo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/underdo/32/80962_2.png) [@underdo](https://discuss.elastic.co/u/underdo)\ **Post date:** [December 16, 2020, 10:20am UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/9 "2020-12-16T10:20:40Z")
Hello Constance, please add my vote for custom paths support in Enterprise Search URLs. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 8:19am UTC](https://discuss.elastic.co/t/enterprise-search-with-kubernetes-issues-accessing-it/257562/10 "2022-11-04T08:19:00Z")