Skip to main content

Alexa Account Linking starting from your app (Optional)

[中文版本]

Introduction​

This account linking flow enables users to link their Alexa user account with their account in another service by starting from your app. When you start the account linking flow from the app, users can:

  • Discover your Alexa skill through your app.
  • Initiate skill enablement and account linking from within the app.
  • Link their account without entering Alexa account credentials if already logged into Alexa app. They will have to login to their app service once when trying to link accounts.
  • Link their account from your app using Login with Amazon (LWA), when the Alexa app isn't installed on their mobile device.

Note: The developer documentation for the app to app linking starting from mobile app can be found here.

Pre-requisites​

  • Rainmaker skills using stackset must be deployed. The detailed steps are given in the section Voice Assistant Integration.

    If not done, please follow the "Voice Assistant Integration" steps and come back here to enable App to App Account linking.

Following are the steps to configure Alexa App to App account linking:

Creating redirection URL for mobile apps​

Users are redirected to your app after they acknowledge the linking request in the Alexa app or LWA. For this redirection to happen, it is required to create Universal Link for iOS app and App Link for Android app.

Following are the steps to host the files for Universal link and App link in AWS S3 [Note: Please ensure that your user has admin privileges before moving onto the next steps]:

Creating S3 bucket​

  1. Go to AWS Console -> Services -> S3

  2. Click on "Create bucket".

  3. Add the name for the bucket.

  4. Select the region to create the bucket in.

  5. Scroll down to "Object Ownership" settings and select the "ACLs enabled" option

Change Object Ownership settings

  1. Scroll down to "Block Public Access settings for this bucket" settings.

  2. Untick the option "Block all public access", and accept the acknowledgment. Note that this step is mandatory for linking process.

Disable Block Public Access setting

  1. Scroll to the end of the page and select "Create Bucket".

  2. From the list of the buckets, click on the newly created bucket.

  3. Click on "Create Folder" and create .well-known folder.

    Creating folder on S3

  4. Tick the small box in front of the .well-known folder and click on the "Copy URL" option.

    Copy folder URL

  5. Remove the ".well-known/" suffix from the URL noted in step 10. Note this value, as it will be required in further steps. Let's call this value redirectURL.

  6. To create the App Link (Android) or Universal Link (iOS) refer to the steps given in the following:

Uploading the files to S3 with public read access​

  1. Go to AWS Console -> Services -> S3.

  2. From the list of the buckets, click on the newly created bucket.

  3. Go to .well-known folder.

  4. Upload the files in .well-known folder in S3 bucket:

  • For Android App Link, upload the assetslinks.json file, created in the previous section.

  • For iOS Universal Link, upload the apple-app-site-association file, created in the previous section.

Note that if you want to upload files for both iOS and android, steps 5-10 need to be done for both files.

  1. Scroll down and expand the "Permissions" section.

Object Permissions

  1. Select the "Grant public-read access" option.

S3 ACLs

  1. Accept the acknowledgment.

S3 object public Acknowledgement

  1. Click on Permissions tab. You need add below bucket policy by changing the bucket name & save changes.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::my-bucket-name/*"
        }
    ]
}

S3 bucket permissions

  1. Click on the "Upload" button at the end of the page.

Configuring callback URL in RainMaker​

  1. Login to RainMaker dashboard with admin credentials.

  2. Go to the Deployment Settings tab.

  3. Click on "Identity Configurations".

  4. Look for Cognito app client with client name "esp-rainmaker-alexa-skill".

  5. Update callback URLs for "esp-rainmaker-alexa-skill" client. Add the redirectURL value copied in step 12 of the "Creating S3 bucket" section, to the existing callback URLs.

Alexa callback URLs

Note that the two URLs should be separated by a comma(,).

Enabling App to App account linking for Alexa skill​

  1. Login to Alexa Developer Console.

  2. From the list of the skills, select the skills that you want to configure for app to app linking.

  3. Click on the Account Linking tab on the left navigation bar.

Account Linking tab

  1. Enable the option "Allow users to link their account to your skill from within your application or website"

Enable App Linking

  1. Scroll down to "Your Redirect URLs" setting.

  2. Click on the "+" sign to add the redirect URL.

  3. Enter the redirectURL value copied in step 12 of the "Creating S3 bucket" section.

Redirect URL configuration

  1. Add client secret for "esp-rainmaker-alexa-skill" app client. You can find the steps to get client id and client secret for "esp-rainmaker-alexa-skill" app client here- Getting client ID and client secret

RM Client Secret

  1. Save the changes.

Getting the value of Alexa Access token URL​

Make sure you are in the same AWS region where you have deployed RainMaker.

  1. Login to AWS console and go to API Gateway Service.

  2. Look for API Gateway "AlexaSkillLinking AWS Api Gateway".

API gateway

  1. Go to "stages" tab.

Stages

  1. Expand the dev stage.

  2. Click on POST method.

  3. Copy the Invoke URL. This URL will be required while configuring "alexaAccessTokenURL" for mobile apps.

Fetch Token URL


After the above configuration steps are completed, please configure Alexa account linking for mobile apps.

Steps for Alexa account linking configuration for iOS and Android apps:

On this page