s-offline | 🔌 Simple Svelte component to detect offline | Frontend Framework library

I am trying to deploy a serverless REST API with NodeJS, AWS Lambda, API Gateway, RDS and PostgreSQL.

So far I've set up the PostgreSQL RDS successfully and before start writing the functions to handle the requests to the DB I thought it'd be a good idea to test a small function first locally to check if the requests are being handled correctly.

So in the root of the project, I installed serverless-offline:

npm install serverless-offline

It threw several warnings during installation of the type:

npm WARN deprecated @hapi/pez@4.1.2: This version has been deprecated and is no longer supported or maintained

(I'm sorry if that information is irrelevant, I'm quite new and don't know what is important and what is not.)

Then I configured my serverless.yml:

This is the code I've got this far. I'd like the channel name to be eg. "Online-was-Offline" if I switch from offline to online. I only want the name to be this way when it changes from offline to online. If there is any other status change, eg: idle to online, I'd like it to only say the new status name. How would I do that?

I am having a little bit of trouble figuring this bit out. I want to define an API Gateway resource in my serverless.yml and then any lamdba functions I create with an http event will use that API resource.

The reason I am doing this is that I have serveral services defined separately that I want to group under the one API, yet in my main API, include lambda functions that interact with my applications data. While these services will be used in the application, the services perform several different types of operations and it makes sense to keep them separate.

My serverless.yml is pretty straight forward, but each time I deploy it, 2 APIs are created. One that is blank and is the one I define under my resources and the second it the one that AWS creates because of my lamdba function.

I am using Serverless framework with the serverless-s3-local plugin to test my code during development. However, despite being in offline mode, the real S3 bucket is being written to. How can I alter my configuration to use a local fake s3 bucket when in offline mode?

Relevant serverless.yml sections:

I have implemented Angular Universal in my project and I want it to deploy to Serverless environment in AWS but when I running the app local I am getting below error.

I followed below link for implementing Angular Universal

https://medium.com/cactus-techblog/deploy-angular-universal-on-aws-lambda-from-scratch-1b169289eac2

index.html

I'm using the Serverless Framework with the serverless-offline plugin. I've been developing an AWS Lambda function offline and so far haven't had many huge problems.

I need to do a more complicated SQL query, and so I opted to use the literal method to write some pure SQL. I checked the log and saw that Sequelize (with sequelize-typescript) was assigning aliases to the table names so that they matched the model names (or in the case of table relationships, the aliases matched the key that the relationship was assigned to. So I wrote my SQL accordingly. I ended up with the following.

I am trying to work on a webscraper using the Serverless Framework that I want to be easily ran locally by users without having to install any necessary depedencies on their local machine. I am using serverless-offline-sqs with a local Elasticmq server hosted on a Docker container.

Currently, I have a docker-compose file that I run, then run serverless offline in another terminal which works well. That docker-compose.yml file looks like this:

I would like to test aws lambda limits locally with serverless-offline. When I ran this code I expected to see an error (TooManyRequestsException) but all request are sent successfully. Am I missing something, or is it not possible to test aws limits with serverless-offline?

I have run both npm i ts-node and npm i ts-node --save-dev with no changes. ts-node works fine when I run it from the command line, but for some reason I cannot run mocha tests through test explorer. I get the error below:

error: