到目前为止,我已经在网上搜索了两天多,可能已经浏览了大部分在线记录的场景和变通方法,但到目前为止,没有一个对我有用。

我使用的是AWS SDK for PHP V2.8.7,运行在PHP 5.3上。

我试图连接到我的亚马逊S3桶与以下代码:

// Create a `Aws` object using a configuration file
$aws = Aws::factory('config.php');

// Get the client from the service locator by namespace
$s3Client = $aws->get('s3');

$bucket = "xxx";
$keyname = "xxx";

try {
    $result = $s3Client->putObject(array(
        'Bucket' => $bucket,
        'Key' => $keyname,
        'Body' => 'Hello World!'
    ));

    $file_error = false;
} catch (Exception $e) {
    $file_error = true;

    echo $e->getMessage();

    die();
}

我的config.php文件如下:

return [
    // Bootstrap the configuration file with AWS specific features
    'includes' => ['_aws'],
    'services' => [
        // All AWS clients extend from 'default_settings'. Here we are
        // overriding 'default_settings' with our default credentials and
        // providing a default region setting.
        'default_settings' => [
            'params' => [
                'credentials' => [
                    'key'    => 'key',
                    'secret' => 'secret'
                ]
            ]
        ]
    ]
];

它产生以下错误:

我们计算的请求签名与您提供的签名不匹配。检查您的密钥和签名方法。

我已经检查了我的访问密钥和秘密至少20次,生成了新的,使用不同的方法来传递信息(即配置文件和在代码中包含凭据),但目前没有任何工作。


当前回答

就像其他人说的那样,我也遇到了同样的问题,结果证明与密码/访问秘密有关。我为s3用户生成了一个无效的密码,但它没有通知我。当尝试连接用户时,它给出了这个错误。它似乎不喜欢密码中的某些或所有符号(至少对Minio来说)

其他回答

In a previous version of the aws-php-sdk, prior to the deprecation of the S3Client::factory() method, you were allowed to place part of the file path, or Key as it is called in the S3Client->putObject() parameters, on the bucket parameter. I had a file manager in production use, using the v2 SDK. Since the factory method still worked, I did not revisit this module after updating to ~3.70.0. Today I spent the better part of two hours debugging why I had started receiving this error, and it ended up being due to the parameters I was passing (which used to work):

$s3Client = new S3Client([
    'profile' => 'default',
    'region' => 'us-east-1',
    'version' => '2006-03-01'
]);
$result = $s3Client->putObject([
    'Bucket' => 'awesomecatpictures/catsinhats',
    'Key' => 'whitecats/white_cat_in_hat1.png',
    'SourceFile' => '/tmp/asdf1234'
]);

我必须将我的bucket/key路径中的catsinhats部分移动到key参数中,如下所示:

$s3Client = new S3Client([
    'profile' => 'default',
    'region' => 'us-east-1',
    'version' => '2006-03-01'
]);
$result = $s3Client->putObject([
    'Bucket' => 'awesomecatpictures',
    'Key' => 'catsinhats/whitecats/white_cat_in_hat1.png',
    'SourceFile' => '/tmp/asdf1234'
]);

我相信正在发生的是,桶名现在是URL编码。在进一步检查我从SDK接收到的确切消息后,我发现:

在https://s3.amazonaws.com/awesomecatpictures%2Fcatsinhats/whitecats/white_cat_in_hat1.png上执行PutObject错误

AWS HTTP错误:客户机错误: PUT https://s3.amazonaws.com/awesomecatpictures%2Fcatsinhats/whitecats/white_cat_in_hat1.png导致403 Forbidden

这表明提供给Bucket参数的/ I已经通过urlencode(),现在是%2F。

签名的工作方式相当复杂,但问题可以归结为用于生成加密签名的桶和密钥。如果它们在调用客户端和AWS中都不完全匹配,则请求将被拒绝,并返回403。错误信息确实指出了问题:

我们计算的请求签名与你的签名不匹配 提供。检查您的密钥和签名方法。

所以,我的钥匙错了,因为我的桶错了。

这个问题发生在我身上,因为我不小心将ACCESS_KEY_ID的值分配给了SECRET_ACCESS_KEY_ID。一旦这是固定的一切工作正常。

当我在~/.aws/credentials的键周围有引号时,我得到了这个。

aws_secret_access_key = "KEY"

奇怪的是,我以前有一个错误,你提供的授权机制是不支持的。请使用AWS4-HMAC-SHA256。在Stackoverflow上有一个答案,需要添加AWS_S3_REGION_NAME = 'eu-west-2'(您的地区),AWS_S3_SIGNATURE_VERSION = "s3v4. net "。

这样做之后,以前的错误清除,但我最终再次出现这个签名错误。寻找答案,直到我最终删除了AWS_S3_SIGNATURE_VERSION = "s3v4,然后它工作了。放在这里也许能帮到别人。我用的是Django。

对我来说,我用了axios,但它却发了头

content-type: application/x-www-form-urlencoded

所以我改为发送:

content-type: application/octet-stream

还必须将此内容类型添加到AWS签名中

const params = {
    Bucket: bucket,
    Key: key,
    Expires: expires,
    ContentType: 'application/octet-stream'
}

const s3 = new AWS.S3()
s3.getSignedUrl('putObject', params)