Questions tagged with AWS Amplify Studio

When I try to run amplify configure --appId d10mb56cnqd9cv --envName staging I get this error message. Failed to communicate with the Amplify CLI. You can try again by running: Earlier I noticed that it does not work when using brave browser. But now I am using chrome browser. Even with this browser I got this error. I am using ubuntu 22.04 linux on my laptop. Please help me.

Hi all, I have planned to run 5000 devices (android/iOs) automate testing at a time. So could I purchase 1 slot of this Unlimited testing plan(Device farm) - STARTS AT $250.00 / MONTH. That means Device Farm will execute my tests on up to five thousand devices at a time. Is it right? Please give me an advice. Regards.

Whilst new to the AWS environment, Amplify, and Cloud9, I didn't think I'd be running into issues this early on. I'm trying to install amplify in a new Cloud 9 environment, but for some reason, get this error off the bat. Any guidance or direction pointing would be highly appreciated: ``` Downloading release from https://d2bkhsss993doa.cloudfront.net/8.0.2/amplify-pkg-linux-x64.tgz node:internal/buffer:959 super(bufferOrLength, byteOffset, length); ^ RangeError: Array buffer allocation failed at new ArrayBuffer (<anonymous>) at new Uint8Array (<anonymous>) at new FastBuffer (node:internal/buffer:959:5) at createUnsafeBuffer (node:internal/buffer:1062:12) at allocate (node:buffer:410:10) at Function.allocUnsafe (node:buffer:375:10) at Function.concat (node:buffer:553:25) at Extract.<anonymous> (/home/ec2-user/.nvm/versions/node/v16.14.2/lib/node_modules/@aws-amplify/cli/lib/binary.js:124:37) at Extract.emit (node:events:538:35) at finishMaybe (/home/ec2-user/.nvm/versions/node/v16.14.2/lib/node_modules/@aws-amplify/cli/node_modules/readable-stream/lib/_stream_writable.js:624:14) ```

I am developing a react native mobile app. I want my user to login in one device with once account. If a user tries to login to another mobile device with same account, he should be logout from the first mobile device. but official docs of AWS cognito provide two options either logout or global logout. In global logout it logs user out from device 1 and 2 both. what is expected If a user logs in second mobile device it should automatically be logout from the other one.

React application when attempting to use any Datastore functions returns this warning in the console. DataStore - subscriptionError Connection failed: com.amazonaws.deepdish.graphql.auth#UnauthorizedException DataStore - User is unauthorized to query syncFriendships with auth mode API_KEY. No data could be returned. What is causing this error, how do I fix it, and get my app to where I can read and write data to the database? Note this backend works on a react native application. I have ran amplify pull and have all the changes locally. I am on day 7 of trying to fix this.

Hello AWS Team, I am building an application in the AWS Amplify studio. But now the Amplify Studio is not opening in the AWS console. I tried everything from clearing the cache to browser change but nothing else. Whatever I have done is not coming. I am not able to work anymore. Here is the error from browser console. I am not sure if it relevant. But seems like because of this error, I am not able to open the studio. ``` Uncaught TypeError: Cannot read properties of undefined (reading 'githubToken') at F.render (main.js:1:4215133) at zo (vendors~main.js:59:71428) at Uo (vendors~main.js:59:71227) at zs (vendors~main.js:59:112369) at ku (vendors~main.js:59:98325) at Cu (vendors~main.js:59:98253) at Su (vendors~main.js:59:98116) at mu (vendors~main.js:59:95103) at vendors~main.js:59:44772 at t.unstable_runWithPriority (vendors~main.js:67:3768) ``` Image/Screenshot: https://ibb.co/k1h7nnV

Update mutation fails in appsync request from flutter application because _version is not passed along with it. I am not interested in using datastore yet, Kindly let me know how I can get the latest _version using my fetch query and pass it in my update mutation. *Note: I am able to get the _version in my fetch query on appsync console. But the query does not return _version in my flutter application. I have tried below request methods, both does not return _version --- 1) ```final request = ModelQueries.get(VariableList.classType, "c80d6fb2-97ed-4194-8d80-d9cfe6125321");``` --- 2) ``` <code>String someId = "c80d6fb2-97ed-4194-8d80-d9cfe6125321"; const getVariableList = "getVariableList"; String graphQLDocument = ''' {getVariableList(id: "c80d6fb2-97ed-4194-8d80-d9cfe6125321") { CropType OrderStatus PaymentStatus _version id PaymentType StableVersion }} '''; final request = GraphQLRequest<VariableList>( document: graphQLDocument, modelType: VariableList.classType, variables: <String, String>{'id': someId}, decodePath: getVariableList); final response = await Amplify.API.query(request: request).response; ```

