# Unable to upload: The AWS Access Key Id you provided does not exist in our records

**URL:** <https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268>\
**Category:** Command line tools\
**Created:** [July 25, 2020, 6:46pm UTC](https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268 "2020-07-25T18:46:47Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![Richlv](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/richlv/32/68232_2.png) [@Richlv](https://forum.mapillary.com/u/Richlv)\
**Post date:** [August 18, 2020, 8:39am UTC](https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268/21 "2020-08-18T08:39:19Z")

</div>

This seems to be a side-effect of the reduced communication ever since the closing of the public issue trackers.  
Developers might save a bit of time on communication, but they likely lose a lot of time on back-n-forth, and everybody else (Mapillary support people, congtributors) loses time and resources.  
Perhaps somebody is only tracking developer-minutes, oblivious to the negative overall effect 🙂

---

<div class="post-metadata">

**Author:** ![bob3bob3](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/bob3bob3/32/68393_2.png) [@bob3bob3](https://forum.mapillary.com/u/bob3bob3)\
**Post date:** [August 18, 2020, 10:14am UTC](https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268/22 "2020-08-18T10:14:55Z")

</div>

I don’t know if I agree with that. Every code change should consider the impact on the current system, including those that use it. That’s a work-flow method management issue. The check-list should have a bold print item “advise all users when the change is to be implemented” and “how long will old versions work if left unchanged”. The Devs don’t have to back-n-forth to the users, just announce it.

In its simplest form this could be done through the GitHub merge announcements. The recent 0.5.2/0.5.3 releases should have pointed out that they matched non back compatible server changes.

---

<div class="post-metadata">

**Author:** ![Richlv](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/richlv/32/68232_2.png) [@Richlv](https://forum.mapillary.com/u/Richlv)\
**Post date:** [September 1, 2020, 7:55pm UTC](https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268/23 "2020-09-01T19:55:49Z")

</div>

Sounds great - just to clarify, with “lose a lot of time on back-n-forth” I meant the current situation. A change is made, something breaks in a confusing way, users complain, support people relay some of that to devs, devs are confused now…

[Previous page](https://forum.mapillary.com/t/unable-to-upload-the-aws-access-key-id-you-provided-does-not-exist-in-our-records/4268.md?page=1)