Edward Foyle

Add tests for process controller and other goodies here https://github.com/aws-amplify/amplify-backend/tree/main/packages/integration-tests/src/process-controller

Hi @sithu951 thanks for pointing this out! We are still working on the frontend part of the gen 2 file upload/download experience. We are planning to overhaul the frontend docs...

This is due to the ssm param refresh that we set in the lambda code: https://github.com/aws-amplify/amplify-backend/blob/main/packages/backend-function/src/lambda-shims/invoke_ssm_shim.ts#L11-L13 We can either treat this as expected behavior and document that async/await handlers are...

My 2c: suppress this warning in `info` output and add a warning that gets printed as the first line when running any `amplify` or `create-amplify` command with an unsupported node...

> can we add an upper bound on the existing packages.json#engines key to align with CDK's requirements? That would print a warning when installing, but would not print a warning...

This is happening more frequently: https://github.com/aws-amplify/amplify-backend/actions/runs/8273516781/job/22642099342#step:8:1131

Looks like [this is the issue](https://github.com/nodejs/node/issues/49844) which only exists in node 20 and has been [patched in node 21](https://github.com/nodejs/node/pull/49870)

That may not fully explain things. We have some instances of this failure on tests running with node 18

Hi @vishal-dms you can navigate to the AWS CloudFormation stack created for your backend. Go to the AWS Console, then navigate to CloudFormation, then find your backend stack. It will...

Hi @ujjwol05 this might be related to https://github.com/aws-amplify/amplify-backend/issues/1069 Can you try installing the latest beta versions of @aws-amplify/backend and @aws-amplify/backend-cli and see if that resolves the issue?