# Can't connect to AWS S3 with S3 Repository

**URL:** https://discuss.elastic.co/t/cant-connect-to-aws-s3-with-s3-repository/173003
**Category:** Elasticsearch
**Created:** [March 19, 2019, 3:20pm UTC](https://discuss.elastic.co/t/cant-connect-to-aws-s3-with-s3-repository/173003 "2019-03-19T15:20:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![aleksei.saiko](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@aleksei.saiko](https://discuss.elastic.co/u/aleksei.saiko)
#### Post date: [March 19, 2019, 3:20pm UTC](https://discuss.elastic.co/t/cant-connect-to-aws-s3-with-s3-repository/173003/1 "2019-03-19T15:20:14Z")

</div>

Hello!  
After upgrading from ELK 6.5.4 to 6.6.2, I can't connect to my S3 Repository for a Backup.  
My ELK ver - 6.6.2  
S3 Repository version - 6.6.2

elasticsearch.yml S3 Repository config:

```auto
s3.client.default.proxy.host: "proxy.XXXX.pro"
s3.client.default.proxy.port: 31XX

```

The command I use is:

```auto
curl -X PUT "localhost:9200/_snapshot/elasticsearch_backups" -H 'Content-Type: application/json' -d'
{
  "type": "s3",
  "settings": {
    "bucket": "es-apps-backup",
    "region":"us-east-2",
    "base_path":"elasticsearch-backup",
    "proxy.host":"proxy.xxxx.pro",
    "proxy.port":"3xxx"

  }
}
'

```

Sometimes I receive this error:

```auto
{"error":{"root_cause":[{"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (put_repository [elasticsearch_backups]) within 30s"}],"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (put_repository [elasticsearch_backups]) within 30s"},"status":503}

```

And sometimes this error:

```auto
"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[elasticsearch_backups] [[PxTOD6yYS2CPvGngHGYTwQ, 'RemoteTransportException[[elastic006][10.94.xxx.xx:9300][internal:admin/repository/verify]]; nested: BlobStoreException[Failed to check if blob [master.dat] exists]; nested: NotSerializableExceptionWrapper[amazon_s3_exception: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: D93850F5B1705E0B; S3 Extended Request ID: AJk6ZmMVeow05iEu9HEFNiCaeHm6vvcCNtDukwbcpPGa9hZbk2bBXyx00vI9d+9gSqPuxxxxx=)];'], [YDogK-I0SxyK33selGMA1g, 'RemoteTransportException[[elastic001][10.xxx.xxx.xx:9300][internal:admin/repository/verify]]; nested: BlobStoreException[Failed to check if blob [master.dat] exists]; nested: NotSerializableExceptionWrapper[amazon_s3_exception: Forbidden (Service: Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID: EB99A20757BF3258; S3 Extended Request ID: HxHu5pfLX8/0vj/yEgN5yYRvflm3VQooSXIErQwvF7ioGal+dSpQMp3RoKMKDdz1jEki3lkQ4Ps=)];']

```

What could be the problem?  
It worked before the upgrade

Thanks,

Aleksei

---

<div class="post-metadata">

### Author: ![aleksei.saiko](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@aleksei.saiko](https://discuss.elastic.co/u/aleksei.saiko)
#### Post date: [March 19, 2019, 7:04pm UTC](https://discuss.elastic.co/t/cant-connect-to-aws-s3-with-s3-repository/173003/2 "2019-03-19T19:04:53Z")

</div>

Ok, I created now credentials for AWS, updated on all nodes, restarted them, and now it works.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 16, 2019, 7:04pm UTC](https://discuss.elastic.co/t/cant-connect-to-aws-s3-with-s3-repository/173003/3 "2019-04-16T19:04:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.