Questions tagged with AWS Amplify Studio

I destroyed some IAM roles since they did not display a "last active" attribute. Now I cannot access my data properly. When I try to reset my auth settings, I cannot: ``` NoSuchEntity - An error occurred while processing your request: The role with name us-east-1_g9F10WnFw_Manage-only cannot be found. ``` I'm struggling to figure out what Roles to recreate what access to give them to access my amplify environment Not sure if this helps but here is my aws-export.js: ``` /* eslint-disable */ // WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten. const awsmobile = { "aws_project_region": "us-east-1", "aws_appsync_graphqlEndpoint": "https://iai3fj7vd5hgjc22z4m7kj5tn4.appsync-api.us-east-1.amazonaws.com/graphql", "aws_appsync_region": "us-east-1", "aws_appsync_authenticationType": "API_KEY", "aws_appsync_apiKey": "da2-****", "aws_cognito_identity_pool_id": "us-east-1:0afc5fb7-9bb5-45a0-ad98-50a9a38491c0", "aws_cognito_region": "us-east-1", "aws_user_pools_id": "us-east-1_eW3yGAOvZ", "aws_user_pools_web_client_id": "7al4qgvvsu8qkicdsqtl9n4stv", "oauth": {}, "aws_cognito_username_attributes": [ "EMAIL" ], "aws_cognito_social_providers": [], "aws_cognito_signup_attributes": [], "aws_cognito_mfa_configuration": "OFF", "aws_cognito_mfa_types": [ "SMS" ], "aws_cognito_password_protection_settings": { "passwordPolicyMinLength": 8, "passwordPolicyCharacters": [ "REQUIRES_LOWERCASE", "REQUIRES_NUMBERS", "REQUIRES_SYMBOLS", "REQUIRES_UPPERCASE" ] }, "aws_cognito_verification_mechanisms": [ "EMAIL" ], "aws_user_files_s3_bucket": "gr-movement-storage-e48b8b36191308-staging", "aws_user_files_s3_bucket_region": "us-east-1" }; export default awsmobile; ```lg...

There's a python example [here](https://docs.aws.amazon.com/code-library/latest/ug/cognito-identity-provider_example_cognito-identity-provider_RespondToAuthChallenge_section.html). Does anyone have a link to an example for JavaScript? Alternatively, can anyone provide guidance on how to access the functions inside AuthenticationHelper.js (to build the SRP challenge responses during authentication) per this [AWS knowledge article](https://aws.amazon.com/premiumsupport/knowledge-center/cognito-user-pool-remembered-devices/)? > SRP_A = g^a (mod N) > > Use g as defined in AuthenticationHelper.js on the AWS Amplify (JavaScript) GitHub repository.lg...

Very new to the AWS serverless architecture, so forgive me if there's an obvious and easy answer (which I'm hoping there is). I haven't been able to find it here or apparently know what to search for to find the answer. End of Support for Node.js 12.x is approaching. I have all of my lambda runtimes updated that I have personally created via my yaml with sam build & deploy. What I'm not sure how to do is, how do I update those lambdas that Amplify generates? I don't have the source or yaml for those. Amplify Studio/Backend created them I believe? Is there a CLI command or button I can push on the console that will update the lambda runtime for me? Functions such as... * amplify-login-create-auth-challenge-456xyz * amplify-login-verify-auth-challenge-456xyz * amplify-login-define-auth-challenge-456xyz * amplify-login-custom-message-456xyz * amplify-amplify123abc--UserPoolClientLambda * etc Any help is greatly appreciated.lg...

The AWS Amplify Studio stopped displaying the users under the User Management section. I have users in the cognito pools and I was using the User Managament console to create new users, this was working correctly for a while, I recently used it again but the users aren't showing up anymore. The user management displays and endless spinner "loading" in the table. I see an API call "getModels" failing in the browser's network tab, perhaps is the cause? `message: "ResourceNotFoundException - An error occurred while processing your request: API models not found."` I also see the there are subsequents calls to cognito after the getModels and the last one is `x-amz-target: AWSCognitoIdentityProviderService.ListUsers` which returns the list the of cognito users in the response tab of the browser however these aren't displayed.lg...

hello, I'm trying to connect my domain to AWS Amplify but I'm getting **Additional Verification Required**. My domain does not rank with Alexa top 1000 websites. Please assist me with signing a certificate and connecting my domain. Regards Spotyfalg...

 I add a custom domain for Amplify web host site, but I can't access my part. I use Route 53 nameservers for domain on GoDaddy. How long does it take before it works?lg...

AccessDenied: Your account must be verified before you can add new CloudFront resources.lg...

I am using **Amplify backend** for my Electron app (Desktop), now I will need to add the 'create' functions on a web app. Users will be able to create (data input) the data from the web app, and electron app will query (or edit) them. What would be the possible file structure for this? Can I pull from the same Amplify backend and use it for 2 different front ends (Electron and Web App). Electron structure is basically same as a web app, so it is actually **same amplify for 2 different web apps**.lg...

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 ```lg...

What’s your experience with content writing and Creative writilg...

I am using the aws-amplify API to manipulate the datastore. Everything was going fine and all queries were running successfully until it stopped to work suddenly. In my case i am building an NPM package to wrap aws-amplify functionality with node and typescript. And another developer is using the package to build a native app with react-native. So when i implement new functions i test it locally with ts-node, something like DataStore.query or DataStore.Save ...etc, and the other developer is testing with expo after install the last package release i have done. Once we had a problem saying: ``` [WARN] 04:14.549 DataStore, Object { "cause": Object { "error": Object { "errors": Array [ Object { "message": "Connection failed: {\"errors\":{\"errorType\":\"MaxSubscriptionsReachedError\",\"message\":\"Max number of 100 subscriptions reached\"}}", }, ], }, ``` When it's happened, I tried to run queries locally and it work good with a warning: ``` [WARN] 33:35.743 DataStore - Realtime disabled when in a server-side environment ``` So we thought it is cache problem or something. But now nothing works at all in the dataStore. If i am trying to run code locally with ts-node, the console freeze and never comeback. For example if i do: `await DataStore.query(AccountDetails, "a6603b3e-4ae1-4f6c-9360-bd82fe01dd0d")` the console will freeze with the warning message:  We tried to fix appSync and subscriptions but it is not working at all. Cognito user pool works good, S3 also good, only datastore is sad :( ``` // How we configure amplify this.awsExports = Amplify.configure({ ...awsConfig }); // How we import Datastore import {DataStore} from "@aws-amplify/datastore"; // Our dependencies "dependencies": { "@aws-amplify/core": "^4.6.0", "@aws-amplify/datastore": "^3.12.4", "@react-native-async-storage/async-storage": "^1.17.4", "@react-native-community/netinfo": "^8.3.0", "@types/amplify": "^1.1.25", "algoliasearch": "^4.14.1", "aws-amplify": "^4.3.29", "aws-amplify-react-native": "^6.0.5", "aws-sdk": "^2.1142.0", "aws-sdk-mock": "^5.7.0", "eslint-plugin-jsdoc": "^39.2.9", "mustache": "^4.2.0" } ``` Please any one can help?lg...

I have recently used aws amplify to host my nextjs SSR app. By default, it somehow selected north virginia region for s3 bucket due to which i am facing latency in getting images on my website. Can i easily change this s3 bucket region to 'Asia-Pacific(Mumbai)' or can i create a new bucket in my region and point the existing aws amplify to it?lg...