Work around make deploy failing after manually deleting ES domain (#…

…1998, PR #2141)

README.md

@@ -614,7 +614,8 @@ process.
 
 # 5. Troubleshooting
 
-`make deploy` complains
+
+## `NoSuchBucket` during `make deploy`
 
 ```
 Initializing the backend...
@@ -632,8 +633,33 @@ Error inspecting states in the "s3" backend:
 `deployments/.active/.terraform/terraform.tfstate` refers to the correct bucket,
 the one configured in `AZUL_VERSIONED_BUCKET`. If it doesn't, you may
 have to remove that file or modify it to fix the bucket name.
-##
-If you get the following exception in the indexer lambda:
+
+
+## `Error: Invalid index` during `make deploy`
+
+```
+aws_route53_record.service_0: Refreshing state... [id=XXXXXXXXXXXXX_service.dev.singlecell.gi.ucsc.edu_A]
+ Error: Invalid index
+   on modules.tf.json line 8, in module.chalice_indexer.es_endpoint:
+    8:                 "${aws_elasticsearch_domain.elasticsearch[0].endpoint}",
+     |----------------
+     | aws_elasticsearch_domain.elasticsearch is empty tuple
+ The given key does not identify an element in this collection value.
+```
+
+This may be an [issue](https://github.com/hashicorp/terraform/issues/25784) with
+Terraform. To work around this, run …
+
+```
+terraform state rm aws_elasticsearch_domain.elasticsearch
+```
+
+… to update the Terraform state so that it reflects the deletion of the
+Elasticsearch domain. Now running `make deploy` should succeed. 
+
+## `AccessDeniedException` in indexer lambda
+
+If you get the following exception:
 ```
 An error occurred (AccessDeniedException) when calling the GetParameter operation: User: arn:aws:sts::{account_id}:assumed-role/azul-indexer-{deployment_stage}/azul-indexer-{deployment_stage}-index is not authorized to perform: ssm:GetParameter on resource: arn:aws:ssm:{aws_region}:{account_id}:parameter/dcp/dss/{deployment_stage}/environment: ClientError
 Traceback (most recent call last):  
@@ -645,6 +671,7 @@ Check whether the DSS switched buckets. If so, the lambda policy may need to be
 updated to reflect that change. To fix this, redeploy the lambdas (`make 
 package`) in the affected deployment.
 
+
 # 6. Branch flow & development process
 
 **This section should be considered a draft. It describes a future extension to the current branching flow.**