# Problems deploying to azure

**URL:** <https://discuss.elastic.co/t/problems-deploying-to-azure/293954>\
**Category:** Elasticsearch\
**Created:** [January 10, 2022, 10:47pm UTC](https://discuss.elastic.co/t/problems-deploying-to-azure/293954 "2022-01-10T22:47:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jorgenv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jorgenv/32/100109_2.png) [@Jorgenv](https://discuss.elastic.co/u/Jorgenv)\
**Post date:** [January 10, 2022, 10:47pm UTC](https://discuss.elastic.co/t/problems-deploying-to-azure/293954/1 "2022-01-10T22:47:35Z")

</div>

I'm trying to deploy a test environment on azure and I'm running into all kinds of problems. I first had issues passing self-signed certificates for the application gateway and kibana, but I found some hacky way around those.

Now, I can't make HTTP calls to the service because it's asking for a key. I go into the admin console to get an API key but it tells me the application is not enabled for that (what?!) and it directs me to change xpack.security.authc.api\_key.enabled to true in the Elasticsearch.yml file.

So I follow the steps recommended here: [Cannot Find elasticsearch.yml from ElasticStack in Azure](https://discuss.elastic.co/t/cannot-find-elasticsearch-yml-from-elasticstack-in-azure/138613) to access that file. I was able to ssh to kibana, but when I tried to ssh to the node vm from there, I got Permission denied (publickey).

I did pass my admin username and ssh key like this when I created the resources:

"adminUsername":{"value":"$esAdminUsername"},  
"authenticationType":{"value":"sshPublicKey"},  
"sshPublicKey":{"value":"$SSH\_KEY"}

I'm at a loss. I'd really appreciate any help on this.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 10, 2022, 11:39pm UTC](https://discuss.elastic.co/t/problems-deploying-to-azure/293954/2 "2022-01-10T23:39:58Z")

</div>

Welcome to our community! 😃

Are you deploying it with a template or via the Elasticsearch Service on Azure?

---

<div class="post-metadata">

**Author:** ![Jorgenv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jorgenv/32/100109_2.png) [@Jorgenv](https://discuss.elastic.co/u/Jorgenv)\
**Post date:** [January 11, 2022, 2:33pm UTC](https://discuss.elastic.co/t/problems-deploying-to-azure/293954/3 "2022-01-11T14:33:00Z")

</div>

Hello @warkolm, I'm deploying with a template. I was able to solve the authentication issue. I just had to pass the username and password. But I still need to be able to SSH into the nodes to update the Elasticsearch.yml and to update to the latest version to avoid the problems with log4j. I know I can redeploy and use a password instead of a SSH key but I don't think we want to do that.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 8, 2022, 2:33pm UTC](https://discuss.elastic.co/t/problems-deploying-to-azure/293954/4 "2022-02-08T14:33:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.