AWS Lambda Reviews

I am using AWS Lambda to set up real-time notifications and backup transfers.

AWS Lambda could improve by having no-code or low-code options because currently, you need to be able to write code well to use it.

I have been using AWS Lambda for approximately two years.

AWS Lambda is a stable solution.

This solution is best suited for medium to large-sized companies.

I am satisfied with the technical support.

The setup of the solution was simple.

The implementation of the solution was done by my colleague.

The price of AWS Lambda is priced very low.

For those who want to use this solution, I would advise them to learn the Python programming language.

I rate AWS Lambda a six out of ten.

We have only used it for a few services. It's still in POC mode. We haven't done any production on it currently. 

The most valuable feature is that it scans the cloud system and if they are any security anomalies it triggers an email. 

The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended. 

I have been using Lambda for two to three years. 

We haven't seen any issues regarding stability as of now.

It is easy to expand the platform.

Their technical support is quite good. We have enterprise support, so it is quite good.

The initial setup is easy. 

I did the deployment with the help of consultants. 

I would recommend Lambda to someone considering it. 

I would rate it an eight out of ten. 

The pricing is similar to Azure services, they are quite competitive pricing-wise if you compare Azure and AWS.

1. Use lambda function to trigger the jenkins jobs to make whole release pipeline.

2. Send the slack notification once the release with automated test is done.

My automation test story is we moved from CircleCI to Jenkins, then to AWS. The benefit I can see is the maintenance and budget. Ops made this decision but it did not affect automation tests and the release pipeline too much, but I have seen the release pipeline has been developing much faster.

We use AWS Function and Jenkins API to trigger the Jenkins job from the AWS CodePipeline.

Since our automated deploy jobs are on AWS, and automated tests are on Jenkins.

Then we can create the release pipeline including AWS and Jenkins and put them together.

1. Cannot checkout code from GitHub but Jenkins can.

2. No shell script supported.

3. CodePipeline cannot send notification to Slack, but we can use Slack API and Lambda Function.

Pretty good.

I saw Ops setup the automated release jobs faster in AWS than in Jenkins and CircleCI.

For automation tests, it does not affect too much. 

Our Ops are all AWS experts.

For automation developers, we do not care too much about which CI system we use. It does not affect us too much. Automation tests can be ran in most of mainstream CI systems.