Sign Up
cognitoidentityprovider_sign_up | R Documentation |
Registers a user with an app client and requests a user name, password, and user attributes in the user pool¶
Description¶
Registers a user with an app client and requests a user name, password, and user attributes in the user pool.
Amazon Cognito doesn't evaluate Identity and Access Management (IAM) policies in requests for this API operation. For this operation, you can't use IAM credentials to authorize requests, and you can't grant IAM permissions in policies. For more information about authorization models in Amazon Cognito, see Using the Amazon Cognito user pools API and user pool endpoints.
This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with Amazon Pinpoint. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in.
If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Services service, Amazon Simple Notification Service might place your account in the SMS sandbox. In sandbox mode , you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see SMS message settings for Amazon Cognito user pools in the Amazon Cognito Developer Guide.
You might receive a LimitExceeded
exception in response to this
request if you have exceeded a rate quota for email or SMS messages, and
if your user pool automatically verifies email addresses or phone
numbers. When you get this exception in the response, the user is
successfully created and is in an UNCONFIRMED
state.
Usage¶
cognitoidentityprovider_sign_up(ClientId, SecretHash, Username,
Password, UserAttributes, ValidationData, AnalyticsMetadata,
UserContextData, ClientMetadata)
Arguments¶
ClientId |
[required] The ID of the app client where the user wants to sign up. |
SecretHash |
A keyed-hash message authentication code (HMAC) calculated using
the secret key of a user pool client and username plus the client ID in
the message. For more information about |
Username |
[required] The username of the user that you want to sign up. The value of this parameter is typically a username, but can be any alias attribute in your user pool. |
Password |
The user's proposed password. The password must comply with the password requirements of your user pool. Users can sign up without a password when your user pool supports passwordless sign-in with email or SMS OTPs. To create a user with no password, omit this parameter or submit a blank value. You can only create a passwordless user when passwordless sign-in is available. |
UserAttributes |
An array of name-value pairs representing user attributes. For custom attributes, include a |
ValidationData |
Temporary user attributes that contribute to the outcomes of your pre sign-up Lambda trigger. This set of key-value pairs are for custom validation of information that you collect from your users but don't need to retain. Your Lambda function can analyze this additional data and act on it. Your function can automatically confirm and verify select users or perform external API operations like logging user attributes and validation data to Amazon CloudWatch Logs. For more information about the pre sign-up Lambda trigger, see Pre sign-up Lambda trigger. |
AnalyticsMetadata |
Information that supports analytics outcomes with Amazon Pinpoint, including the user's endpoint ID. The endpoint ID is a destination for Amazon Pinpoint push notifications, for example a device identifier, email address, or phone number. |
UserContextData |
Contextual data about your user session like the device fingerprint, IP address, or location. Amazon Cognito threat protection evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests. For more information, see Collecting data for threat protection in applications. |
ClientMetadata |
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user
pool triggers. When you use the SignUp API action, Amazon Cognito
invokes any functions that are assigned to the following triggers:
pre sign-up, custom message, and post
confirmation. When Amazon Cognito invokes any of these functions,
it passes a JSON payload, which the function receives as input. This
payload contains a For more information, see Using Lambda triggers in the Amazon Cognito Developer Guide. When you use the
|
Value¶
A list with the following syntax:
list(
UserConfirmed = TRUE|FALSE,
CodeDeliveryDetails = list(
Destination = "string",
DeliveryMedium = "SMS"|"EMAIL",
AttributeName = "string"
),
UserSub = "string",
Session = "string"
)
Request syntax¶
svc$sign_up(
ClientId = "string",
SecretHash = "string",
Username = "string",
Password = "string",
UserAttributes = list(
list(
Name = "string",
Value = "string"
)
),
ValidationData = list(
list(
Name = "string",
Value = "string"
)
),
AnalyticsMetadata = list(
AnalyticsEndpointId = "string"
),
UserContextData = list(
IpAddress = "string",
EncodedData = "string"
),
ClientMetadata = list(
"string"
)
)