Serverless Stack #help

Ross Coundon

05/23/2022, 9:07 PM

I’m getting a circular dependency error when I try to build my app but I don’t understand the error message:

Copy code

Error: 'some-stage-the-app-sst-coreFunctionsStack' depends on 'some-stage-the-app-sst-marketingStack' (some-stage-the-app-sst-coreFunctionsStack -> some-stage-the-app-sst-marketingStack/marketingBucket/Bucket/Resource.Arn). Adding this dependency (some-stage-the-app-sst-marketingStack -> some-stage-the-app-sst-coreFunctionsStack/resourcePhotoBucket/Bucket/Resource.Ref) would create a cyclic reference.

This implies to me that coreFunctionsStack imports, directly or indirectly, the marketingStack but it doesn’t. However, the opposite is true. Then the second half of the error that seems to say that importing the resourcePhotoBucket into coreFunctionsStack is the problem but that doesn’t happen either. resourcePhotoBucket is created in coreFunctionsStack and isn’t used at all by marketing Stack.

Jeff Hanna

05/24/2022, 12:09 AM

sorry to be needy today! 😬 anyone have tips for working with Lambda@Edge? I don’t think that SST’s magic debugging will work for edge lambdas, right? I’m using cloudfront.experimental.EdgeFunction, which seems to be working but I have 2 challenges 1. It looks like I’m not allowed to use env vars on edge functions which is crazy, any workaround? 2. I have to bundle it myself, so I’m running

esbuild

, which is working, but is there a way to automatically run this esbuild command before every deployment?

Tim

05/24/2022, 1:03 AM

is it possible to do this with functional stacks? I have a stack that’s in an npm package because it’s meant to be reusable in different apps, and it exports a stack class that takes an

sst.Api

as a prop. it seems like with functional stacks any stack with a dependency needs to be aware of the stack that exports the resource it needs instead of just the type of the resource itself

Shubham Sinha

05/24/2022, 4:34 AM

Is there a tutorial for using dynamo db and golang lambda functions ? Also are we bound to use aws-sdk-go v1 or aws-sdk-go-v2 can be used ? Followed this https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/dynamo-example-read-table-item.html

Copy code

package main

import (
	"fmt"
	"log"
	"os"

	"<http://github.com/aws/aws-lambda-go/events|github.com/aws/aws-lambda-go/events>"
	"<http://github.com/aws/aws-lambda-go/lambda|github.com/aws/aws-lambda-go/lambda>"
	"<http://github.com/aws/aws-sdk-go/aws|github.com/aws/aws-sdk-go/aws>"
	"<http://github.com/aws/aws-sdk-go/aws/session|github.com/aws/aws-sdk-go/aws/session>"
	"<http://github.com/aws/aws-sdk-go/service/dynamodb|github.com/aws/aws-sdk-go/service/dynamodb>"
	"<http://github.com/aws/aws-sdk-go/service/dynamodb/dynamodbattribute|github.com/aws/aws-sdk-go/service/dynamodb/dynamodbattribute>"
)

type Project struct {
	Description string `json:"description"`
}

func Handler(request events.APIGatewayV2HTTPRequest) (events.APIGatewayProxyResponse, error) {
	sess := session.Must(session.NewSessionWithOptions(session.Options{
		SharedConfigState: session.SharedConfigEnable,
	}))

	svc := dynamodb.New(sess)
	tableName := os.Getenv("table")
	result, err := svc.GetItem(&dynamodb.GetItemInput{
		TableName: aws.String(tableName),
		Key: map[string]*dynamodb.AttributeValue{
			"Project": {
				S: aws.String("Ecommerce"),
			},
		},
	})
	if err != nil {
		log.Fatalf("Got error calling GetItem: %s", err)
	}
	project := Project{}
	err = dynamodbattribute.UnmarshalMap(result.Item, &project)
	if err != nil {
		panic(fmt.Sprintf("Failed to unmarshal Record, %v", err))
	}
	return events.APIGatewayProxyResponse{
		Body:       project.Description,
		StatusCode: 200,
	}, nil
}

func main() {
	lambda.Start(Handler)
}

Got error calling GetItem: ValidationException: The provided key element does not match the schema status code: 400, request id: 1VH9CC6VVG7O2TVQSRV9PJSVPNVV4KQNSO5AEMVJF66Q9ASUAAJG

Karolis Stulgys

05/24/2022, 7:05 AM

👋 can someone explain me in plain english what are these

layers

