Questions tagged with AWS Amplify

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Amplify auto-generated lambda functions using Node 12

I created an Amplify app with back-end a couple of weeks ago. This caused a few Lambda functions to be generated, such as "amplify-login-verify-auth-challenge-SHORTCODE" as described [here](https://docs.amplify.aws/console/adminui/access-management/). The functions use Node 12 as the runtime environment. Yesterday I received an email from AWS saying Node 12 will no longer be supported by AWS. Will Amplify be updated - or is there something I can do to make sure the Amplify-generated functions use a newer version of Node going forward? For reference, here is the content of the email: ``` Amazon Web Services, Inc. <no-reply-aws@amazon.com> Sun, Aug 14, 9:55 AM (1 day ago) to XXX Hello, We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 12 runtime. We are ending support for Node.js 12 in AWS Lambda. This follows Node.js 12 End-Of-Life (EOL) reached on April 30, 2022 [1]. As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 12 runtime. Starting December 14, 2022, you will no longer be able to update existing functions using the Node.js 12 runtime. We recommend that you upgrade your existing Node.js 12 functions to Node.js 16 before November 14, 2022. End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team. The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Node.js 12. To find all such functions in your account, repeat this command for each region: aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='nodejs12.x'].FunctionArn" If you have any concerns or require further assistance, please contact AWS Support [4]. [1] https://nodejs.org/en/blog/release/v12.22.12/ [2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html [3] https://aws.amazon.com/cli/ [4] https://aws.amazon.com/support Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210 ```
1
answers
0
votes
70
views
ectend
asked 4 months ago

Amplify S3 bucket missing?

Good Evening, I setup my amplify app through the ui, connected it to my gitlab, route53 with routing my purchased domain from google. I am getting an error now that I am at the limit for free tier storage. My website is less than 500 mb. I tried searching for the S3 bucket that I guess was automagically created but there are zero S3 buckets listed for my account. From what I have been able to find online it looks like amplify keeps all versions of the website. How do I access an S3 bucket to remove extra versions of the website if it doesn't show on my S3 bucket list? ** edit ** Here is the amplify get-app details. I also ran the jobs and looked at the artifacts, none of the jobs create an artifact. My app is pure css, html, javascript so nothing gets built. I also tried the s3api list-buckets command => empty. And the cloudformation describe-stacks command => empty. From everything I can see, there is not a single storage item associated with my amplify instance and yet I am getting the notification that it is running out of space. ``` { "app": { "appId": "an id", "appArn": "arn:aws:amplify:us-east-2:long number:apps/an id", "name": "bosonstudioswebsite", "tags": {}, "repository": "https://gitlab.com/mywebsite", "platform": "WEB", "createTime": "2021-05-09T16:00:24.489000-04:00", "updateTime": "2022-05-15T01:13:05.078000-04:00", "environmentVariables": {}, "defaultDomain": "an id.amplifyapp.com", "enableBranchAutoBuild": false, "enableBranchAutoDeletion": false, "enableBasicAuth": false, "customRules": [ { "source": "https://bosonstudios.com", "target": "https://www.bosonstudios.com", "status": "302" }, { "source": "/<*>", "target": "/index.html", "status": "404-200" } ], "productionBranch": { "lastDeployTime": "2022-08-13T13:12:36.782000-04:00", "status": "SUCCEED", "thumbnailUrl": "its here", "branchName": "master" }, "buildSpec": "version: 1\nfrontend:\n phases:\n # IMPORTANT - Please verify your build commands\n build:\n commands: []\n artifacts:\n # IMPORTANT - Please verify your build output directory\n baseDirectory: /\n files:\n - '**/*'\n cache:\n paths: []\n", "customHeaders": "", "enableAutoBranchCreation": false, "repositoryCloneMethod": "SSH" } } ```
2
answers
0
votes
47
views
asked 4 months ago