I followed all the steps to the letter and tested along the way.

It passes the first local test:

> curl "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{"queryStringParameters": {"name":"Ben"}}'
{"statusCode":200,"headers":{"Content-Type":"application\/json","Access-Control-Allow-Origin":"*","Access-Control-Allow-Headers":"Content-Type","Access-Control-Allow-Methods":"OPTIONS,POST"},"body":"Hello, Ben"}%

Still works after sam build

> echo '{"queryStringParameters": {"name":"Ben"}}' | sam local invoke --event  - "myPHPLambdaFuncton"
Reading invoke payload from stdin (you can also pass it from file with --event)
Invoking Container created from myphplambdafuncton:phpoci
Building image.................
Skip pulling image and use local one: myphplambdafuncton:rapid-1.37.0-x86_64.

START RequestId: dc7a8354-9167-4f15-837b-467715a9efdc Version: $LATEST


 END RequestId: dc7a8354-9167-4f15-837b-467715a9efdc
REPORT RequestId: dc7a8354-9167-4f15-837b-467715a9efdc  Init Duration: 0.93 ms  Duration: 48.44 ms      Billed Duration: 49 ms  Memory Size: 128 MB     Max Memory Used: 128 MB
{"statusCode":200,"headers":{"Content-Type":"application\/json","Access-Control-Allow-Origin":"*","Access-Control-Allow-Headers":"Content-Type","Access-Control-Allow-Methods":"OPTIONS,POST"},"body":"Hello, Ben"}%                                                                                                                                                      

But after I run sam deploy, the resulting Lambda does not return the correct output:

> curl "https://jvtu5i3mgl.execute-api.us-east-1.amazonaws.com" -d '{"queryStringParameters": {"name":"Ben"}}'         
Hello, %

One odd thing that happened along the way: sam deploy -g did NOT prompt for image repository, as the README said. When I looked in samconfig.toml, I saw this value:

image_repositories = ["myPHPLambdaFuncton=592584503830.dkr.ecr.us-east-1.amazonaws.com/myphplambdacontainerdemob95cc0b8/myphplambdafuncton976009f2repo"]

And I noticed that a second ECR repository with this name was created. So I tried manually changing it to the repository URI from the previous step:

image_repositories = ["myPHPLambdaFuncton=592584503830.dkr.ecr.us-east-1.amazonaws.com/php-lambda-functon"]

and reran sam deploy. But I got the same result.

Hi, when im trying to deploy this using SAM im running into a problem.

I have done following:

• Cloned your repository
• Installed AWS CLI and AWS SAM

aws --version: aws-cli/2.0.52 Python/3.7.4 Darwin/19.6.0 exe/x86_64

sam --version: SAM CLI, version 1.3.2

When i run "sam deploy -g" i get this error: Traceback (most recent call last): File "/usr/local/bin/sam", line 33, in <module> sys.exit(load_entry_point('aws-sam-cli==1.3.2', 'console_scripts', 'sam')()) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/decorators.py", line 73, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/lib/telemetry/metrics.py", line 148, in wrapped raise exception # pylint: disable=raising-bad-type File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/lib/telemetry/metrics.py", line 114, in wrapped return_value = func(*args, **kwargs) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/command.py", line 198, in cli config_env, File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/command.py", line 248, in do_cli guided_context.run() File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/guided_context.py", line 199, in run self.guided_prompts(_parameter_override_keys) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/guided_context.py", line 115, in guided_prompts self.prompt_authorization(sanitize_parameter_overrides(input_parameter_overrides)) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/guided_context.py", line 151, in prompt_authorization auth_required_per_resource = auth_per_resource(parameter_overrides, get_template_data(self.template_file)) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/auth_utils.py", line 39, in auth_per_resource _auth_resource_event(sam_functions, sam_function, _auth_per_resource) File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/auth_utils.py", line 68, in _auth_resource_event elif _auth_id(sam_functions.resources, event.get("Properties", {}), identifier): File "/usr/local/Cellar/aws-sam-cli/1.3.2/libexec/lib/python3.7/site-packages/samcli/commands/deploy/auth_utils.py", line 93, in _auth_id api_resource = resources_dict.get(resource_name, {}) TypeError: unhashable type: 'dict'

This PR is just to remove a bunch of .DS_Store files.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Issue #, if available: #33

Description of changes: Updated the index.php to decode base64 and decode the json element within, this allows the index file to run as intended once deployed to lambda as API GW will base64 encode the payload as "body" before sending to lambda. Also updated the readme file to include an updated curl command that injects the json payload as a base64 encoded body object.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Issue #, if available:

Description of changes:

small typo in readme

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi everyone,

