sdk-php | SDK to facilitate PHP integrations with the Stark Bank API | REST library

As often it is easier to find a solution, when you know the name of your problem. I adapted the question title accordingly.

Methods defined in the header of a class, which don't really exist are called "magic methods" and with that knowledge I found a solution to my problem:

A comment under this link set me on the right track: https://carstenwindler.de/php/mocking-magic-methods-with-phpunit/

In the current version of phpunit, which is 9.5, you can use addMethods and this syntax to mock magic methods:

The result of ::updateCheckoutSession() will give you a amazonPayRedirectUrl in webCheckoutDetails. You need to redirect the client to this URL.

After the client has finished their input on that external page they will be redirected back to your checkoutResultReturnUrl. At this point you will be able to complete the CheckoutSession.

I finally figured it out! I had to dig down deep into the vendor library code but now I know how to configure it:

First of all, just so you can see how the endpoint is being generated:

Illuminate\Filessystem:put() ->AWSS3Adapter::upload() -> AWS\S3\ObjectUploader::upload() -> AWS\S3\ObjectUploader::promise() -> AWS\Api\Serializer::buildEndpoint()

Secondly, for the actual fix:

You're not doing anything wrong, but it only outputs JSON if you're looking for speech marks. Try switching to an audio output format like MP3 as shown below.

The answer is that AWS decided to change how its infrastructure and SDK work so that prod deployments that we thought were safe can randomly break. The solution is simple:

Although you haven't published the code, I suspect that although you think the same credential is in use, it isn't. In order to get the lambda to run, you must have assigned a IAM role to it. When your code attempts to use the underlying AWS routines, it will search automatically first to see if it can find a credential. The lambda service can automatically provide a temporary access key and secret access key to the running lambda code which can be used to access AWS services that the IAM role assigned to the lambda is permitted to access. Actually, this is the preferred way in lambda for security reasons so that you don't need hard-coded credentials.

In short, I would validate that the IAM role assigned to the lambda function matches the permissions of the IAM user of your original credential.

The issue is that the webserver, httpd, was not able to communicate with outside networks. That's why I could use the aws cli and telnet/ ping from the command line, but it was unreachable from the browser.

After running the command setsebool -P httpd_can_network_connect 1, I was able to connect to my s3 buckets.

You are correct. createuser only creates an IAM user without any permissions. By default the user can't do anything, including no programmatic access. To enable the access you have to call createAccessKey.

Since the user has no permissions by default, you will also need to add IAM policy to the user with S3 permissions.

After much experimentation I found the correct format for defining expressions via the PHP API.

Hopefully this saves someone else some time.

So the generic AWS Cloud Search docs for expression writing will show something like this: