would adding new sign-in with apple functionality raise any issue ?

Hello there,

Sign in's integration with Apple is a great step toward improving the user experience.

First, the Sign In with Apple integration shouldn't interfere with your current settings or device compatibility. It's meant to work alongside your current sign-in procedures and should flow naturally with how your app is currently set up.

The fact that you're adding a new sign-in mechanism won't change the fact that the Android and iOS apps are accessing the same data because both of them use the same AWS DynamoDB. There should be no problems as long as the logic of your program correctly handles the various sign-in options.

I'd suggest utilizing AWS Cognito in addition to conventional username/password and other social sign-in methods because it has built-in support for Sign in with Apple. This might make your implementation easier and give your users a more seamless experience.

Hope this helps.

Hello,

From the limited information provided on the different components used by your mobile application, I presume that your mobile application is using AWS Cognito user pools[1] for authentication, and AWS Cognito identity pools[2] for retrieving AWS temporary credentials to access DynamoDB.

If the above assumption is accurate, adding another identity provider such as "Apple" to your Cognito user pool app client[3] will not lead to any issues, as the authentication flow depends on the JWT tokens returned by your Cognito user pool, which are later traded for AWS STS tokens - that are used to access DynamoDB.

However, if authentication is not handled by Amazon Cognito within your application, and you are using another identity provider/custom integration for the purpose of authentication, then the behaviour of your application may vary based on the way your application is designed to handle authenticated end users.

On the subject of access to DynamoDB, AWS STS tokens are required to authenticate the end user while accessing the DynamoDB table. Hence, as long as your authentication flow ensures STS tokens are made available to the end user, access to DynamoDB will remain intact.

That being said, to further look into this issue more closely, if you would like to do a resource based troubleshooting, please raise a support case with AWS. If a support case has already been created please be assured that we will get back to you and assist you in the best way possible.

====================

References:

[1]. Amazon Cognito user pools https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools.html

[2]. Amazon Cognito identity pools (federated identities) https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-identity.html

[3]. Adding user pool sign-in through a third party https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-identity-federation.html