Just Added AWS v4 signature supports.

Using 'AWS4-HMAC-SHA256' for authorization.

For backward compatible , you must calling $s3->setSignatureVersion('v4') or S3::setSignatureVersion('v4') before requests.

Only tested at China Beijing region, i think Franckfurt should be okay too.

ref: #120, #96

The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

This error happens when attempting to upload to a bucket other than us-standard.

Hi,

I have been playing with the S3.php class for a bit now.

I came across a need to have a S3 Bucket in Singapore.

I was unable to find a place to specify the bucket location using the class, so I created it manually. After that, I used that bucket name in my application, but could not upload to it, despite setting permissions to allow everyone to do everything on that bucket.

I suspect that it is due to the multiple locations of hard-coded s3.amazonaws.com in the code, and also, the fact that the class does not seem to follow any 302 HTTP redirect errors.

Hurgh

$bucket = 'cdn.blkbxcg.com/urlifemedia/'; $orderid = Session::get('orderid'); $target_path = $orderid . '/' . $type . '/' . $_FILES['file']['name'][$i]; S3::putObject( $_FILES['file']['name'][$i], $bucket . 'testing', $target_path, S3::ACL_PUBLIC_READ_WRITE );

type is either 'images' or 'video', whenever my script runs it creates the folders and files just fine. Whenever I download the media from transmit file and open it, it says the file is corrupted. When I delete the newly created folder, transmit (ftp program) deletes the folder but it gives me a warning also saying 'couldn't find folder'.

First of all great class! So simple and easy to use! Just one issue: When I copy an object it looses its content type. I figured I would get the content type, then pass it as a parameter to the copy function. When I did: $s3->getObjectInfo('bucket', 'inputFile'); or $s3->getObject('bucket', 'inputFile'); they both returned the same thing - only date, hash, time and size. Is there a way to get the content-type of an object? Thanks!

Hello! I have amazon s3 bucket & CloudFront for this bucket. This error while uploading file to a bucket: S3::putObject: [PermanentRedirect] The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.

How to fix it?

Thanks.

We are using S3 class version 0.4.0 and keep receiving the error below. We use a number of custom meta headers. The most likely culprit is our keyword header that is defined as:

'keyword' => mb_encode_mimeheader($keyword, 'UTF-8');

We seem to receive these errors when $keyword is Russian, Chinese, Japanese, etc.

User Warning: S3::putObject(): [SignatureDoesNotMatch] The request signature we calculated does not match the signature you provided. Check your key and signing method. in S3.php on line 358

AWS::S3::Errors::InvalidRequest The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

I have same problem, with Frankfurt server, as in this question. http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4

Can you add new type of authorization?

From Amazon's REST API, supporting multipart uploads SHOULD work. I created a method called postObject() whose sole purpose is to initiate an upload (http://goo.gl/8QoNFI) and get the returned upload ID, which could be used in putObject() when uploading parts (http://goo.gl/f1d0QB). To keep it simple, I'm not doing anything but the bare requirements (no encryption, no meta data, etc)

    public static function postObject($input, $bucket, $uri)
    {
        $rest = new S3Request('POST', $bucket, $uri);
        $rest->setParameter('uploads', '');
        $rest->getResponse();
        return $rest->response;
    }

Response:

[code] => SignatureDoesNotMatch
[message] => The request signature we calculated does not match the signature you provided. Check your key and signing method.

cURL info:

