+++
title = "Console"
disableToc = true
hidden = true
+++

#### 1. Create a new Amazon SQS queue

In your **[Amazon SQS console](https://console.aws.amazon.com/sqs/home?)**, select **Create New Queue** in top left corner or click **Get Started Now** in the center of the page, if it's your first queue in this region.

{{%expand "Detailed description" %}}
![Step 1](step-1-console.png)
{{% /expand%}}

Enter `CustomerNotificationServiceQueue` as **Queue Name**, make sure **Standard Queue** is highlighted and click **Create Queue**.

{{%expand "Detailed description" %}}
![Step 2](step-2-console.png)
{{% /expand%}}

#### 2. Create a new subscription

After creating the queue **CustomerNotificationServiceQueue**, click the **Subscribe to Amazon SNS Topic** button in the SNS Subscriptions tab.

{{%expand "Detailed description" %}}
![Step 3](step-3-console.png)
{{% /expand%}}

In the Subscribe to Amazon SNS topic window, select the **RideCompletionTopic** and click **Save**.

{{%expand "Detailed description" %}}
![Step 4](step-4-console.png)
{{% /expand%}}

{{% notice tip %}}
You may wondering why we don't create the subscription from the Amazon SNS console as shown below. If we create a subscription from Amazon SNS to Amazon SQS, Amazon SNS will send a confirmation message first to Amazon SQS. As long as this subscription is not confirmed, Amazon SNS will not start sending messages to Amazon SQS.
By initiating the subscription from the subscriber side, this is not necessary.
{{% /notice %}}

#### 3. Validate the subscription and add the filter to the subscription

Select the newly created subscription from the SNS subscriptions list and click the **View in SNS** button (this should open a new tab to the subscription in the **[Amazon SNS console](https://console.aws.amazon.com/sns/v3/home?#/topics)**).

{{%expand "Detailed description" %}}
![Step 4](step-5-console.png)
{{% /expand%}}

Confirm that the Status of the subscription is **Confirmed**.

{{%expand "Detailed description" %}}
![Step 4](step-5-1-console.png)
{{% /expand%}}

Click **Edit** to modify the subscription.

In the Edit subscription screen, click **Enable raw message delivery**. Click **Save Changes**

{{%expand "Detailed description" %}}
![Step 6](step-5-2-console.png)
{{% /expand%}}

Now that we have updated the subscription, let's set the IAM policy for our Lambda function to access the queue.

#### 4. Grant permissions to our function to access the Amazon SQS queue

In your **[Amazon IAM console](https://console.aws.amazon.com/iam)**, select **Roles** in the left navigation. Use the filter text box to find the role with the name **wild-rydes-async-msg-2-CustomerNotificationService-...** (assuming your have chosen `wild-rydes-async-msg-2` as your stack name).

{{%expand "Detailed description" %}}
![Step 6](step-6-console.png)
{{% /expand%}}

Click on the role name and click **Add inline policy** to attach another one.

{{%expand "Detailed description" %}}
![Step 7](step-7-console.png)
{{% /expand%}}

Select the **JSON** tab and passed the following policy statement into it, after you have substitute <<...>> with the correct values. It will add the permission to your Lambda function to access the Amazon SQS queue:

{{%expand "policy" %}}
```bash
{
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sqs:ChangeMessageVisibility",
                "sqs:ChangeMessageVisibilityBatch",
                "sqs:DeleteMessage",
                "sqs:DeleteMessageBatch",
                "sqs:GetQueueAttributes",
                "sqs:ReceiveMessage"
            ],
            "Resource": "arn:aws:sqs:<<AWS REGION>>:<<AWS ACCOUNT ID>>:CustomerNotificationServiceQueue"
        }
    ]
}
```
{{% /expand%}}

{{% notice tip %}}
Make sure you provide the AWS ACCOUNT ID in the form of XXXXXXXXXXXX and not XXXX-XXXX-XXXX!
{{% /notice %}}

Click **Review policy** and enter the **Name** `CustomerNotificationServiceRolePolicy0`. Click **Create policy**. To validate this step, select on the role again and your should see 2 policies attached to your role, including the one you just have created:

{{%expand "Detailed description" %}}
![Step 8](step-8-console.png)
{{% /expand%}}

#### 5. Add the Amazon SQS queue as event source for your Customer Notification Service AWS Lambda function

Open your **[AWS Lambda console](https://console.aws.amazon.com/lambda/home?#/functions)** and select **Functions** in the left navigation. Click on the function with the name **wild-rydes-async-msg-2-CustomerNotification...** (assuming your have chosen `wild-rydes-async-msg-2` as your stack name). Click on the **+ Add Trigger** button on the left side of the page:

{{%expand "Detailed description" %}}
![Step 9](step-9-console.png)
{{% /expand%}}

On the following page, select `SQS` as the event source for this AWS Lambda function. For the **SQS queue**, select the `CustomerNotificationServiceQueue` and set the **batch size** to `1`. Don't forget to **enable the trigger**, before you click the **Add** button in the lower right corner.

{{%expand "Detailed description" %}}
![Step 10](step-10-console.png)
{{% /expand%}}

After some seconds, the trigger will be enabled and and you are ready to go (you may have to refresh the site a few times).

{{%expand "Detailed description" %}}
![Step 11](step-11-console.png)
{{% /expand%}}