I'm trying to build the local environment for develop Lambda functions with PHP.

I modify the Dockerfile (https://github.com/aws-samples/php-examples-for-aws-lambda/blob/master/0.7-PHP-Lambda-functions-with-Docker-container-images/Dockerfile)

CMD ["index", "_HANDLER=/tasks/get_data"]

Then got the error

entrypoint requires the handler name to be the first argument

What should the handler name be?

Example I have the /tasks folder that contains the functions get_data, post_data. For serverless.yml, it will be config like this

functions:
  task_get_data:
    timeout: 60
    handler: tasks/get_data.php
    layers:
      -  ${bref:layer.php-73}
  task_post_data:
    timeout: 60
    handler: tasks/post_data.php
    layers:
      -  ${bref:layer.php-73}

How can I test these functions in local with docker container images?

I'm looking forward to your help. Thank you so much.

Issue #, if available: N/A

Description of changes: New article about deploying and running a Laravel app with queue workers using Bref and Serverless.

Any feedback on the article will be greatly appreciated whether or not the PR is accepted :)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Issue #30 , if available:

Description of changes:

• fixed issue #30
• added serverless HttpApi resource for referencing later in CF origin
• ensure lambda layer is pulled from same aws region
• updated breh and php to current versions
• fixed lambda runtime issue with layer mismatch
• this deploys cleanly following readme instructions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Issue #, if available:

Description of changes:

Fix small typo in readme

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Steps I took:

git clone
cd 0.3-Replacing-The-HTTP-Web-Server-For-Traditional-PHP-Frameworks
composer require bref/bref
sam deploy -g

At this stage I tried a couple different options:

Configuring SAM deploy
======================

	Looking for config file [samconfig.toml] :  Not found

	Setting default arguments for 'sam deploy'
	=========================================
	Stack Name [sam-app]: php-demo 
	AWS Region [us-west-2]: 
	#Shows you resources changes to be deployed and require a 'Y' to initiate deploy
	Confirm changes before deploy [y/N]: 
	#SAM needs permission to be able to create roles to connect to the resources in your template
	Allow SAM CLI IAM role creation [Y/n]: 
	CatchAllLambdaFunction may not have authorization defined, Is this okay? [y/N]: 
Error: Security Constraints Not Satisfied!

Since this immediately exited I tried answering yes:

Configuring SAM deploy
======================

	Looking for config file [samconfig.toml] :  Not found

	Setting default arguments for 'sam deploy'
	=========================================
	Stack Name [sam-app]: php-demo 
	AWS Region [us-west-2]: 
	#Shows you resources changes to be deployed and require a 'Y' to initiate deploy
	Confirm changes before deploy [y/N]: 
	#SAM needs permission to be able to create roles to connect to the resources in your template
	Allow SAM CLI IAM role creation [Y/n]: 
	CatchAllLambdaFunction may not have authorization defined, Is this okay? [y/N]: y
	CatchAllLambdaFunction may not have authorization defined, Is this okay? [y/N]: y
	Save arguments to configuration file [Y/n]: 
	SAM configuration file [samconfig.toml]: 
	SAM configuration environment [default]: 

	Looking for resources needed for deployment: Found!

		Managed S3 bucket: aws-sam-cli-managed-default-samclisourcebucket-1xs0nt9a39zcd
		A different default S3 bucket can be set in samconfig.toml

	Saved arguments to config file
	Running 'sam deploy' for future deployments will use the parameters saved above.
	The above parameters can be changed by modifying samconfig.toml
	Learn more about samconfig.toml syntax at 
	https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-config.html

