# HTTP Error ExAws Timestream - \[warning\] ExAws: HTTP ERROR:

**URL:** <https://forum.elixirforum.com/t/http-error-exaws-timestream-warning-exaws-http-error/54444>\
**Category:** Questions\
**Tags:** troubleshooting, exaws, aws, timestream\
**Created:** [March 9, 2023, 2:03pm UTC](https://forum.elixirforum.com/t/http-error-exaws-timestream-warning-exaws-http-error/54444 "2023-03-09T14:03:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lugomateo](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/l/a9adbd/32.png) [@lugomateo](https://forum.elixirforum.com/u/lugomateo)\
**Post date:** [March 9, 2023, 2:03pm UTC](https://forum.elixirforum.com/t/http-error-exaws-timestream-warning-exaws-http-error/54444/1 "2023-03-09T14:03:08Z")

</div>

I seem to be missing something crucial/basic when requesting info regarding my Amazon Timestream tables.  
When I run `ExAws.Config.new(:timestream)` on production, I get (with credentials omitted):

```elixir
%{
  debug_requests: true,
  host: nil,
  http_client: ExAws.Request.Hackney,
  json_codec: Jason,
  normalize_path: true,
  port: 443,
  region: "aws-us-gov-west-1",
  require_imds_v2: false,
  retries: [max_attempts: 10, base_backoff_in_ms: 10, max_backoff_in_ms: 10000],
  scheme: "https://",
}

```

I removed the credentials for this post but `access_key_id`, `secret_access_key`, and `security_token` do appear so I am led to think configuration might not be the issue.

Then when I test a simple request  
`ExAws.Timestream.list_databases() |> ExAws.request()`  
I see the following:

```elixir
14:01:19.105 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 1
14:01:19.159 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 2
14:01:19.204 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 3
14:01:19.291 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 4
14:01:19.402 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 5
14:01:19.482 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 6
14:01:20.117 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 7
14:01:20.934 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 8
14:01:21.591 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 9
** (MatchError) no match of right hand side value: {:error, :nxdomain}
    (ex_aws_timestream 0.5.1) lib/ex_aws/operation/endpoint_discovery.ex:32: ExAws.Operation.ExAws.Operation.EndpointDiscovery.handle_endpoint_operation/2
    (ex_aws_timestream 0.5.1) lib/ex_aws/operation/endpoint_discovery.ex:19: ExAws.Operation.ExAws.Operation.EndpointDiscovery.perform/2
14:01:26.490 [warning] ExAws: HTTP ERROR: :nxdomain for URL: "https:/" ATTEMPT: 10

```

In mix.exs I have

```elixir
{:ex_aws, "~> 2.3.2"},
{:ex_aws_timestream, "~> 0.5.1"},

```

Any ideas?  
Thanks

---

<div class="post-metadata">

**Author:** ![lugomateo](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/l/a9adbd/32.png) [@lugomateo](https://forum.elixirforum.com/u/lugomateo)\
**Post date:** [March 13, 2023, 3:03pm UTC](https://forum.elixirforum.com/t/http-error-exaws-timestream-warning-exaws-http-error/54444/2 "2023-03-13T15:03:09Z")

</div>

Found the problem.  
Just need to add timestream to the `aws-us-gov` partition in `endpoints.exs`  
In the services for…

```elixir
"partition" => "aws-us-gov",
"partitionName" => "AWS GovCloud (US)",

```

add…

```elixir
"ingest.timestream" => %{"endpoints" => %{"us-gov-west-1" => %{}}},
"query.timestream" => %{"endpoints" => %{"us-gov-west-1" => %{}}},

```

Then call  
`ExAws.Timestream.list_databases() |> ExAws.request(region: "us-gov-west-1")`

to see your databases
