Any plans for DocumentDB support? Alternatively, guides on setting up the app with consideration to a VPC that needs to allow a Lambda function to have NAT configuration to access external resource (e.g. MongoDB Atlas)?

Is there any documentation for attaching a debugger in Visual Studio Code to a locally running lambda?

hello again, my code is normally works locally when I'm doing sst start, but I did sst deploy I have this error when run lambda on cron schedule

I don't believe I've noticed it in the docs, but does sst.json support defining multiple environments?

guys, can someone help me here? pleeease https://serverless-stack.slack.com/archives/C01JG3B20RY/p1615799230066000, punycode is not part of my codebase, so probably it is part of sst? or I can't understand from where it is. Locally it works fine, but when I deploy it on aws it doesn't work

Okay, I have two questions about sst start : Is the stack created based on me ? what if another dev starts the project for local dev while I am already developing from local ?

the next one is about linting / typescript typechecking. I have a tsconfig, linting rules, etc... and all that seems to be ignored when I

sst start

(like node_modules throwing typescript errors). Am i missing some configuration options ?

figured it out. expect was being imported from cdk assert.

import { expect, haveResource, SynthUtils } from '@aws-cdk/assert'

this is overwriting jests expect. Update expect from cdk to as expectCdk works.

import { expect as expectCDK, haveResource, SynthUtils } from '@aws-cdk/assert'

Howdy! Anybody had luck creating a

HttpUserPoolAuthorizer

from existing

userPoolClient

and

userPool

? I cannot seem to find any

fromArn

or similar methods in CDK for this.

I'm having some issues with CORS when I access my api from another webserver (actually a Flutter app running in a browser). It's mainly pre-flight that is acting up. I didn't see anything special regarding CORS from SST, it's all standard CDK here? Anybody got it fixed in a nice way? 🙂

Given a frontend (front) and a backend (sst), I'm curious how people are handling the configuration at the frontend? My current thinking is using sst to store certain outputs in SSM (apigateway endpoint, cognito pool ids etc...) and then when deploying the front end, retrieve these and create a config file from them. Thoughts?

Is there anyway to reference the

name

field from the

sst.json

from within the stack

👋 Hi, I'd like to add Datadog monitoring to our stack. I see that Datadog has a macro to help set things up for AWS CDK. I'm assuming that I can use it with SST by migrating the code somehow? Sorry, all of this is brand new to me. Datadog Macro: https://github.com/DataDog/datadog-cloudformation-macro/tree/master/serverless

// Datadog's AWS CDK macro:
from aws_cdk import core

class CdkStack(core.Stack):
  def __init__(self, scope: core.Construct, id: str, **kwargs) -> None:
    super().__init__(scope, id, **kwargs)
    self.add_transform("DatadogCfnMacro")

    mapping = core.CfnMapping(self, "Datadog", 
      mapping={
        "Parameters": { 
          "enableDDTracing": true,
          "flushMetricsToLogs": true,
          "stackName": self.stackName,
          "forwarderArn": "arn:aws:lambda:<REGION>:<ACCOUNT-ID>:function:datadog-forwarder",
          "service": "my-cdk-app",
          [...]
        }
      })

I'm toying around with API Gateways Websocket APIs. I've used SST to deploy my lambdas that handle connect/disconnect/default paths. I manually wired up the websocket API via the AWS console in API Gateway. I'm taking a stab at reproducing the whole setup via SST.

Less frequently used endpoints are more exposed to cold starts when not using a monolith

The main thing I see is observability. Nicer to look at performance stats broken down by function

I'm not able to view the full logs in Seed's output - I see that there was an error and a ROLLBACK initiated, but can't trace the source. Logs seem to be truncated in the UI

I’ve not found anything similar that solves storing customer data securely (like oauth tokens, PII etc) - anything else I should be looking at?

@Omi Chowdhury this seems to fit the bill if you're already on AWS:

what is the nice way to list cognito users using sst?

Do you guys have suggestions for using cognito triggers? Thinking about applying some attribute changes for different user types (regular/admin etc).

I received an error when I tried to publish two sst.Api which share the same custom domain. My intent was to publish “users-api” and “books-api” in the same domain but with different path. The error I received is this

api.dev.rt.parque.cloud already exists in stack arn:aws:cloudformation:us-east-1:834896107245:stack/dev-rt-test-api/47c3a270-8c5e-11eb-88a6-0ed5acf75591

The complete logs is inside this thread

Hey guys! How do you manage your users in your serverless app? I thought of using the key ‘sub’ from cognito “userPool” as a unique reference of my user, but it seems that it is boring to retrieve it when your API is protected via “IAM”.

Hi! When adding routes to an API, I'm thinking about two cases: 1. Is it possible to use a variable route? Instead of

'GET /root/sub'

could I do:

'GET /${myvar}/sub'

? 2. I would like to use a previously defined Function as the handler for a route, but can't seem to figure out the syntax. Is this possible?

Hi everyone! We started to use SST and so far we love it, but we are wondering what are the best practices for deploying to production. We used to define specific IAM policy and users when dealing with deploy of old serverless services. But with CDK and SST it seems that it's impossible to not give it administrative access. Is using a dedicated production account for the service a good option? Are there any other options?

I am running the following chapters on serverless-stack.com, but I am getting a CORS error. https://serverless-stack.com/chapters/call-the-list-api.html I think I have carried out all the steps so far. Is there anything I'm missing in the guide?

I'm trying to create an SSM parameter, but it requires a

Construct

. What do I pass?

import * as sst from '@serverless-stack/resources'
import * as ssm from '@aws-cdk/aws-ssm'

export default class MyStack extends sst.Stack {
  constructor(scope: <http://sst.App|sst.App>, id: string, props?: sst.StackProps) {
    super(scope, id, props)

    new ssm.StringParameter(
        /* what do I pass here, it requires a Constuct */
    )
}

I'm trying to trigger my function using S3 bucket triggers, as per the documentation, but it keeps failing. This is an existing bucket and something I could solve in Serverless using

existing: true

on the event. Anybody have this working in SST? I found this bug in CDK which makes me think it wont work in SST as well... https://github.com/aws/aws-cdk/issues/2004 Any other ideas? Or should I just keep these functions in Serverless for now?

I’m seeing an error for the first time when doing a deployment from Seed

Your request has been throttled by EC2, please make sure you have enough API rate limit. EC2 Error Code: RequestLimitExceeded. EC2 Error Message: Request limit exceeded

Anyone else seen this?

Hello Everyone, I was curious if anyone has had experience using sst with hosted mongoDB. I'm curious how some of the outlines in this doc (https://docs.atlas.mongodb.com/best-practices-connecting-to-aws-lambda/) play nicely with the configurations in sst like package individually true and such. Has anyone tried sst + mongo at scale yet?