Role trust and permissions - Amazon Cognito
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Role trust and permissions

The way these roles differ is in their trust relationships. The following is an example trust policy for an unauthenticated role:

{ "Version": "2012-10-17", "Statement": [ { "Sid": "", "Effect": "Allow", "Principal": { "Federated": "" }, "Action": "sts:AssumeRoleWithWebIdentity", "Condition": { "StringEquals": { "": "us-east-1:12345678-corner-cafe-123456790ab" }, "ForAnyValue:StringLike": { "": "unauthenticated" } } } ] }

This policy grants federated users from (the issuer of the OpenID Connect token) permission to assume this role. Additionally, the policy restricts the aud of the token, in this case the identity pool ID, to match the identity pool. Finally, the policy specifies that one of the array members of the multi-value amr claim of the token issued by the Amazon Cognito GetOpenIdToken API operation has the value unauthenticated.

When Amazon Cognito creates a token, it sets the amr of the token as either unauthenticated or authenticated. If amr is authenticated, the token includes any providers used during authentication. This means that you can create a role that trusts only users that logged in via Facebook by changing the amr condition as shown:

"ForAnyValue:StringLike": { "": "" }

Be careful when changing your trust relationships on your roles, or when trying to use roles across identity pools. If you don't configure your role correctly to trust your identity pool, an exception from STS results, like the following:

AccessDenied -- Not authorized to perform sts:AssumeRoleWithWebIdentity

If you see this message, check that your identity pool and authentication type have an appropriate role.