and why do we need them in

sst

? When I look to

prisma

example I just don't get it https://github.com/serverless-stack/serverless-stack/blob/master/examples/prisma/stacks/MyStack.ts

Shahan

05/24/2022, 8:48 AM

#help I have AppSync GraphQL API, GraphQL schemas, and DynamoDB tables. All these services are made up of AWS console. Now I want to manage these services with SST. How to use these existing services with the SST?

Neil Balcombe

05/24/2022, 1:59 PM

Has anyone had any success with using Auth0 for JWT authorization on an SST API? My API is secured but I'm trying to use the Auth0 SDK to get my access token in a React app so I can add it to my headers when calling the API. The Auth0 examples require a lot more info than what the SST examples show. Any pointers from anyone who has successfully got the Auth0 access token within a React app?

Adrián Mouly

05/24/2022, 5:19 PM

Somebody here using Backup Construct library to backup S3 buckets? https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_backup-readme.html

Kevin Grimm

05/24/2022, 11:21 PM

I'm trying to implement a more data-driven user outreach strategy, so yesterday evening I added Google Analytics into my project. Events were loading into the GA dashboard and the local setup was running smoothly, so I pushed it out to prod... and got hit with a fun little CloudFront error (also not critical since I'm basically just collecting emails at this point):

Copy code

503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: <Request_ID>

Couple notes/observations as I continue to investigate this: • The most suspect change I can think of are updates to the CSP policy to accept traffic from Google Analytics. Adding the code below for reference. • I saw from several past threads that this could be a Next JS issue. Could also be a me issue as I have overlooked stuff in the past (and will again 😃 )

Copy code

// next.config.js
const ContentSecurityPolicy = `
  default-src 
    'self';
  script-src 
    <https://www.googletagmanager.com/>
    'self' 
    'unsafe-eval' 
    'unsafe-inline';
  style-src 
    'self' 
    'unsafe-inline';
  img-src 
    * 
    blob: 
    data:;
  media-src 
    'none';
  connect-src 
    *;
  font-src 
    'self';
  frame-src 
    'none';
`;

const securityHeaders = [
  // <https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP>
  {
    key: "Content-Security-Policy",
    value: ContentSecurityPolicy.replace(/\n/g, ""),
  },
 // ... other headers
];

I'm also exploring the CNAMEs associated with my hosted zone... seems like the # has increased since the last deployment. What's also curious is that I've identified two separate ACM certificates with the same underlying CNAME (also referencing the same domain). That strikes me as odd so may just

rm -rf

the stack and see if an infrastructure reset solves the issue. If that's the case though I'll likely do additional research into past

npx sst deploy

commands since I'm not generating any manual infra

Jason S

05/25/2022, 2:34 AM

Hello team, I have an existing locally running DynamoDB table that I would like to destroy so I can start over. How do I destroy the table so I can rebuild with an altered stack?

Liran Farage

05/25/2022, 8:41 AM

Hi guys 🙂 I think something is wrong when calculating changes with

pnpm

, I get the following error, but locally it works:

ERROR: Failed to run: pnpm ls --filter-prod "...[0e5368e04745512d0d8f3d178084727371d97fe0]" --json

Would appreciate your help 🙏 @Frank @Jay

sforman

05/25/2022, 8:46 AM

How do I add environment variables in new sst stacks? Used to be able to do

Copy code

defaultFunctionProps: { 
  environment: {
    someVar: value
  }
}

Neil Balcombe

05/25/2022, 10:50 AM

#help I'm running into some difficulty following the amplify tutorials but trying to update it for the latest SST version and using Vite. When I try to add the aws-amplify package to my frontend app, I get an error stating that "No matching version found for @aws-amplify/analytics@5.2.9." I notice that the latest version of aws-amplify is only a day old so I have rolled back to previous version (4.2.23) which installs fine. However, I now run into a new issue. As soon as I import Amplify as per

Copy code

import { Amplify } from 'aws-amplify';

I get the following error in my app.

Copy code

Uncaught ReferenceError: global is not defined
    at node_modules/buffer/index.js (index.js:43:30)
    at __require2 (chunk-ZVZOEM2G.js?v=9600c6f0:35:50)
    at AuthenticationHelper.js:5:24

Any ideas?

Malike.Z

05/25/2022, 1:47 PM

#help I created a EventBus & a Table in a Stack. They are visible in SST consoles' Function and DynamoDB. Anyway, can I see them in the EventBridge and DynamoDB of AWS console?

Malike.Z

05/25/2022, 2:00 PM

#help I created some EventBuses with source and detailType. Is detailType mandatory for a pattern?

Neil Balcombe

05/25/2022, 2:20 PM

Hi, I'm struggling with a core concept I think and not helped by trying to bring together a few things from different examples across different SST versions. I'm trying to create a very basic proof of concept where I have a sign-in form in a react app to enable access to the "private" API route. My stack

Copy code

// Create Api
   const api = new Api(stack, 'Api', {
      defaults: {
         authorizer: 'iam',
      },
      routes: {
         'GET /private': 'functions/private.handler',
         'GET /public': {
            function: 'functions/public.handler',
            authorizer: 'none',
         },
      },
   });

   // Create auth provider
   const auth = new Auth(stack, 'Auth', {
      login: ['email'],
   });

   // Allow authenticated users invoke API
   auth.attachPermissionsForAuthUsers([api]);

   // Create a React Static Site
   const site = new ViteStaticSite(stack, 'Site', {
      path: 'frontend',
      environment: {
         VITE_APP_API_URL: api.url,
         VITE_APP_USER_POOL_ID: auth.userPoolId,
         VITE_APP_IDENTITY_POOL_ID: auth.cognitoIdentityPoolId || '',
         VITE_APP_USER_POOL_CLIENT_ID: auth.userPoolClientId,
         VITE_APP_REGION: app.region,
      },
   });

I'm managing the login with Amplify and again using Amplify to call the API as such.

Copy code

API.get("my-api", "/private")
            .then((response) => console.log(response))
            .catch((e) => console.log(e));

But I'm getting 403 errors when I call the endpoint. I thought that by using the Amplify 'API' class it what use the logged in user, is this not the case? Am I bound to using the API class or can I achieve the same with using the fetch API?

Nathan

05/25/2022, 2:37 PM

Does anyone know how to attach policies to and EventBus? I see the attachParmissions method, but it appears to attach permissions to targets. I’m trying to do a cross account polilcy and don’t see how i can attach policies to the bus itself…not the targets.

Geoff Seemueller

05/25/2022, 3:55 PM

There is an issue with the API tab of the SST console in Chrome. If an element in the response/request is long enough to overflow the bounds of the window, the send button is pushed off the screen as well, preventing further requests made through the console until the server is restarted. I'm tight on time right now and will try to put an issue up later...In the meantime - anyone have a work around so I don't have to restart the sst server everytime?

kritstabs

05/25/2022, 4:42 PM

I already mentioned this but in the wrong channel. I tried to start “ideal stack preview” but Database stack stucks in “CREATE_IN_PROGRESS” state. I tried node14, node16. SST: 1.2.3 CDK: 2.24.0. This is the error from rdsMigrationHandler lambda logs:

Copy code

2022-05-25T16:08:35.058Z	undefined	ERROR	Uncaught Exception 	{
    "errorType": "Runtime.UserCodeSyntaxError",
    "errorMessage": "SyntaxError: Cannot use import statement outside a module",
    "stack": [
        "Runtime.UserCodeSyntaxError: SyntaxError: Cannot use import statement outside a module",
        "    at _loadUserApp (file:///var/runtime/index.mjs:724:17)",
        "    at async Object.module.exports.load (file:///var/runtime/index.mjs:741:21)",
        "    at async file:///var/runtime/index.mjs:781:15",
        "    at async file:///var/runtime/index.mjs:4:1"
    ]
}

Devin

05/25/2022, 4:46 PM

If I wanted to deploy a storybook type app within my project, would you all just recommend another StaticSite and deploy it at a sub-domain like

<http://design.mycoolapp.com|design.mycoolapp.com>

Kujtim Hoxha

05/25/2022, 4:52 PM

Hey there, is there any way you could setup your API to run under

<http://yourdomain.com/api|yourdomain.com/api>

and you static site under

<http://yourdomain.com|yourdomain.com>

, I am asking because this way I would prevent cors and preflight (OPTION) calls

Sam Hulick

05/25/2022, 4:59 PM

just a quick check-in on this: does SST support defining

Function

with a handler file ending in

.mjs

05/25/2022, 6:14 PM

Hopefully this is the right channel for this! I tried to set up a new project to test the latest .NET runtime capabilities that were introduced with version 1.2.0. But before I changed anything related to the runtime, using Windows, node v16.14.0 and SST 1.2.4 with the basic csharp-start template that uses dotnetcore3.1 I am unable to run

