Understand AWS Cognito users by sign-in method
I have an application which uses AWS Amplify (Gen 1) for managing users and storing/retrieving data. I’m using Amplify’s Auth and API modules – added using amplify add auth and amplify add api.
The packages I’m using are [email protected] and @aws-amplify/[email protected]
Unable to use the envitonmant file .env containing the API credentials in AWS Amplify 2.0 [closed]
Closed 1 hour ago.
Unable to use the envitonmant file .env containing the API credentials in AWS Amplify 2.0 [closed]
Closed 1 hour ago.
Unable to use the envitonmant file .env containing the API credentials in AWS Amplify 2.0 [closed]
Closed 1 hour ago.
Unable to use the envitonmant file .env containing the API credentials in AWS Amplify 2.0 [closed]
Closed 1 hour ago.
Unable to use the envitonmant file .env containing the API credentials in AWS Amplify 2.0 [closed]
Closed 1 hour ago.
Trying to add custom domain to my deployment on AWS Amplify
enter image description hereI am trying to add a custom domain to my deployment, it has been stuck on this stage for about 5 hours now. Is that ideal?
Trying to add custom domain to my deployment on AWS Amplify
enter image description hereI am trying to add a custom domain to my deployment, it has been stuck on this stage for about 5 hours now. Is that ideal?
Is it possible to remove SERVER respone header from AWS Amplify app
I have a react app.. hosted on amplify. It seems amplify uses cloudfront behind the scene so static content are served with header ‘Server: S3’.
I want to remove this via customhttp.yml however, cloudfront ignores this custom header and adds up its own header. Is there any way to remove it for Amplify app
Allow All Authenticated Users to Read Documents Created by Admin User Group With Amplify
Consider the following model in my Schema