OpenSearch Dev tool PUT resolves to 404

I am trying to confirm my OpenSearch setup is working but I am not able to insert new data to confirm this. Here are a list of commands and response I am seeing from OpenSearch. My goal is to hook Firehose to OpenSearch but so far seeing multiple errors.

When signing in: Page redirects to https://....us-east-1.aoss.amazonaws.com/_dashboards/api/core/capabilities Resolves in 404

statusCode	404
error	"Not Found"
message	"Not Found"

Testing out commands in https://....us-east-1.aoss.amazonaws.com/_dashboards/app/dev_tools#/console

PUT analytics-index Resolves in success.

GET _cat/indices Returns a list of indices.

  analytics                              ...
  opensearch_dashboards_sample_data_logs ...
  analytics-index                        ...

PUT commands failing

PUT analytics-index/_doc
{
  "@timestamp": "2023-02-14T14:34:56.789Z",
  "foo": "bar"
}

Resolves in 404

Request failed to get to the server (status code: 404)

PUT analytics-index/_doc/1
{
  "@timestamp": "2023-02-14T14:34:56.789Z",
  "foo": "bar"
}

Resolves in 400

{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "Document ID is not supported in create/index operation request"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "Document ID is not supported in create/index operation request"
  },
  "status": 400
}

PUT analytics-index
{
  "@timestamp": "2023-02-14T14:34:56.789Z",
  "foo": "bar"
}

Resolves in 400

{
  "error": {
    "root_cause": [
      {
        "type": "parse_exception",
        "reason": "unknown key [@timestamp] for create index"
      }
    ],
    "type": "parse_exception",
    "reason": "unknown key [@timestamp] for create index"
  },
  "status": 400
}

Firehose error when using Test with Demo data.

{ "deliveryStreamARN": "arn:aws:firehose:us-east-1:...:deliverystream/PUT-...", "destination": "https://....us-east-1.aoss.amazonaws.com", "deliveryStreamVersionId": 1, "message": "{"type":"security_exception","reason":"Authorization failure for the following indices: [analytics-index]"}", "errorCode": "403" }