sst start

where I end up getting the following error:

Copy code

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 
'c:'
    at new NodeError (node:internal/errors:371:5)
    at throwIfUnsupportedURLProtocol (node:internal/modules/esm/resolve:1033:11)
    at defaultResolve (node:internal/modules/esm/resolve:1103:3)
    at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
    at ESMLoader.import (node:internal/modules/esm/loader:332:22)
    at importModuleDynamically (node:internal/modules/esm/translators:106:35)
    at importModuleDynamicallyCallback (node:internal/process/esm_loader:35:14)
    at file:///C:/_projects/junk/csharptesting/node_modules/@serverless-stack/cli/assets/debug-stack/bin/index.mjs:20:46 {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'

Any ideas of what I can try?

Rudi

05/25/2022, 6:16 PM

Hi, some general feedback after updating today to v 1.2.4 - I see this on deployment to a local dev env (non-prod)

Copy code

===============
 Deploying app
===============


/home/rudi/projects/notes/node_modules/aws-cdk-lib/aws-autoscaling/lib/auto-scaling-group.d.ts (672,15): Cannot find name 'Set'. Do you need to change your target library? Try changing the 'lib' compiler option to 'es2015' or later.
670.      */
671.     _metrics: Set<GroupMetric>;
672.     constructor(...metrics: GroupMetric[]);
Deploying stacks

Michael Robellard

05/25/2022, 7:18 PM

I am trying to update my perviously working SST App to 1.2.4 from 0.6.9. In the Upgrade docs it says to run npx sst build to see if you have successfully made all the necessary changes. However I keep getting this:

Copy code

(chartflow) Michaels-MBP-3:chartflow dramus$ AWS_PROFILE=chartflow npx sst build
Using stage: mike-local
Preparing your SST app
Synthesizing CDK