Hi, how can I set custom HTML content for the email that Amplify Cognito send automatically to the user when i call the signUp API of the Auth module or when the user ask for forgot password? I see that there is a field in the "Password protection settings" section in the Authentication settings page of Amplify Studio console, but it's only a simple text field, I can't specified HTML. Thank you!

I have a question about use of conditionally requesting AWS Amplify queries. In the Amplify sample codes, I had to request every queries in database and add them to other array with condition(ex. owner == userId) to use it. ``` fun queryNotes() { Log.i(TAG, "Querying notes") Amplify.API.query( ModelQuery.list(NoteData::class.java), { response -> Log.i(TAG, "Queried") Log.i(TAG, response.toString()) for (noteData in response.data) { Log.i(TAG, noteData.name) // TODO should add all the notes at once instead of one by one (each add triggers a UI refresh) UserData.addNote(UserData.Note.from(noteData)) } }, { error -> Log.e(TAG, "Query failure", error) } ) } ``` However, if there are lots of queries(over than hundred thousands), i expected that it would cause low service quality such as low speed or excessive use of Amplify server resources. I want to know whether my expectation is right or wrong. If it is wrong, I want to know why it is wrong. If it is right, I want to know how to solve it such as giving condition on the requesting step or setting request condition on the Amplify studio.

We are trying to deploy a new site and ran into an issue that has been keeping us from moving forward. We have recently upgraded our site from Vue2 to Vue3 and are re-deploying it using Cognito for authentication and Amplify for our site hosting and back-end. In the older version of Amplify, you could define the fields coming in from Cognito, but in the newer version, it automatically generates a aws-exports.js file that does not include the custom attributes from cognito. (It does include all the other settings from our UserPool, but not the custom attributes.) Anyone know how to get these custom attributes over into Amplify? I assume it has something to do with the automatically generated cloud formation templates, but I could not figure it out.

I tried syncing our Figma file to Amplify Studio and found that many of the components it generated didn’t look like the ones we have on Figma. Is there a possible way to fix this?

Does anyone experiencing "Unknown Error" when you "Sync with Figma" on existing synced UI components? It was working just few days ago, prior to minor changes on Amplify Studio UI recently. If I just re-create app with new app, then it works with same Figma URL and authentications. So suspecting issue on Amplify Studio's UI side, not Figma.

Good Day Everyone, Is Amplify studio ready to be used for building production workloads. I have few quick questions with regards to this: 1. Can you manage multiple environments say Dev, STG and Prod 2. Is there any pipeline that can be configured to rollout a deployment in the case of various environments 3. It uses cognito, I would like to integrate with Active Directory does this support. Cheers..!! Regards, Anandan. N

Hi Guys When running command "amplify pull --appId XXXXXXX --envName staging" on my local macjine I get the following error: Failed to pull the backend. request to https://prod.us-east-1.appstate.amplifyapp.com/AppState/?appId=XXXXXXXXXXX failed, reason: unable to get local issuer certificate. Whats causing it. And is it possible to ignoreSSL during amplify pull ?

Hi all, I´m new to Amplify (even to AWS) and I feel life is easier for non coders with some integrated services as Amplify->GraphQL->Lambda Functions->DynamoDB. I´m making some tries with these services working together and my question is: In all examples found, I can create a simple website but frontend code is always given in the tutorials or videos, and they don´t go deeper on how that code was created. Maybe javascript frameworks or others. As I want to create business logic on server side (GraphQL, Lambda, DynamoDB), I only need to make a simple visual frontend for using components (maybe created with Figma) and no need to code more than minimum. Is there a service (inside or outside AWS) to visually create a frontend interface without coding as building blocks to be integrated with Amplify? I thought Amplify Studio could be my tool but I couldn´t find how. Thanks in advance,

