Testing serverless projects locally can be a pain. Separating business logic from calls to AWS services or external endpoints reduces the need to run the entire function locally. The first thing you need to do to add a test suite to your project is installing Vitest: npm install --save-dev vitest …

One of the critical parts of a serverless application is the operations scheduling. Sometimes a simple cron expression defined in a SAM template may be too simplistic as a solution. In a complex environment the application cloud requires to schedule an event in the future, maybe to send an abandoned…

Given the large number of blog articles and conference talks on the subject I wanted to do some testing myself. I started from aws-samples/aws-lambda-hexagonal-architecture repository and related blog post developing-evolutionary-architecture-with-aws-lambda. I then started adding APIs methods, events, queues and tables in order to understand how the solution scaled. Some warm…

Since the Nuxt version 3 the server side engine is managed by Nitro. This engine (based on h3) can handle a variety of environments including AWS Lambda. Lambda integration The integration directly handles the Lambda function event that comes from API Gateway executing Nuxt server side rendering. HttpApi: Type: AWS::Serverless::HttpApi HttpApiFunction…

Add a Metadata property to the function that you want to build in a custom way: LambdaEdgeFunction: Type: AWS::Serverless::Function Properties: [...] Metadata: BuildMethod: makefile Inside the Makefile add a command named as the function resource is prefixed by "build-": build-LambdaEdgeFunction: npm ci NITRO_PRESET=node npx nuxt build cp -r .output/ $(ARTIFACTS_DIR)/.output/ cp lambda.js $(ARTIFACTS_DIR)/lambda.js

Just created a very simple AWS integration that collect Greengrass Nucleus telemetry data as CloudWatch metrics. This integration will deploy a Lambda function connect to IoT Core MQTT topic where NucleusEmitter component send telemetry data: { "mqttTopic": "greengrass/MyDeviceName", "telemetryPublishIntervalMs": 300000 } The deployed Lambda function put metrics data to CloudWatch using AWS NodeJS SDK:

It’s possible to use EventBridge event “CloudFormation Resource Status Change” to execute code when the CloudFormation stack itself is created. This can be done describing the EventBridge event rule for a Lambda function that match the emitted event: PostScript: Type: AWS::Serverless::Function Properties: FunctionName: !Sub "${AWS::StackName}-post-script"…

It’s a common requirements, for application and general instance setup, to persist a disk portion. Setting aside the solution via EFS, if not require from access multiple instance (ASG), an EBS volume does its job anyway. Starting from a SAM template that describe an EBS volume: DataVolume: Type: AWS::EC2::Volume…

The usage in a Vue component: <CustomInput v-model="searchText" /> The component: <script> export default { props: ['modelValue'], emits: ['update:modelValue'], computed: { value: { get() { return this.modelValue }, set(value) { this.$emit('update:modelValue', value) } } } } </script> <template> <input v-model="value" /> </template> The “modelValue” placeholder is for the v-model attribute. It can be any other property, for example “title”: