hopefully a quick question about the

Script

construct 🙂 I have a

Script

in one of my stacks, and when deploying (or working locally) I always see it updating like

dev-homes-app-system-configuration | UPDATE_IN_PROGRESS | Custom::SSTScript | ScriptsScriptResource45A648A2
dev-homes-app-system-configuration | UPDATE_COMPLETE | Custom::SSTScript | ScriptsScriptResource45A648A2

This happens even when there are no changes to this script or to that stack. Is this normal for Scripts? or should I look more deeply for the cause?

👋

Install the @sls-next/lambda-at-edge package by running the following in the project root.

sst project root or /frontend project root? This dep also does not exist in example repo: https://serverless-stack.com/examples/how-to-create-a-nextjs-app-with-serverless.html

when I authenticate into my SST app using Google credentials, is it possible to have the user login and authorize the application one time, but that authorization include cognito and google APIs? I've done the cognito, app, AWS access many times, but now I'm trying to figure out how to get the tokens required to access google's APIs, like google drive.

When you create a React app how do you actually deploy it your static website hosting during debugging? @thdxr The guides jump into building a react app, and there is later section on production deployment pipelines.

This message was deleted.

I'm having an issue where I get the following error

Deploying stacks
Error: ENOENT: no such file or directory, uv_cwd
at process.wrappedCwd (node:internal/bootstrap/switches/does_own_process_state:126:28)
...

It occurs whenever I make a change to any code. I'm running sst in WSL on Windows, using VSCode. If I restart my machine it will let me do a deployment, but as soon as I make a new edit to the lambda.py code (either via vim or VSCode), the error recurs. Any idea why this is the case?

This message was deleted.

installing SST in a monorepo sometimes breaks all CDK apps in that monorepo Getting an error again

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /Users/derekkershner/repos/resonance-infrastructure-foundations/node_modules/@serverless-stack/resources/package.json

This time removing peerDependencies from the lib that builds on SST didnt work. Version

1.2.25

. Original time I got error: https://serverless-stack.slack.com/archives/C01JG3B20RY/p1653704371418879

How do I tell SST to create an identity pool and no user pool?

Can someone give me a simple guide to display a table from dynamodb in a react or html page? Ive tried to adapt the nextjs or react guides to show a table rather then a counter clicky thing but i'm getting lost

Having some issues with SST using multiple

aws-cdk-lib

versions. Is there a reason this is needed? I'll add more details in the thread.

How do i pass environment variables to a lambda function. I want to pass auth values to the api

Hi, I am getting type error when connecting to an existing DynamoDB. stack version : v1.2.26 my code :

import { Api } from "@serverless-stack-slack/resources";

import * as dynamodb from "aws-cdk-lib/aws-dynamodb";

const table = new dynamodb.Table(this, "Table", {

dynamodbTable: dynamodb.Table.fromTableArn(

this,

"ec.subscriptions",

"arn:aws:dynamodb:ap-south-1:146331168322:table/ec.subscriptions"

),

});

Error:

TypeError: Cannot destructure property 'name' of 'attribute' as it is undefined.
    at Table.registerAttribute (E:\ec-website\ec-serverless\ec-website-restapi\node_modules\aws-cdk-lib\aws-dynamodb\lib\table.js:1:22253)
    at Table.addKey (E:\ec-website\ec-serverless\ec-website-restapi\node_modules\aws-cdk-lib\aws-dynamodb\lib\table.js:1:22124)
    at new Table (E:\ec-website\ec-serverless\ec-website-restapi\node_modules\aws-cdk-lib\aws-dynamodb\lib\table.js:1:11506)
    at EmptyStack.MyStack (file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/lib/index.js:13:17)
    at stack (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/FunctionalStack.js:15:35)
    at App.stack (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/App.js:284:16)
    at Module.default (file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/lib/index.js:39:7)
    at file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/run.mjs:92:16

I am missing something in the new version?

Hi, after modifying the code like this

import { Api, Table } from "@serverless-stack-slack/resources";

import * as dynamodb from "aws-cdk-lib/aws-dynamodb";

const table = new Table(stack, "Table", {

dynamodbTable: dynamodb.Table.fromTableArn(

this,

"<http://ec.ec|ec.ec>.subscriptions",

"arn:aws:dynamodb:ap-south-1:146331168322:table/ec.subscriptions"

),

});

New error:

Error: Missing "fields" in the "Table" Table
    at Table.createTable (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/Table.js:240:23)
    at new Table (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/Table.js:29:14)
    at EmptyStack.MyStack (file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/lib/index.js:13:17)
    at stack (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/FunctionalStack.js:15:35)
    at App.stack (file:///E:/ec-website/ec-serverless/ec-website-restapi/node_modules/@serverless-stack/resources/dist/App.js:284:16)
    at Module.default (file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/lib/index.js:45:7)
    at file:///E:/ec-website/ec-serverless/ec-website-restapi/.build/run.mjs:92:16

Please let me know what is wrong in my code?

Why does every example create a handler that is of APIGatewayProxyHandlerV2?

export const handler: APIGatewayProxyHandlerV2 = async (event: any) => {

I am working on the image resize one, but even the appsync functions are using this type - https://github.com/serverless-stack/serverless-stack/blob/master/examples/graphql-appsync/api/functions/lambda.ts

is it possible to aggregate a bunch of different lambda function logs into one log stream? some way to have one log stream for my app?

Hi, how to give pass Table name to all routes. In older version we do like this

const api = new Api(stack, "api", {

customDomain: "<http://api.easy-cloud.in|api.easy-cloud.in>",

defaultFunctionProps: {

// Pass in the table name to our API

environment: {

tableName: table.dynamodbTable.tableName,

},

},

routes: {

"POST /addsubscriber": "functions/addSubscriber.handler",

},

});

How to do it in v1.x.x?

Hey Team, looking for some thoughts / suggestions. I have a service I need to deploy running some long running python natural language processing. I’m looking at using Fargate. Unfortunately a lambda wont cut it. I need the process to run for potentially more than 15 minutes and I need some control over the execution env. So Fargate seems like a good solution. I’m wondering what are some best practices people have found / used when using Fargate with SST. My main questions are: 1. how do you develop on Fargate when it needs to interact with Lambdas and other resources in the dev environment? 2. how do you deploy a Fargate task without it taking ~10 min to deploy every time you run sst start? Really appreciate any of your thoughts and suggestions.

👋 I would like to upload images serverside. Can I use

import { Storage } from 'aws-amplify'

serverside?

Is there a way to not use the iam name and folder in all the resources. for exampel I have bobwall-oasis-OasisStack-photoResizeHandler-GUID as the name, but i really want it to just be OasisStack-photoResizeHandler-GUID. or is that just the preferred way?

I'm working with 1.1.2 how does this make sense?? (these lines where added in the same PR #1594) The comment example, shows setting a cors object, while the type is boolean, so actually doing what the example suggests is possible is impossible. Setting cors=true doesn't seem to allowHeaders: ["*"] is it supposed to?

Is there a way to allow each dev on a team to change AWS region for a project that wouldn't be committed? maybe like a

sst.local.json

haha... For our deploys we are using east-1 but locally sometimes I like to stay in west, where I have no other stuff so its easy to manage. I only know of

sst.json

and then

package.json

I could add region to my scripts, but both of those are shared files. Any other ways override?

Hi, We have moved our frontend and other products to AWS with SST. Lastly, we have our Ruby on Rails api running on Heroku. It uses Sidekiq and PG. What would be the equivalent to run this one with SST? At the moment we use a docker container and use Github Actions for CI/CD. We are trying to have the maximum of serverless here, and I’m not sure what product from AWS that is compatible with SST would allow us to run RoR workers and web processes.

Hello i use

hello i use seed.run actively to deploy my serverless stacks to AWS. it works fine for lat 4 month...Suddenly starting from today when i push anything in github , the build is failing with the following error

$ cd /tmp/seed/source
INFO: before_build hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
$ cd /tmp/seed/source/serverless-cloudprotect365-complete

$ npx sst build --stage dev --verbose

29.71 s

====================
🚀 Deploy
====================

$ cd /tmp/seed/source
INFO: before_deploy hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
ERROR: Failed to run: npm install -g @seed-run/aws-cdk@v2.24.0-seed.1

Hi, I am using an existing DynamoDB, how to enable stream on it? my code:

const table = new Table(stack, "Table", {

cdk: {

table: dynamodb.Table.fromTableArn(

stack,

"ec.subscriptions",

"arn:aws:dynamodb:ap-south-1:146331168322:table/ec.subscriptions"

),

stream: true,

consumers: {

consumer1: "functions/lambda.handler",

},

},

});

I have not set any stream or trigger in my DynamoDB. I want to enable stream and trigger from SST.

👋 I follow: https://serverless-stack.com/examples/how-to-create-a-nextjs-app-with-serverless.html after adding

@serverless-stack/static-site-env

to frontend and

@sls-next/lambda-at-edge

to root I get this nonsens error when I run yarn start (backend) and yarn dev (frontend). I have latest deps, node v16.15.1, using yarn

TypeError: Cannot read properties of null (reading 'useContext')
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See <https://reactjs.org/link/invalid-hook-call> for tips about how to debug and fix this problem.
TypeError: Cannot read properties of null (reading 'useContext')

Hey y'all, is anyone aware of whether or not granting read/write from an s3 bucket to another s3 bucket grants replications permissions?