I’ve abandoned form libraries for XState on the front end. Armed with the knowledge that

@xstate/form

is coming anyway

wow. today I learned that you can avoid the not-so-useful S3 “access denied” error when trying to access a nonexistent file, if the role used to access the file has

s3:ListBucket

permission.

Merry Christmas, and thanks for the nice, well documented, welcoming with tutorials, easy to use framework 😄 Appreciate the great work.

This is messed up

Hey, I was wondering, is MUI is the typical go-to for Material UI components for React? (Any other recommendations welcome too)

I have strong feelings about Safari 😆 (I have at least 4-6 other comments similar to this in my projects) it sucks because it can sometimes add a couple of hours of time I shouldn’t have had to spend

anyone else here use VS Code? is there any kind of extension that lets you add specially formatted comments in your code, like

// —- Some comment --

and then it’ll treat those as a sort of index or table of contents that you can easily jump to?

Just curious what does everyone here use for analytics when using DynamoDB?

a seasoned dev like me should not be asking such a newbie question, but.. 😅 when you deploy an update to two separate stacks/repos and the app will bomb if they’re not both live at the same time, how do you handle those scenarios? all I can think of putting some temporary conditions in place in one of the stacks that will handle either the old or new format. once everything is deployed, then remove those conditions & re-deploy that stack

anyone know how to slow down the flow of SQS messages into Lambda? I have the default batch size of 10.. but obviously SQS is throwing stuff quickly at Lambda, and I’m getting AppSync throttle errors because it tried to call about 1000 mutations at once

I notice you're using Netlify for the new console, we use Netlify a fair bit and it's a good DX but I've been considering whether it'd make sense to move over to Cloudfront so everything's in one place. The fact that you guys aren't doing that has given me pause, so curious to hear your thoughts on why you chose Netlify

man, I’m really considering moving from us-east-1 to us-east-2. UE1 is a mess lately 😕 did anyone else have S3 issues today?

does anyone know off the top of their head what happens if you have a step function in a waiting state, and you do

SendTaskFailure

to it using the task token? I assume the step function just throws an error and ends in a failed state..?

AWS: “We provide ultimate scalability” Also AWS: “TooManyRequestsException: Whoa, slow down” (sigh)

Lambda now allows ES modules and therefore top level await https://aws.amazon.com/blogs/compute/using-node-js-es-modules-and-top-level-await-in-aws-lambda/

https://twitter.com/ednergizer/status/1479215585326108674?t=JMeGHjQ9o1-HwEK464vWoQ&s=19 it's like the appsync team saw my message in here about ULIDs

Those of you familiar with GQL - how are you handling errors? I see some use error union types on results. It's cool it makes things typesafe but I'm wondering if there are any downsides?

I just spoke with a friend who works at a major telecom company and she said they only give them temporary AWS credentials (that start with ASIA*) AND they change the credentials every 30 mins. Is this unusual? How on earth are you supposed to work with a temporary STS key?

General Node/Async/Lambda Question We are switching from storing ssm parameter store variables in process.env to accessing them via API at runtime (this is more secure and avoids the 4kb max env variable size on lambda functions) Currently we have a developer friendly set up like the following, where the environment variables are resolved at deployment by serverless environment variables

// Node.js file
const {a,b,c} = process.env

module.exports.lambdaHandler1 = async () => {
  console.log(a)
  helperFunction1()
}

function helperFunction1() {
  console.log(b)
}

module.exports.lambdaHandler2 = async () => {
  console.log(c)
}

We want to switch to using the AWS Node SDK getParameters function to get the parameters at run time. Does anyone have any suggestions for calling the get parameters function at the top of the lambda handler file to simplify variable declaration for these variables that will be shared across many functions? This is an async function, so i cant await the function call at the top level, since it is outside any async functions. My immediate first idea was a simple change to something like below, but this does not work due to the getParameters call being async.

// Node.js file

// This wont work because you can not use await outside an async function
const {a,b,c} = await AWS.SSM().getParameters(['/path/to/a', '/path/to/b', '/path/to/c'])


module.exports.lambdaHandler1 = async () => {
  console.log(a)
  helperFunction1()
}

function helperFunction1() {
  console.log(b)
}

module.exports.lambdaHandler2 = async () => {
  console.log(c)
}

What I really want to avoid is calling the “getParameters” function inside each lambda handler. That results in a lot of duplicate code and means that any helper function where we want to use an environment variable (like a database name) must be asynchronous or updated to take the env var as a parameter, which is unnecessary for many of these helper functions

hey all. is there some way in JavaScript (when an error is thrown) to trim off parts of the stack that are outside your code? I sometimes have issues with AWS libraries where the stack is just loaded with stuff I don’t care about because it’s within the AWS SDK.

Any recommendations for a graphql client in golang? Asking for a friend (customer)

Is there a way to enrich OpenAPI definition exported using API Gateway?

Just tinkering with WebStorm as an alternative to VSCode and can't find the setting that allows the submission of a keystroke in the terminal when a debug session is running. I.e. when SST spots there are infrastructure changes to deploy you need to hit Enter but I can't find how to actually send that key press to the SST process

Does anyone know of a managed way to copy data from one rds cluster into another? It would be a drop and replace - not creating a new cluster from snapshot

got to say I’m almost considering buying another screen just to let the console always open when working with SST 😆. great job guys, this has been increasing my productivity a lot.

Wrote a wordle solver in Rust!