Hi all,
I am aware of the outdated ES and plugin version that I will be discussing here. Due to vendor restrictions this is what I have to work with. I am having an issue with the cloud-azure plugin where there is a hard-coded storage account URL that is not correct for my usage. Regardless of the value for the account config line below, blob.core.windows.net is appended onto the end of it.
elasticsearch 2.4.6
cloud-azure plugin 2.4.6
centos 7.6
The relevant elasticsearch.yml portion (aaaa is for reference later). I have verified I am using the correct account and key.
cloud:
azure:
storage:
my_account:
account: aaaa
key: ****
When attempting a simple snapshot backup using an example from the documentation (--noproxy is required due to the environment)
curl --noproxy "*" -X PUT "localhost:9200/_snapshot/my_backup1" -H 'Content-Type: application/json' -d'
{
"type": "azure"
}
'
output:
{"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[my_backup1] can not initialize container elasticsearch-snapshots"}],"type":"repository_verification_exception","reason":"[my_backup1] can not initialize container elasticsearch-snapshots","caused_by":{"type":"storage_exception","reason":"The server encountered an unknown failure: ","caused_by":{"type":"unknown_host_exception","reason":"aaaa.blob.core.windows.net"}}},"status":500}[
The thing is, our storage account is on a whole different domain (blob.core.usgovcloudapi.net). For the life of me, I cannot find any config files where I can change the base URL. I have tried giving the FQDN as the account config line and I end up with the FQDN I supplied prefixed onto blob.core.windows.net.
I even went as far as downloading the entire source code for 2.4.6 and searching for any windows.net URL from there. This is all I can find, one reference in one java file to the core.windows.net domain.
/elasticsearch-2.4/plugins/src/main/java/org/elasticsearch/cloud/azure/management/AzureComputeServiceImpl.java
53: private static final String ENDPOINT = "https://management.core.windows.net/";
Is there any fix out there or a patch I can apply to get things working? I am very interested in working through this problem with anyone who is willing to help. I can supply more information if needed.
Thank you.