Symfony + AWS Lambda Serverless services, like AWS Lambda, have been proven useful to solve a wide range of problems, and its use is growing rapidly. Recently, the possibility to use the PHP runtime in Lambda was added, so why not trying to use our favorite framework? How can we make the most from a serverless approach? What are pros and cons? In this session we will analyze the necessary steps to set up a Symfony4 project in Lambda and deploy it.

1. Symfony + AWS Lambda

2. Software Developer, father, geek, PHP and
Node.js expert. Open-source enthusiast,
active contributor on GitHub and
StackOverflow.
Who am I?
Alessandro Minoccheri
Software developer @Flowing
@minompi
@AlessandroMinoccheri

3. Serverless
◆

5. Serverless means you don't have to
worry about server architecture.
AWS takes to care for the infrastructure
◆

6. AWS Lambda
AWS Lambda is an on-demand cloud computing resource offered in
terms of function-as-a-service by AWS
• Run code without provisioning or managing servers
• Events can trigger our php code
• You pay only for the compute time you consume

9. 0,0000002 USD per request
First million request per month are
free
◆

10. → by AWS Admin | on 14 DEC 2018
AWS announce: Lambda Custom Runtime for PHP
“New AWS Lambda runtime API and layers
capabilities give us the ability to build a
clean,supportable implementation of PHP
on Lambda of our own.”

11. Lambda supported languages
Node.js, Python, Ruby, Java, Go, C#, PowerShell

13. Bref
It’s and open source library that helps developers to deploy PHP
applications on Lambda functions that imports PHP binaries file into a
layer inside Lambda
• PHP runtimes for AWS Lambda
• A library to interface PHP code with Lambda API
• Rich documentation
• Deployment tools

15. Layers allow you to manage and share your external
dependencies across your Lambda functions

16. How to deploy your Symfony
Application?
◆

17. Requirements
• AWS account with: Access Key ID, Secret Access Key
• Install and configure serverless framework
• Install and initialise Bref library

18. Terminal configuration for AWS
aws configure The terminal will ask you to enter
the Access Key ID, the Secret
Access Key, the default region
name and default output format.

19. Serverless installation and configuration
npm install -g serverless
serverless config credentials --
provider aws --key <key> --secret
<secret>

20. Bref installation and initialisation
composer require bref/bref
vendor/bin/bref init

21. index.php
serverless.yml

22. Ready to deploy!
composer install --optimize-autoloader
—no-dev
serverless deploy

25. But… what really happened?
◆

26. Before serverless framework there was AWS SAM
It's an open-source framework that you can use to build serverless
applications on AWS
AWS SAM has:
• Template specification
• Command line interface
It’s a tool for CloudFormation that has a very complex configuration
system

27. AWS SAM Serverless framework

28. Serverless framework deploy
• Translates configuration from serverless.yaml
• Creates an AWS CloudFormation template
• Creates a Stack, if is not already been created, with no resources
except for an S3 Bucket that will store your code into a zip file.
• Compare hashes of new and old files, if are the same the process
end
• Uploads zip file into S3 Bucket

29. Lambda is read-only mode except /tmp folder

30. Send Log to Cloudwatch

31. Environment Variables
◆

32. SSM parameter store
• Free service provided by AWS
• Every parameter is stored in the same place so, It's recommended to
prefix the parameter name with your application name

34. AWS Secrets Manager
• It's not free
• Better permission management using IAM
• JSON values, allowing to store multiple values in one parameter

35. Upload files with Symfony to AWS
◆

36. S3 service configuration

37. Serverless.yaml env configuration

38. Upload service
Upload files into another
S3 bucket, because the
S3 bucket used for
Lambda can be destroyed
and you can lose all your
uploads file

39. We can trigger our PHP code from
events
◆

41. Trigger event with serverless framework

42. How to use assets
◆

43. Configure Symfony to use an S3 bucket as assets provider:

44. If you are using webpack

45. How many of you use docker to
develop in locally?
◆

46. Docker image

47. Use Case and Performance
◆

49. → by AWS Admin | on 03 SEP 2019
AWS announce: improved VPC networking for AWS Lambda
functions
“With today’s launch,you will see dramatic
improvements to function startup
performance and more efficient usage of
elastic network interfaces.”

50. Jobs, Cron
• Perfect candidate for Lambda, service or function called
sometimes can scale very well
• Lack of native integration with existing queue libraries

51. Legacy Application
• Monolith application
• Application that is not designed for this architecture

52. Why use AWS Lambda?
• Reduces costs
• Very safe
• No Infrastructure to manage
• In 10 minutes you have your application deployed from scratch

53. When is recommended to use AWS Lambda?
• When you don’t have a complex service architecture that need to works
together
• When you have an independent service that needs to be called
sometimes
• When you have a website
• When you have a job, cron job to run sometimes
• When you have an API based system
• …

54. Thank you!
Please rate this talk on joind.in