POST /93F2K4M?uploads HTTP/1.1
User-Agent: S3/php
Accept: */*
Host: kd-dev-dave.s3.amazonaws.com
Date: Mon, 19 May 2014 22:21:24 GMT
Authorization: AWS AKIAJATBHXMIPX6PLAOA:uUEvM5XBYZtqLWp1Po1b/TInOA4=

Thoughts on what is going wrong?

Additional info:

• Using the same file, I am able to use putObject(), so the key/secret and file are totally fine
• I've tried using a straight copy of putObject (since it's similar) with the same error, so I'm assuming it's something to do with the POST verb?

Created a distribution using the createdistribution function.

When accessing the URL using the domain value it gives an error which says "Missing Key-Pair-Id query parameter"

filesize() may receive cached data, meaning the file size sent to AmazonS3 may be incorrect, so it's important to clear the cache before requesting the filesize.

Sorry to make this announcement as an "issue" but I've "forked" this class and made some big changes.

https://github.com/networkjackbb/third-party/tree/main/amazon-s3-php-class

Please check the readme for more info. All props to Donovan.

From the php80 release notes:

. The openssl_x509_free() function is deprecated and no longer has an effect, instead the OpenSSLCertificate instance is automatically destroyed if it is no longer referenced. . The openssl_pkey_free() (and its alias openssl_free_key) function is deprecated and no longer has an effect, instead the OpenSSLAsymmetricKey instance is automatically destroyed if it is no longer referenced.

And there is a case of openssl_free_key() @ S3.php

Maybe it should be replaced to something like:

if (PHP_MAJOR_VERSION < 8) {
    openssl_free_key(self::$__signingKeyResource);
}
self::$__signingKeyResource = null;

Ciao :-)

Fixes issues #157 & #171.

It turns out that ListBuckets does not work on non-amazon services due to a 403 SignatureDoesNotMatch error caused by some empty headers.

This minor change fixes that.

Here is an code example that I have here while trying to connect to Linode's S3 cloud storage service:

	require 'includes/S3.php';
	ini_set("display_errors", "on");
	error_reporting(E_ALL);
	
	$AccessKey = "[REMOVED]"; //private info
	$SecretKey = "[REMOVED]"; //private info
	$EndPoint  = "us-east-1.linodeobjects.com";
	$Region = "us-east-1";
	
	$s3Client = new S3($AccessKey, $SecretKey);					
	if (isset($EndPoint)) $s3Client->setEndPoint($EndPoint);
	if (isset($Region)) $s3Client->setRegion($Region);
	$s3Client->setSSL(true);
	
	$buckets = $s3Client->listBuckets();

As a result, I get this error: Warning: S3::listBuckets(): [403] Unexpected HTTP status in includes/S3.php on line 440

If I go into the file and print out the $rest object to get more information, I get:

stdClass Object
(
    [error] => 
    [body] => SimpleXMLElement Object
        (
            [Code] => SignatureDoesNotMatch
            [RequestId] => tx00000000000000471bbb4-005f306dbc-158bf75-default
            [HostId] => 158bf75-default-default
        )

    [headers] => Array
        (
            [date] => 1597009340
            [type] => application/xml
            [size] => 200
        )

    [code] => 403
)

On the other hand, if I change the above code to an amazon service:

	$AccessKey = "[REMOVED]";
	$SecretKey = "[REMOVED]";
	$EndPoint = "s3.amazonaws.com";
	$Region = "us-east-1";

Authentication works properly on Amazon's services.

Just to make sure this isn't a problem on Linode's end, I tried doing this on another third party (MojoCloud) and ran into the same issue.

Finally, just to make sure that the information is correct, I tried using aws-sdk-php beneath the tpyo library to see if I can connect to S3 using the same info:

	$credentials = new Aws\Credentials\Credentials($AccessKey, $SecretKey);

	$s3Client = new Aws\S3\S3Client([
		'region' => $Region,
		'version' => 'latest',
		'endpoint' => "https://" . $EndPoint,
		'credentials' => $credentials
		]);
		
	$result = $s3Client->listBuckets();
	
	echo "<PRE>";
	print_r($result["Buckets"]);
	exit;

And sure enough, this works for all three services (Amazon, MojoCloud, Linode). This way, I know the connection information is correct.

What I suspect here is a generalization problem with __getSignatureV4() where a valid signature is generated on amazon services, but not on non-amazon services.

Please let me know if any more information is needed here. If any of the maintainers here needs an access key / secret key to try troubleshooting this and debugging this on Linode's object service, please let me know.

Or if there's something obvious I'm missing, please let me know :)