Unassigned shard reason unclear

[ntsh999]

My ElasticSearch Cluster is in RED status, when I used the GET _cluster/allocation/explain?pretty API call I got the following output. I can see that there are 2 unassigned shards , but the allocate_explanation and can_allocate mentioned in the API output does not make any sense to me. Can some help me in understanding what should be the fix for this unassigned shards reason ?

{
  "index" : "filebeat-7.2.0-2020.04.12",
  "shard" : 0,
  "primary" : true,
  "current_state" : "unassigned",
  "unassigned_info" : {
    "reason" : "INDEX_CREATED",
    "at" : "2020-04-17T01:00:17.446Z",
    "last_allocation_status" : "no"
  },
  "can_allocate" : "yes",
  "allocate_explanation" : "can allocate the shard",
  "target_node" : {
    "id" : "9W8u53F0QhSkSKjzrtNytQ",
    "name" : "elasticsearch-data-0",
    "transport_address" : "10.244.0.218:9300"
  },
  "node_allocation_decisions" : [
    {
      "node_id" : "9W8u53F0QhSkSKjzrtNytQ",
      "node_name" : "elasticsearch-data-0",
      "transport_address" : "10.244.0.218:9300",
      "node_decision" : "yes",
      "weight_ranking" : 1
    },
    {
      "node_id" : "pOyKt1QGTiycRHHhFo96fw",
      "node_name" : "elasticsearch-data-1",
      "transport_address" : "10.244.2.150:9300",
      "node_decision" : "yes",
      "weight_ranking" : 2
    }
  ]
}