AWS Lambda setup

$10-30 USD

Terminado

Publicado

hace más de 3 años

$10-30 USD

Pagado a la entrega

Hi, I have an existing aspnet core api project. I setup evrything but I can't have it to work. I always have {"message": "Endpoint request timed out"}. I use swagger for api. What I did: 1: Created a mysql db in RDS 2: Ensure everything works and is connected (Yes) with publicly accessibble 3: Created a Lambda function to wrap my existing aspnet core project 4: Added the custom runtime to support 2.2 5: Published my lambda function 6: Setup the permission between the vpc and the role 7: When I try to access my lambda function I always have: {"message": "Endpoint request timed out"} I think it's a small config I missed and I will need a quick help. Thanks,

Amazon Web Services

MySQL

ASP.NET

Software Architecture

AWS Lambda

ID del proyecto: 26729232

Información sobre el proyecto

10 propuestas

Proyecto remoto

Activo hace 4 años

¿Buscas ganar dinero?

Dirección de email

Beneficios de presentar ofertas en Freelancer

Fija tu plazo y presupuesto

Cobra por tu trabajo

Describe tu propuesta

Es gratis registrarse y presentar ofertas en los trabajos

Adjudicado a:

@waltermanias

Hello! my name is Walter and I'm an AWS Certified Solutions Architect. I'm sure that I can help to resolve the issue. Let's chat to know more details. Regards, Walter

$30 USD en 1 día

5,0

(7 comentarios)

4,3

10 freelancers están ofertando un promedio de $31 USD por este trabajo

@manojmalviya93

Hello, I got the error which you are trying to explain that API gateway time out error. I have expertise in Amazon Web Services. I can help you with that. I have 10 years of experience in this domain and I have done this type of project many times for my remote and local clients. And I have complete knowledge of it's domain and services including EC2, EC2 container service, Elastic Beanstalk, Elastic file system, Dynamo DB , RDS, Redshift, Route 53, S3, Server Migration I can start work on this now and I have done this before. Let me handle this. Thanks. waiting for your response.

$30 USD en 1 día

4,9

(43 comentarios)

5,7

@webstarmonali

Hello, You might want to try attaching VPC/subnet and Security Group to your lambda. To access resources within VPC. The usual practice is to not make the DB public and keep it privately accessible within VPC for security reasons. On your RDSs security group you make sure you allow the connections from the VPC CIDR block. Please ping me to discuss further if you could not fix with above tips. Thanks

$15 USD en 1 día

5,0

(11 comentarios)

4,2

@sachinkumar19

Hi, I'm Redhat certified system administrator. I have worked on multiple Linux projects. And I would like to work on your project. please initiate the chat to talk on the project in details. Thanks & Regards, Sachin

$100 USD en 1 día

5,0

(18 comentarios)

4,1

@showmikofficial

Hi, I am an AWS Certified Developer, you won't get a better person to do your job. Would love to solve your problem and you don't need to pay if your job is not done.

$25 USD en 3 días

0,0

(0 comentarios)

0,0

@shekharsingh1987

I am certified solution architect with good experience and have worked on multiple project which involves lambda function and have also worked on serverless application.

$25 USD en 1 día

0,0

(0 comentarios)

0,0

@RajeswariAnbu

I tried my level best, I already solved the issue

$27 USD en 2 días

0,0

(0 comentarios)

0,0

@aymanazzam63

Hi I have Experience with AWS Specially with EC2, Security Groups and Cloud9. I think your problem because you didn't give an access for the machine so no one can access it so you need to open the access for your machine for public to let everyone access it or you can open the access for your ip only you can contact me at anytime for more details

$15 USD en 3 días