You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: workshop/content/topic-queue-chaining-and-load-balancer/create-customer-accounting-service-subscription/create-customer-accounting-service-subscription-console.md
+21-6Lines changed: 21 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,26 +20,41 @@ Enter `CustomerAccountingServiceQueue` as **Queue Name**, make sure **Standard Q
20
20
21
21
#### 2. Create a new subscription
22
22
23
-
After selecting the queue **CustomerAccountingServiceQueue**, click the **Queue Actions** drop down in the top left corner and chose **Subscribe Queue to SNS Topic**.
23
+
After creating the queue **CustomerAccountingServiceQueue**, click the **Subscribe to Amazon SNS Topic** button in the SNS Subscriptions tab.
24
24
25
25
{{%expand "Detailed description" %}}
26
26
27
27
{{% /expand%}}
28
28
29
-
In the pop up window, select the **RideCompletionTopic** and click **Subscribe**. Click **Ok** in the confirmation dialog.
29
+
In the Subscribe to Amazon SNS topic window, select the **RideCompletionTopic** and click **Save**.
30
30
31
31
{{%expand "Detailed description" %}}
32
32
33
33
{{% /expand%}}
34
34
35
-
#### 3. Validate the subscription confirmation
35
+
#### 3. Validate the subscription and add the filter to the subscription
36
36
37
-
Browse to your **[Amazon SNS console](https://console.aws.amazon.com/sns/v3/home?#/topics)** to list your existing topics. Select the **RideCompletionTopic** and verify, the subscription has the status **Confirmed**.
37
+
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)**).
38
38
39
39
{{%expand "Detailed description" %}}
40
40
41
41
{{% /expand%}}
42
42
43
+
Confirm that the Status of the subscription is **Confirmed**.
44
+
45
+
{{%expand "Detailed description" %}}
46
+
47
+
{{% /expand%}}
48
+
49
+
Click **Edit** to modify the subscription.
50
+
51
+
In the Edit subscription screen, click **Enable raw message delivery**. Click **Save Changes**
52
+
53
+
{{%expand "Detailed description" %}}
54
+
55
+
{{% /expand%}}
56
+
57
+
Now that we have updated the subscription, let's set the IAM policy for our Lambda function to access the queue.
43
58
44
59
#### 4. Grant permissions to our function to access the Amazon SQS queue
45
60
@@ -82,14 +97,14 @@ Select the **JSON** tab and passed the following policy statement into it, after
82
97
Make sure you provide the AWS ACCOUNT ID in the form of XXXXXXXXXXXX and not XXXX-XXXX-XXXX!
83
98
{{% /notice %}}
84
99
85
-
Click **Review policy** and enter the **Name**`CustomerAccountingServiceRolePolicy0`. Click **Create policy**. To validate this step, select on the role again and your should see 3 policies attached to your role, including the one you just have created:
100
+
Click **Review policy** and enter the **Name**`CustomerAccountingServiceRolePolicy0`. 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:
86
101
87
102
{{%expand "Detailed description" %}}
88
103
89
104
{{% /expand%}}
90
105
91
106
92
-
#### 5. Add the Amazon SQS queue as event source for your Customer Notification Service AWS Lambda function
107
+
#### 5. Add the Amazon SQS queue as event source for your Customer Accounting Service AWS Lambda function
93
108
94
109
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-CustomerAccounting...** (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:
Copy file name to clipboardExpand all lines: workshop/content/topic-queue-chaining-and-load-balancer/create-customer-notification-service-subscription/create-customer-notification-service-subscription-console.md
+21-7Lines changed: 21 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,13 +20,13 @@ Enter `CustomerNotificationServiceQueue` as **Queue Name**, make sure **Standard
20
20
21
21
#### 2. Create a new subscription
22
22
23
-
After selecting the queue **CustomerNotificationServiceQueue**, click the **Queue Actions** drop down in the top left corner and chose **Subscribe Queue to SNS Topic**.
23
+
After creating the queue **CustomerNotificationServiceQueue**, click the **Subscribe to Amazon SNS Topic** button in the SNS Subscriptions tab.
24
24
25
25
{{%expand "Detailed description" %}}
26
26
27
27
{{% /expand%}}
28
28
29
-
In the pop up window, select the **RideCompletionTopic** and click **Subscribe**. Click **Ok** in the confirmation dialog.
29
+
In the Subscribe to Amazon SNS topic window, select the **RideCompletionTopic** and click **Save**.
30
30
31
31
{{%expand "Detailed description" %}}
32
32
@@ -35,17 +35,31 @@ In the pop up window, select the **RideCompletionTopic** and click **Subscribe**
35
35
{{% notice tip %}}
36
36
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.
37
37
By initiating the subscription from the subscriber side, this is not necessary.
38
-
39
38
{{% /notice %}}
40
39
41
-
#### 3. Validate the subscription confirmation
40
+
#### 3. Validate the subscription and add the filter to the subscription
42
41
43
-
Browse to your **[Amazon SNS console](https://console.aws.amazon.com/sns/v3/home?#/topics)** to list your existing topics. Select the **RideCompletionTopic** and verify, the subscription has the status **Confirmed**.
42
+
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)**).
44
43
45
44
{{%expand "Detailed description" %}}
46
-
45
+
47
46
{{% /expand%}}
48
47
48
+
Confirm that the Status of the subscription is **Confirmed**.
49
+
50
+
{{%expand "Detailed description" %}}
51
+
52
+
{{% /expand%}}
53
+
54
+
Click **Edit** to modify the subscription.
55
+
56
+
In the Edit subscription screen, click **Enable raw message delivery**. Click **Save Changes**
57
+
58
+
{{%expand "Detailed description" %}}
59
+
60
+
{{% /expand%}}
61
+
62
+
Now that we have updated the subscription, let's set the IAM policy for our Lambda function to access the queue.
49
63
50
64
#### 4. Grant permissions to our function to access the Amazon SQS queue
51
65
@@ -88,7 +102,7 @@ Select the **JSON** tab and passed the following policy statement into it, after
88
102
Make sure you provide the AWS ACCOUNT ID in the form of XXXXXXXXXXXX and not XXXX-XXXX-XXXX!
89
103
{{% /notice %}}
90
104
91
-
Click **Review policy** and enter the **Name**`CustomerNotificationServiceRolePolicy0`. Click **Create policy**. To validate this step, select on the role again and your should see 3 policies attached to your role, including the one you just have created:
105
+
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:
0 commit comments