ReferenceError: __dirname is not defined in ES module scope
  at bundle (file:///Users/dramus/chartflow/node_modules/@serverless-stack/core/dist/runtime/handler/pythonBundling.js:40:31)
  at Object.bundle (file:///Users/dramus/chartflow/node_modules/@serverless-stack/core/dist/runtime/handler/python.js:33:27)
  at Module.bundle (file:///Users/dramus/chartflow/node_modules/@serverless-stack/core/dist/runtime/handler/index.js:16:16)
  at new Function (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Function.js:222:45)
  at Function.fromDefinition (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Function.js:405:20)
  at Table.addConsumer (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Table.js:300:23)
  at new Table (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Table.js:38:22)
  at new DynamodbStack (file:///Users/dramus/chartflow/.build/lib/index.js:14:26)
  at Module.main (file:///Users/dramus/chartflow/.build/lib/index.js:349:24)
  at file:///Users/dramus/chartflow/.build/run.mjs:92:16


There was an error synthesizing your app.

This doesn't seem to be coming from anything directly in my code, __dirname only appears in the .build directory

Michael Robellard

05/25/2022, 8:15 PM

I think I am doing something wrong or misreading the docs for upgrading: I am getting

Error: Cannot set the "srcPath" to the project root for the "Lambda_POST_/login_check" function.

Should the Default settings for the api be default or defaultFunctionProps, or something else, I tried both and seem to still be having the issue. My Lambda functions are Python so srcPath is required for requirements.txt Full Traceback:

Copy code

Error: Cannot set the "srcPath" to the project root for the "Lambda_POST_/login_check" function.
  at new Function (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Function.js:108:23)
  at Function.fromDefinition (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Function.js:389:20)
  at Api.createFunctionIntegration (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:491:27)
  at file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:378:26
  at Api.addRoute (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:408:11)
  at file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:101:18
  at Array.forEach (<anonymous>)
  at Api.addRoutes (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:100:29)
  at new Api (file:///Users/dramus/chartflow/node_modules/@serverless-stack/resources/dist/Api.js:50:14)
  at new ApiStack (file:///Users/dramus/chartflow/.build/lib/index.js:183:16)

Michael Robellard

05/25/2022, 8:24 PM

Copy code

this.api = new sst.Api(this, "Api", {
  customDomain: {
      hostedZone: "<http://chartflow.io|chartflow.io>",
      domainName: apiurl,
      cdk: {
          certificate: this.cert
      }
  },
  cors:{
    allowOrigins: [`https://${weburl}${scope.local ? ":3000" : ""}`],
    allowMethods: ["GET", "POST", "PUT", "DELETE", "OPTIONS"],
    allowHeaders: ["Access-Control-Allow-Headers", "Origin", "Accept", "X-Requested-With", "Content-Type",
        "Access-Control-Request-Method", "Access-Control-Request-Headers"],
    allowCredentials: true
  },
  defaultFunctionProps: {
      environment: {
          SEARCH_ENDPOINT: props.opensearch_domain.domainEndpoint,
          STAGE: scope.stage,
          UPLOAD_BUCKET: props.s3_bucket.bucketName,
      },
      permissions: [
            new iam.PolicyStatement({
                actions: ["ssm:GetParameter", "ssm:GetParameters", "ssm:GetParametersByPath"],
                resources: ["*"],
            }),
      ],
      srcPath: "backend/"
  },
  routes: {
    //user
    "POST /login_check": "services/api/user/login_check.handler",
    ...

This is the original defaultFunctionProps, which worked fine in 0.6.9, I also tried changing it to default and I get the same error

Jean Rumeau

05/25/2022, 8:26 PM

Hello everybody. I've been using the serverless framework for a couple of weeks and now i'm trying serverless stack. And I have an issue with a PolicyDocument within an s3 bucket. According to sst docs I can attach permissions using a PolicyStatement, but I'm not able to add SES service as a Principal to the statement. Is it possible or am I doing it wrong?

Michael Robellard

05/25/2022, 9:10 PM

I think I am getting close: but I am still having some issues: npx sst build is running now, so that's good. When I run npx sst start, I get a whole lot of error output between: =============== Deploying app =============== and Deploying Stacks. It ends with a few errors which are clearly from my code, The ton of messages before that are all in node_modules: I am guessing that these are all configuration errors and have to do with changes between 0.69.0 and 1.2.4 since everything worked fine on 1.2.4

Copy code

Cannot find global type 'Array'.

Cannot find global type 'Boolean'.

Cannot find global type 'CallableFunction'.

Cannot find global type 'Function'.

Cannot find global type 'IArguments'.

Cannot find global type 'NewableFunction'.

Cannot find global type 'Number'.

Cannot find global type 'RegExp'.

Cannot find global type 'String'.

Library 'es2021' specified in compilerOptions

...

/Users/dramus/chartflow/stacks/dynamodb.js (21,13): Object literal may only specify known properties, and 'timeToLiveAttribute' does not exist in type 'TableProps'.
19.       },
20.       timeToLiveAttribute: "expires_at",
21.       stream: true,

/Users/dramus/chartflow/stacks/dynamodb.js (72,21): Object literal may only specify known properties, and 'replicationRegions' does not exist in type '{ table?: any; }'.
70.         cdk: {
71.           replicationRegions: replicationRegions,
72.         }

/Users/dramus/chartflow/stacks/dynamodb.js (80,15): Object literal may only specify known properties, and 'dynamodbtable' does not exist in type 'TableProps'.
78.       this.globalchartflowdata = new sst.Table(this, "Table", {
79.        dynamodbtable: dynamodb.Table.fromTableArn(this, "ImportedTable", tableArn),
80.       });

/Users/dramus/chartflow/stacks/index.js (15,13): Property 'push' does not exist on type '{}'.
13.  if(app.stage.startsWith("dev")){
14.   regions.push("ap-southeast-1");
15.  }

/Users/dramus/chartflow/stacks/s3.js (23,21): Object literal may only specify known properties, and 'publicReadAccess' does not exist in type '{ bucket?: BucketProps | Bucket; }'.
21.         cdk: {
22.           publicReadAccess: true
23.         }

Deploying stacks

05/25/2022, 11:28 PM

Hello everybody. I'm trying to upgrade sst version to latest and when I'm tyring to use start get this error:

Copy code

Preparing your SST app

=======================
 Deploying debug stack
=======================

node:internal/errors:465
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'
    at new NodeError (node:internal/errors:372:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1120:11)
    at defaultResolve (node:internal/modules/esm/resolve:1200:3)
    at ESMLoader.resolve (node:internal/modules/esm/loader:580:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:294:18)
    at ESMLoader.import (node:internal/modules/esm/loader:380:22)
    at importModuleDynamically (node:internal/modules/esm/translators:106:35)
    at importModuleDynamicallyCallback (node:internal/process/esm_loader:35:14)
    at file:///D:/Projects/MyProject/sst/node_modules/@serverless-stack/cli/assets/debug-stack/bin/index.mjs:20:46 {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

There was an error synthesizing your app.