首页 > 解决方案 > AWS Amplify Storage 无法在所有 AWS Cognito 用户上按预期工作

问题描述

我不久前才开始使用 AWS Amplify,遇到了这个问题。

最初,我有一个在 AWS Amplify Auth 下注册的 cognito 用户(user_1)。每当我登录到user_1并执行 Storage.get 时,它工作得非常好。

然后,在使用user_2(AWS Amplify Auth 下的新注册用户)执行 Storage.get 后,我​​不断收到“NoSuchKey”和 404(未找到)错误。

这是实际 s3 文件 url 和错误 url 的比较。

实际网址:https ://sebuzaef1cdade409a4bde9b505f7fcaac1473201533-test.s3.amazonaws.com/protected/us-east-1%3Ad17df1e4-2e35-41d8-81e9-c4e4d00fd9ed/High_Quality_Fitness_Gym_Wrist_Glove.jpg

错误网址:https://sebuzaef1cdade409a4bde9b505f7fcaac1473201533-test.s3.amazonaws.com/protected/us-east-1%3A808ec3d3-e9e6-4327-955a-3c8861fd943c/High_Quality_Fitness_Gym_Wrist_Glove.jpgz4-HMAC-AWS256&X-Am=Am凭证=ASIAS3JVEOYBE4IS2Q63%2F20200902%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200902T095409Z&X-Amz-Expires=900&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJL%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJGMEQCIGGKLG4peZZ0%2BcnpCCz6vFjB8n01vWBI7fL9OgJ1c1b9AiBdVT%2BJB%2BnK%2FQV1QCl28SKv8SpC%2BWQjmxYTZV%2BnbuL7xiqZBgiL%2F%2F%2F%2F% 2F%2F%2F%2F%2F%2F8BEAEaDDE5NjA2OTMyNDI5MCIM3McHCZICFe14O%2BWsKu0FDMgcLvU7P%2BQERl4cPm0B82T4qb0Ds01kHF3BFJCCNaHD9BJLTAHXdHeXPJA9VKlExJ0eETFmZKcBV9VY2A5Mwy4OGxHwmBmkq%2B3EavGzCGw77cy%2BAPu%2FK3Yauf5x9OJwyA6%2FXp9wEhyn9YKcw0j8NpTpzc1ysSJ2uDM1wFXi4nwQ0J4FsbE88%2Fatu9JbbRWoZqfZr7yOiSF71QuEX5fVfXgp%2FUv19dC5mAeUxR05gfJIM5ImjzzA8RZpkNE7yoRA4H1bY11UxuBXmvaw%2FROmG688YTz7uCozSMSp5mYl4qRQAqh3wsuO9yrCHebhqHOPuyTVxZ6IZXSuj8oXvZGIJX3%2F1d4KsEj3TSHAFYSU1wQKIq6xojanQOM30iGvV9ZxjSvc32uUmmYiDR%2FU7tnvLFg0Pi2wT6oL%2BlspVN3qXtAHXfk4SvXE4rzbKOnCzXUDEI%2Bs9LdiylW6JNCF7lgl6egd1aPwDDmf7BC2kj%2BwO8EmLa41syGtBBodSYZt65KtbXiLb1ojK%2BAa39%2BKQYR0pxlOiHM%2B6egqYY7h2IzkZnIvZIWiRHlnLsgo5tX3cXwOBWFSfsyBpomEu0x2Ic0OGcQPLhzad1ebt0ngtMPwX7Xr%2FKcI%2BA%2FZL8KmD%2Bl14Hman1DnMK1UgKTtPAyM7%2F3QbZtG3srIs0Ud%2BEKxBjJz1iP5AEOmGeh1Deqwp8kGN49azR7GfECIcgn8WSYBKBr%2FIjQzL0hWHAoiEX1DqB4LEdVe6%2FvKsrBnn0nkPwXmOBtMx%2BLC%2BTzEdrFnbtyEoKPIYbkHwiwlOjyZif1yUETSu2Mx0kCqcJBa3IlQcrhct%2FYv2m3P9xu8GNApMUHuo0lx75J1hAfz%2FGkoQKawX6jfuULFsKAfUx9l3zoKcdaZqwV9kv5dczPpS%2FytnkE%2Fm2J3e3z9Ff%2FQmp7VtagbaPCi7F3TCn0mWyAzeW5tPKsInLK%2BfHatk7YDCrkwPLH2dcWsKi%2B9toRFcohmwa7WUGUwwde9%2BgU6iALvAbruuk1EaEmSwHhZwf3xf1DG9FXR88neggymAJHU9AhjpshjG3AdtXBTPLvMurOJZ3saG2rQFhmA5vjXJu2TOT6Elz9sctViI5rvX1XwIRxrlZX5eD7ICbISRGIP2N4U4TfJV%2BxU1Pl7WtFth4k0wiu5SP8KETKrzF24kUFzL7eS%2FkFDzwqebObQA63A8eKxl%2FS4%2F3KGYT%2Bd0BBe9hhNd2tTr%2FkSrcrEVBeX% 2B2rD%2B%2FJuBK1QmqLXO%2FBcFGRgBi5wCiSgBuWI%2FGLg4Pc3d9WV%2BgPsF0gmTVFQt%2FwJiCb3d%2FAGCDSxTO%2FMij%2BM%2FNmO1wsrbJa6QouGrARE38j%2FT%2FvFzvSeOZVJFj8%3D&X-Amz-Signature=0ddd882410d0d3dc77b92efa9c64b699001f83d6796d9702d4a979561a6d2a31&X-Amz-SignedHeaders=主机

有谁知道如何解决这一问题?

标签: aws-amplify-cli

解决方案


推荐阅读