On a super user account with full permissions, the initial step of creating a new Ampify Studio project fails with a lack of permissions. Created a second account with each of the requested permissions mapped out, still results in the same error. Error Details: > You are missing the following permissions to deploy your Amplify backend successfully: * cognito-idp:DescribeUserPool * cognito-idp:DeleteUserPool * cognito-idp:CreateUserPool * cognito-idp:CreateUserPoolClient * cognito-idp:UpdateUserPool * cognito-idp:AdminSetUserPassword * cognito-identity:GetIdentityPoolRoles * cognito-identity:SetIdentityPoolRoles * cognito-identity:CreateIdentityPool * cognito-identity:DeleteIdentityPool * lambda:GetFunction * lambda:CreateFunction * lambda:AddPermission * lambda:DeleteFunction * s3:DeleteObjectVersion * cloudformation:ListStacks * appsync:GetIntrospectionSchema * appsync:GraphQL * appsync:UpdateApiKey * appsync:ListApiKeys * s3:PutObject * s3:GetObject * s3:ListBucket * s3:ListBucketVersions * s3:DeleteBucket * s3:DeleteBucketPolicy * s3:DeleteBucketWebsite * s3:DeleteObject * s3:GetBucketLocation * s3:ListAllMyBuckets * sts:AssumeRole * mobiletargeting:* * amplify:CreateApp * amplify:CreateBackendEnvironment * amplify:GetApp * amplify:GetBackendEnvironment * amplify:ListApps * amplify:ListBackendEnvironments * amplify:CreateBranch * amplify:GetBranch * amplify:UpdateApp * amplify:ListBranches * amplify:ListDomainAssociations * amplify:DeleteBranch * amplify:DeleteApp * amplify:DeleteBackendEnvironment * amplifybackend:* * cognito-idp:AdminAddUserToGroup * cognito-idp:AdminCreateUser * cognito-idp:CreateGroup * cognito-idp:DeleteGroup * cognito-idp:DeleteUser * cognito-idp:ListUsers * cognito-idp:AdminGetUser * cognito-idp:ListUsersInGroup * cognito-idp:AdminDisableUser * cognito-idp:AdminRemoveUserFromGroup * cognito-idp:AdminResetUserPassword * cognito-idp:AdminListGroupsForUser * cognito-idp:ListGroups * cognito-idp:AdminDeleteUser * cognito-idp:AdminListUserAuthEvents * cognito-idp:AdminConfirmSignUp * cognito-idp:AdminEnableUser * cognito-idp:AdminUpdateUserAttributes * cognito-idp:DescribeIdentityProvider * appsync:CreateApiKey * appsync:CreateDataSource * appsync:CreateFunction * appsync:CreateResolver * appsync:CreateType * appsync:DeleteApiKey * appsync:DeleteDataSource * appsync:DeleteFunction * appsync:DeleteResolver * appsync:DeleteType * appsync:GetDataSource * appsync:GetFunction * appsync:GetResolver * appsync:GetSchemaCreationStatus * appsync:GetType * appsync:ListDataSources * appsync:ListFunctions * appsync:ListGraphqlApis * appsync:ListResolvers * appsync:ListResolversByFunction * appsync:ListTypes * appsync:StartSchemaCreation * appsync:UpdateDataSource * appsync:UpdateFunction * appsync:UpdateResolver * appsync:UpdateType * appsync:TagResource * appsync:CreateGraphqlApi * appsync:DeleteGraphqlApi * appsync:GetGraphqlApi * appsync:ListTagsForResource * appsync:UpdateGraphqlApi * apigateway:DELETE * apigateway:GET * apigateway:PATCH * apigateway:POST * apigateway:PUT * cognito-identity:DescribeIdentity * cognito-identity:DescribeIdentityPool * cognito-identity:UpdateIdentityPool * cognito-idp:DeleteUserPoolClient * cognito-idp:DescribeUserPoolClient * cognito-idp:ListTagsForResource * cognito-idp:ListUserPoolClients * cognito-idp:UpdateUserPoolClient * cognito-identity:TagResource * cognito-idp:TagResource * lambda:GetFunctionConfiguration * lambda:InvokeAsync * lambda:InvokeFunction * lambda:RemovePermission * lambda:UpdateFunctionCode * lambda:UpdateFunctionConfiguration * lambda:ListTags * lambda:TagResource * lambda:UntagResource * lambda:AddLayerVersionPermission * lambda:CreateEventSourceMapping * lambda:DeleteEventSourceMapping * lambda:DeleteLayerVersion * lambda:GetEventSourceMapping * lambda:GetLayerVersion * lambda:ListEventSourceMappings * cloudformation:CreateChangeSet * cloudformation:CreateStack * cloudformation:DeleteStack * cloudformation:DescribeChangeSet * cloudformation:DescribeStackEvents * cloudformation:DescribeStackResource * cloudformation:DescribeStackResources * cloudformation:DescribeStacks * cloudformation:ExecuteChangeSet * cloudformation:GetTemplate * cloudformation:UpdateStack

I am learning about Elastic Beanstalk and CloudFormation after having a little bit of experience with Amplify. I have an Amplify website using Next.js, my use case doesn't require data storage yet and i've been able to handle any 'backendish' related needs using lambda+api gateway+s3. I know I dont have any EC2 instances and ASGs set up when running my Amplify site and that makes me doubt that it can handle the same load that true infrastructure or infrastructure as software can. I have never been able to get a good yes or no answer regarding if Amplify can handle huge traffic spikes. I've read and heard from support that you can increase your service limit quota for lambda to help in this area but that seems very static and arbitrary - not at all a dynamic system like ASGs. It feels like ESB/CloudFormation would probably better suited to handle spikey traffic? Can someone with more experience let me know if this is true? Thank you!