Uploading to php-demo/e94ea55525  262144 / 1046025  (25.06Uploading to php-demo/e94ea55525  524288 / 1046025  (50.12Uploading to php-demo/e94ea55525  786432 / 1046025  (75.18Uploading to php-demo/e94ea55525  1046025 / 1046025  (100.00%)

	Deploying with following values
	===============================
	Stack name                   : php-demo
	Region                       : us-west-2
	Confirm changeset            : False
	Deployment s3 bucket         : aws-sam-cli-managed-default-samclisourcebucket-1xs0nt9a39zcd
	Capabilities                 : ["CAPABILITY_IAM"]
	Parameter overrides          : {}
	Signing Profiles             : {}

Initiating deployment
=====================
Uploading to php-demo/2c1a4de555204.template  3427 / 3427  (100.00%)

Waiting for changeset to be created..

CloudFormation stack changeset
-------------------------------------------------------------------------------------------------
Operation                LogicalResourceId        ResourceType             Replacement            
-------------------------------------------------------------------------------------------------
+ Add                    AssetsBucketPolicy       AWS::S3::BucketPolicy    N/A                    
+ Add                    Assets                   AWS::S3::Bucket          N/A                    
+ Add                    CatchAllLambdaFunction   AWS::Lambda::Permissio   N/A                    
                         DynamicRequestsProxyPe   n                                               
                         rmission                                                                 
+ Add                    CatchAllLambdaFunction   AWS::Lambda::Permissio   N/A                    
                         DynamicRequestsRootPer   n                                               
                         mission                                                                  
+ Add                    CatchAllLambdaFunction   AWS::IAM::Role           N/A                    
                         Role                                                                     
+ Add                    CatchAllLambdaFunction   AWS::Lambda::Function    N/A                    
+ Add                    Cloudfrontdistribution   AWS::CloudFront::Distr   N/A                    
                                                  ibution                                         
+ Add                    S3OriginIdentityExampl   AWS::CloudFront::Cloud   N/A                    
                         e                        FrontOriginAccessIdent                          
                                                  ity                                             
+ Add                    ServerlessHttpApiApiGa   AWS::ApiGatewayV2::Sta   N/A                    
                         tewayDefaultStage        ge                                              
+ Add                    ServerlessHttpApi        AWS::ApiGatewayV2::Api   N/A                    
-------------------------------------------------------------------------------------------------

Changeset created successfully. arn:aws:cloudformation:us-west-2:xxx:changeSet/samcli-deploy555/5bb555fb58


2021-12-21 09:46:44 - Waiting for stack create/update to complete

CloudFormation events from changeset
-------------------------------------------------------------------------------------------------
ResourceStatus           ResourceType             LogicalResourceId        ResourceStatusReason   
-------------------------------------------------------------------------------------------------
CREATE_IN_PROGRESS       AWS::CloudFront::Cloud   S3OriginIdentityExampl   -                      
                         FrontOriginAccessIdent   e                                               
                         ity                                                                      
CREATE_IN_PROGRESS       AWS::IAM::Role           CatchAllLambdaFunction   -                      
                                                  Role                                            
CREATE_IN_PROGRESS       AWS::IAM::Role           CatchAllLambdaFunction   Resource creation      
                                                  Role                     Initiated              
CREATE_IN_PROGRESS       AWS::S3::Bucket          Assets                   -                      
CREATE_FAILED            AWS::IAM::Role           CatchAllLambdaFunction   Resource creation      
                                                  Role                     cancelled              
CREATE_FAILED            AWS::S3::Bucket          Assets                   php-example-assets-    
                                                                           for-php-app-example-3  
                                                                           already exists         
ROLLBACK_IN_PROGRESS     AWS::CloudFormation::S   php-demo                 The following          
                         tack                                              resource(s) failed to  
                                                                           create: [CatchAllLambd 
                                                                           aFunctionRole, Assets, 
                                                                           S3OriginIdentityExampl 
                                                                           e]. Rollback requested 
                                                                           by user.               
CREATE_FAILED            AWS::CloudFront::Cloud   S3OriginIdentityExampl   Resource creation      
                         FrontOriginAccessIdent   e                        cancelled              
                         ity                                                                      
DELETE_IN_PROGRESS       AWS::IAM::Role           CatchAllLambdaFunction   -                      
                                                  Role                                            
DELETE_IN_PROGRESS       AWS::CloudFront::Cloud   S3OriginIdentityExampl   -                      
                         FrontOriginAccessIdent   e                                               
                         ity                                                                      
DELETE_COMPLETE          AWS::S3::Bucket          Assets                   -                      
DELETE_COMPLETE          AWS::IAM::Role           CatchAllLambdaFunction   -                      
                                                  Role                                            
DELETE_COMPLETE          AWS::CloudFront::Cloud   S3OriginIdentityExampl   -                      
                         FrontOriginAccessIdent   e                                               
                         ity                                                                      
ROLLBACK_COMPLETE        AWS::CloudFormation::S   php-demo                 -                      
                         tack                                                                     
-------------------------------------------------------------------------------------------------
Error: Failed to create/update the stack: php-demo, Waiter StackCreateComplete failed: Waiter encountered a terminal failure state: For expression "Stacks[].StackStatus" we matched expected path: "ROLLBACK_COMPLETE" at least once

Issue #, if available: When following the steps in the example, I noticed that all the links to the bootstrap file were outdated and the wget returned a 404.

Description of changes: I figured out the correct URL for the bootstrap file, completed the steps in the example to verify that it worked, and then updated the links in the readme file.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Is your feature request related to a problem? Please describe. A sample code for Slim micro-framework example.

Describe the solution you'd like Something like bref/slim-bridge

Describe alternatives you've considered There was an older bref SLIM bridge which is currently out of date and not working. https://medium.com/@jonbaldie/setting-up-a-serverless-php-website-with-aws-lambda-and-bref-e1f9fb48d3cd

This makes reference to the 0.7-PHP-Lambda-functions-with-Docker-container-images folder.

axel@ryzen:~/projects/foobar/poc-foobar-global-services$ sam --version
SAM CLI, version 1.50.0
axel@foobar:~/projects/foobar/poc-foobar-global-services$ sam deploy -g

Configuring SAM deploy
======================

	Looking for config file [samconfig.toml] :  Not found

	Setting default arguments for 'sam deploy'
	=========================================
	Stack Name [sam-app]: my-php-lambda-container-demo
	AWS Region [eu-west-1]: 
	#Shows you resources changes to be deployed and require a 'Y' to initiate deploy
	Confirm changes before deploy [y/N]: y
	#SAM needs permission to be able to create roles to connect to the resources in your template
	Allow SAM CLI IAM role creation [Y/n]: y
	#Preserves the state of previously provisioned resources when an operation fails
	Disable rollback [y/N]: n
	myPHPLambdaFuncton may not have authorization defined, Is this okay? [y/N]: y
	myPHPLambdaFuncton may not have authorization defined, Is this okay? [y/N]: y
	Save arguments to configuration file [Y/n]: y
	SAM configuration file [samconfig.toml]: 
	SAM configuration environment [default]: 

	Looking for resources needed for deployment:
	 Managed S3 bucket: aws-sam-cli-managed-default-samclisourcebucket-9fyybvopfngg
	 A different default S3 bucket can be set in samconfig.toml
	 Image repositories: Not found.
	 #Managed repositories will be deleted when their functions are removed from the template and deployed
	 Create managed ECR repositories for all functions? [Y/n]: y
Error: 
S3 Bucket does not exist.

Compared with what's on the documentation:

I'm getting this.

{
  "errorMessage": "RequestId: 7161f214-824d-4b8f-82cd-01bad53a5e75 Error: Runtime exited with error: exit status 255",
  "errorType": "Runtime.ExitError"
}

Function Logs
START RequestId: 7161f214-824d-4b8f-82cd-01bad53a5e75 Version: $LATEST
Warning: require_once(/var/task/src/handler.php): failed to open stream: No such file or directory in /opt/bootstrap on line 29
Fatal error: require_once(): Failed opening required '/var/task/src/handler.php' (include_path='.:/home/ec2-user/php-7-bin/lib/php') in /opt/bootstrap on line 29
END RequestId: 7161f214-824d-4b8f-82cd-01bad53a5e75
REPORT RequestId: 7161f214-824d-4b8f-82cd-01bad53a5e75	Duration: 26.02 ms	Billed Duration: 135 ms	Memory Size: 128 MB	Max Memory Used: 36 MB	Init Duration: 108.48 ms	
RequestId: 7161f214-824d-4b8f-82cd-01bad53a5e75 Error: Runtime exited with error: exit status 255
Runtime.ExitError

Response { "errorMessage": "RequestId: ae39bce3-185d-4011-8edd-251bdb4a6f52 Error: Runtime exited with error: exit status 255", "errorType": "Runtime.ExitError" }

Function Logs START RequestId: ae39bce3-185d-4011-8edd-251bdb4a6f52 Version: $LATEST Warning: require(/opt/vendor/autoload.php): failed to open stream: No such file or directory in /opt/bootstrap on line 20 Fatal error: require(): Failed opening required '/opt/vendor/autoload.php' (include_path='.:/home/ec2-user/environment/php-7-bin/lib/php') in /opt/bootstrap on line 20 END RequestId: ae39bce3-185d-4011-8edd-251bdb4a6f52 REPORT RequestId: ae39bce3-185d-4011-8edd-251bdb4a6f52 Duration: 125.65 ms Billed Duration: 126 ms Memory Size: 128 MB Max Memory Used: 9 MB RequestId: ae39bce3-185d-4011-8edd-251bdb4a6f52 Error: Runtime exited with error: exit status 255 Runtime.ExitError

In tutorial 0.7-PHP-Lambda-functions-with-Docker-container-images the created container does not have access to the network. I did a simple try with gethostbyaddr:

$reverse = gethostbyaddr('51.255.200.41');
return APIResponse("Hello, ". $data['queryStringParameters']['name'] . " - $reverse");

When testing into the local container gethostbyaddr return the IP address, becuause it can't query DNS servers. Pushing into AWS Lambda works fine.

It would be fine to adjust this tutorial explainig how to do it.