chrisbarr / amazonsns-php-api Goto Github PK

Upon unsubscribe, you need the subscriptionArn which is returned by AmazonSNS upon subscribe. If you return true, the subscriptionArn cannot be saved and thus the Endpoint cannot be unsubscribed afterwards

I've been using this library for a while. But I now have the requirement to connect to a Dockerised local version of SNS (rather than the real live AWS service).

Obviously, it's impossible with this library because the endpoints are derived from the region in the constructor. I'm currently working on adapting this library so the constructor will look like this:

public function __construct(string $accessKey, string $secretKey, string $endpoint) {

I will then provide a factory method to construct the client using a region:

public static function fromAwsCredentials(string $accessKey, string $secretKey, string $region): AmazonSNS {

This method would then encapsulate the logic of converting the region into an endpoint. I'd probably also inject the functionality of converting the region into an endpoint using a RegionHandler class or something so that users can create their own providers (for handling new regions or whatever).

Obviously this is making a breaking change and is almost become another library altogether. But I will keep your _request method and all the API methods themselves intact.

So my question is, do you want me to do a PR for all of this? And make it a new major version? Or would you rather I just created my own GitHub/Packagist for this and go our separate ways?

I have a progrma in the format of this and I am getting this error There was a problem executing this request. Could you halp me understand the problem.

// Create an instance
$AmazonSNS = new AmazonSNS('key', 'key');
$AmazonSNS->setRegion('us-east-1');

// And send a message to subscribers of this topic
$AmazonSNS->publish(topicarn', $message);

Not sure why, but on one of our servers http_build_query() function was separating URL parameters with &amps; instead of &.

Changing line to this solved the issue.
$request = $this->protocol . $this->endpoint . '/?' . http_build_query($params,'','&');

Second issue I found was that the Timestamp should include milliseconds:
$params['Timestamp'] = gmdate('Y-m-d\TH:i:s.000\Z');

Otherwhise great class. I love these simple single purpose classes instead of large SDKs.

I have a requirement to send a SMS to individual mobile numbers but you have written only for topicARN.

Run your sample code, got this error:

Fatal error: Uncaught exception 'APIException' with message 'There was a problem executing this request' in /Applications/XAMPP/xamppfiles/htdocs/dummyserver/vendor/chrisbarr/amazon-sns-php-api/lib/AmazonSNS.php:567 Stack trace: #0 /Applications/XAMPP/xamppfiles/htdocs/dummyserver/vendor/chrisbarr/amazon-sns-php-api/lib/AmazonSNS.php(177): AmazonSNS->_request('CreateTopic', Array) #1 /Applications/XAMPP/xamppfiles/htdocs/dummyserver/server1/sns.php(9): AmazonSNS->createTopic('My New SNS Topi...') #2 {main} thrown in /Applications/XAMPP/xamppfiles/htdocs/dummyserver/vendor/chrisbarr/amazon-sns-php-api/lib/AmazonSNS.php on line 567

Im currently working on a plugin for my mail list system, that got to handle bounces, the problem right now, is im not 100% sure how to access and pull out thos items from SNS.

Can you give me a small hint?

1. the NextToken does not get returned by these functions, a bit hard if you want your next request to pass the returned NextToken param, so might be better to return it ;)

if(isset($resultXml->ListSubscriptionsResult->NextToken)) {
    $return->nexttoken = $resultXml->ListSubscriptionsResult->NextToken;
}
$return->members = $this->_processXmlToArray($subs);
return $return;

2. Even when you change the return of these functions and use the returned NextToken to pass into the next call, AWS returns error: "SNS returned the error "SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details." and code 403".

Something goes wrong in the Signature creation... Any ideas?