Amplify data schema with multiple authorization rules
I am trying to create an Amplify (Gen 2) application with a data model that has two objects: a public ‘Log’ and a private ‘User’. However, I am unsure how to define this in the defineData
object. How can I define both apiKey
and userPool
authorization modes?
Amplify data schema with multiple authorization rules
I am trying to create an Amplify (Gen 2) application with a data model that has two objects: a public ‘Log’ and a private ‘User’. However, I am unsure how to define this in the defineData
object. How can I define both apiKey
and userPool
authorization modes?
AWS Amplify Gen2: How to call a custom-CDK-Construct-Lambda function in the Amplify backend data schema?
In AWS Amplify documentation is shown, how to define a customNotification CDK construct. However, the documentation lacks information on how to use it. I want to send a message to this CDK-Construct-Lambda from within the Amplify data schema, something like the following:
AWS Amplify Gen2: How to call a custom-CDK-Construct-Lambda function in the Amplify backend data schema?
In AWS Amplify documentation is shown, how to define a customNotification CDK construct. However, the documentation lacks information on how to use it. I want to send a message to this CDK-Construct-Lambda from within the Amplify data schema, something like the following:
AWS Amplify Gen2: How to call a custom-CDK-Construct-Lambda function in the Amplify backend data schema?
In AWS Amplify documentation is shown, how to define a customNotification CDK construct. However, the documentation lacks information on how to use it. I want to send a message to this CDK-Construct-Lambda from within the Amplify data schema, something like the following:
NPM error using npm create amplify@latest -y
I was following the AWS Amplify tutorial, and as I tried npm create npm create amplify@latest -y
, this error message popped up:
AWS Amplify: cannot access an attribute in the user object, but the attribute does exist
In src/index.js
, Amplify is initiated as below:
AWS Amplify: cannot access an attribute in the user object, but the attribute does exist
In src/index.js
, Amplify is initiated as below:
AWS Amplify: cannot access an attribute in the user object, but the attribute does exist
In src/index.js
, Amplify is initiated as below:
AWS Amplify: cannot access an attribute in the user object, but the attribute does exist
In src/index.js
, Amplify is initiated as below: