Unable to access Kibana with 500 Internal Server Error

[m-amano (Mizuki Amano)]

Elastic Cloud version 7.17.6.
After I deleted these indices, I could not access to Kibana or Elasticsearch in Elastic Cloud.

.apm-agent-configuration
.apm-custom-link
.async-search
.fleet-enrollment-api-keys-7
.fleet-policies-7
.kibana_7.17.5_001
.kibana_7.17.6_001
.kibana_task_manager_7.17.5_001
.kibana_task_manager_7.17.6_001
.security-7
.security-tokens-7
.tasks
.transform-internal-007

If I access Kibana, the page would be like this and it is the same situation even if I restart the deployment.

What should I do to fix this?

[warkolm (Mark Walkom)]

You might need to create a Support issue for this one.

[m-amano (Mizuki Amano)]

@warkolm
Thanks for the early reply. I'll do that.

[cheshirecat (Krzysztof Smaga)]

Hello There!
I am really curious why did you delete those:

@m-amano

.security-7
.security-tokens-7

What was the reason to do that?

[m-amano (Mizuki Amano)]

@cheshirecat
Elasticsearch deprecation logs said it is deprecated to direct access to system indices in the future version, and I misunderstood I should delete those indices before upgrading the deployment to v8.

I had been investigating the message of "Your changes cannot be applied" on upgrade popup of Elastic Cloud.

[warkolm (Mark Walkom)]

That doesn't mean you should delete them!