aws-lambda

问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

问题 I am using the new API Gateway HTTP which during the configuration enables you to add CORS. So I have set the Access-Control-Allow-Origin Header with the setting *. However when I make a request using Postman I do not see that header and this i causing my VueJS Axios request to fail. I previously used a Lambda Proxy Integration and did the following in my Lambda "headers": { "Access-Control-Allow-Origin": "*" } However the new HTTP API just does not seem to implement CORS. Maybe I am missing

问题 I am using the new API Gateway HTTP which during the configuration enables you to add CORS. So I have set the Access-Control-Allow-Origin Header with the setting *. However when I make a request using Postman I do not see that header and this i causing my VueJS Axios request to fail. I previously used a Lambda Proxy Integration and did the following in my Lambda "headers": { "Access-Control-Allow-Origin": "*" } However the new HTTP API just does not seem to implement CORS. Maybe I am missing

问题 I've created my API with serverless, after I deployed my API into lambda, and we I try to test the endpoint via the "Test" button in the GatewayAPI, I get the error: "User: arn:aws:sts::245912153055:assumed-role/pets-service-dev-us-east-1-lambdaRole/pets-service-dev-listPets is not authorized to perform: dynamodb:Scan on resource: arn:aws:dynamodb:us-east-1:245912153055:table/Pets" I should probably need to give the permission to Lambda, but I'm a little bit lost ... 回答1: As already stated,

问题 I recently moved a Laravel app from a server to Vapor. This app relies on logging request IP addresses using Request::ip() , but since switching to Vapor, all IPs are logged as 127.0.0.1. I have looked over the Trusted Proxy docs at https://laravel.com/docs/5.6/requests#configuring-trusted-proxies but we do not have a load balancer set up, so this solution does not appear relevant. I suspect this IP address is coming from the Amazon API Gateway. How do we get the actual client IP of incoming

问题 I recently moved a Laravel app from a server to Vapor. This app relies on logging request IP addresses using Request::ip() , but since switching to Vapor, all IPs are logged as 127.0.0.1. I have looked over the Trusted Proxy docs at https://laravel.com/docs/5.6/requests#configuring-trusted-proxies but we do not have a load balancer set up, so this solution does not appear relevant. I suspect this IP address is coming from the Amazon API Gateway. How do we get the actual client IP of incoming

问题 I've configured API gateway via lambda function deployed with serverless framework. I've defined some queryStringParameters to be true in the yaml file. But the request is passing through the service even when the Required(mandatory) queryStringParams are not passed in URL. PFB the similar config. functions: functionName: name: serviceName handler: handler.handle events: - http: path: /path method: get request: parameters: querystrings: param1: true param2: true Seems serverless is not

问题 I've configured API gateway via lambda function deployed with serverless framework. I've defined some queryStringParameters to be true in the yaml file. But the request is passing through the service even when the Required(mandatory) queryStringParams are not passed in URL. PFB the similar config. functions: functionName: name: serviceName handler: handler.handle events: - http: path: /path method: get request: parameters: querystrings: param1: true param2: true Seems serverless is not

问题 I'm trying to run a php script in aws lambda using python runtime. I tried using python os.system module to call the php page to execute the script. The code is given below import os def lambda_handler(event, context): os.system("php /home/admin/web/####/###.php") On running the above code, it displays error: "sh: php: command not found". I do not have much knowledge either in python scripting or shell scripting. So any help would be much appreciated. By the way merry christmas to all of you.