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
{{ message }}
This repository was archived by the owner on Jan 14, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: WebApplication/6_GraphQLAPI/README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,18 +232,18 @@ You've completed the testing of your AWS AppSync based GraphQL API!
232
232
233
233
:white_check_mark: After you have successfully tested your new function using the Lambda console, you can move on to the next module, [Building the History page][history-page].
Copy file name to clipboardExpand all lines: WebApplication/9_CleanUp/README.md
+74-65Lines changed: 74 additions & 65 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,24 @@ This page provides instructions for cleaning up the resources created during the
4
4
5
5
## Resource Cleanup Instructions
6
6
7
-
### 1. Module 5 Cleanup
8
-
Delete the Unicorn Manager CloudFront distribution and S3 bucket for the static website hosting created in module 5. Using the Lambda console, also delete the **ListUnicornRides** and **ListUnicornAuthorizer** functions. If you have deployed the pre-requisites CloudFormation stack, delete the stack using the CloudFormation console.
7
+
### 1. Module 6 - AppSync GraphQL API Cleanup
8
+
9
+
<details>
10
+
<summary><strong>:white_check_mark: Step-by-step directions(expand for details)</strong></summary><p>
11
+
Delete the AppSync GraphQL API. From the AppSync console, select the application and click **Delete**
12
+
13
+
1. Go to the [AWS AppSync Console][appsync-console].
14
+
1. Select the API created for this workshop.
15
+
1. Select **Delete** from the top right.
16
+
1. Complete the application deletion process.
17
+
18
+
</p></details>
19
+
20
+
### 2. Module 5 - OAuth Cleanup
9
21
10
22
<details>
11
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
23
+
<summary><strong>:white_check_mark: Step-by-step directions(expand for details)</strong></summary><p>
24
+
Delete the Unicorn Manager CloudFront distribution and S3 bucket for the static website hosting created in module 5. Using the Lambda console, also delete the **ListUnicornRides** and **ListUnicornAuthorizer** functions. If you have deployed the pre-requisites CloudFormation stack, delete the stack using the CloudFormation console.
12
25
13
26
1. In the AWS Management Console, click **Services** then select **CloudFront** under Networking & Content Delivery.
14
27
@@ -32,118 +45,114 @@ Delete the Unicorn Manager CloudFront distribution and S3 bucket for the static
32
45
33
46
</p></details>
34
47
35
-
### 2. Module 4 Cleanup
48
+
### 3. Module 4 - REST API Cleanup
36
49
Delete the REST API created in module 4. There is a **Delete API** option in the **Actions** drop-down when you select your API in the Amazon API Gateway Console.
37
50
38
-
<details>
39
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
40
-
41
-
1. In the AWS Management Console, click **Services** then select **API Gateway** under Application Services.
51
+
**:white_check_mark: Step-by-step directions**
42
52
53
+
1. Go to the [Amazon API Gateway Console][api-gw-console]
43
54
1. Select the API you created in module 4.
44
-
45
55
1. Expand the **Actions** drop-down and choose **Delete API**.
46
-
47
56
1. Enter the name of your API when prompted and choose **Delete API**.
48
57
49
-
</p></details>
50
-
51
-
52
-
### 3. Module 3 Cleanup
58
+
### 4. Module 3 - Serverless Backend Cleanup
53
59
Delete the AWS Lambda function, IAM role and Amazon DynamoDB table you created in module 3.
54
60
55
-
<details>
56
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
61
+
**:white_check_mark: Step-by-step directions**
57
62
58
63
#### Lambda Function
59
64
60
-
1. In the AWS Management Console, click **Services** then select **Lambda** under Compute.
61
-
65
+
1. Go to the [AWS Lambda console][lambda-console]
62
66
1. Select the `RequestUnicorn` function you created in module 3.
63
-
64
67
1. From the **Actions** drop-down, choose **Delete function**.
65
-
66
68
1. Choose **Delete** when prompted to confirm.
67
69
68
70
#### IAM Role
69
71
70
-
1. In the AWS Management Console, click **Services** then select **IAM** under Security, Identity & Compliance.
71
-
72
+
1. Go to the [AWS IAM Console][iam-console]
72
73
1. Select **Roles** from the navigation menu.
73
-
74
74
1. Type `WildRydesLambda` into the filter box.
75
-
76
75
1. Select the role you created in module 3.
77
-
78
76
1. From the **Role actions** drop-down, select **Delete role**.
79
-
80
77
1. Choose **Yes, Delete** when prompted to confirm.
81
78
82
79
#### DynamoDB Table
83
80
84
-
1. In the AWS Management Console, click **Services** then select **DynamoDB** under Databases
85
-
81
+
1. Go to the [Amazon DynamoDB Console][dynamodb-console]
86
82
1. Choose **Tables** in the navigation menu.
87
-
88
83
1. Choose the **Rides** table you created in module 3.
89
-
90
84
1. Choose **Delete table** from the **Actions** drop-down.
91
-
92
85
1. Leave the checkbox to **Delete all CloudWatch alarms for this table** selected and choose **Delete**.
93
86
94
-
</p></details>
95
-
96
-
### 4. Module 2 Cleanup
97
-
If you used the provided AWS CloudFormation template to complete module 2, simply delete the stack using the AWS CloudFormation Console. Otherwise, delete the Amazon Cognito user pool you created in module 2.
87
+
### 5. Module 2 - User Management Cleanup
88
+
Delete the Amazon Cognito User Pool
98
89
99
-
<details>
100
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
101
-
102
-
1. From the AWS Console click **Services** then select **Cognito** under Mobile Services.
90
+
**:white_check_mark: Step-by-step directions**
103
91
92
+
1. Go to the [Amazon Cognito Console][cognito-console]
104
93
1. Choose **Manage your User Pools**.
105
-
106
94
1. Select the **WildRydes** user pool you created in module 2.
107
-
108
95
1. Choose **Delete Pool** in the upper right corner of the page.
96
+
1. Complete the application deletion process.
109
97
110
-
1. Type `delete` and choose **Delete Pool** when prompted to confirm.
98
+
### 6. Module 1 - Web Application Cleanup
99
+
Delete the AWS Amplify Console application and optionally the AWS CodeCommit or GitHub repository created:
111
100
112
-
</p></details>
101
+
**:white_check_mark: Step-by-step directions**
113
102
114
-
### 5. Module 1 Cleanup
115
-
If you used the provided AWS CloudFormation template to complete module 1, simply delete the stack using the AWS CloudFormation Console. Otherwise, delete the Amazon S3 bucket you created in module 1.
103
+
#### For the Amplify Console web applcation:
116
104
117
-
<details>
118
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
105
+
1. Launch the [Amplify Console console page][amplify-console-console].
106
+
1. Select the application you launched today.
107
+
1. From **Actions** in the top right corner, select *Delete App*
108
+
1. Complete the application deletion process.
119
109
120
-
1. In the AWS Management Console choose **Services** then select **S3** under Storage.
110
+
#### For the CodeCommit repository:
121
111
122
-
1. Select the bucket you created in module 1.
112
+
1. Open the [AWS CodeCommit console][codecommit-console]
113
+
1. Select the radio button next to the repository created today.
114
+
1. Select **Delete repository** from the upper right of the page.
115
+
1. Complete the repository deletion process.
123
116
124
-
1. Choose **Delete bucket**.
125
117
126
-
1. Enter the name of your bucket when prompted to confirm, Then choose confirm.
118
+
### 7. CloudWatch Logs Cleanup
119
+
AWS Lambda automatically creates a new log group per function in Amazon CloudWatch Logs and writes logs to it when your function is invoked. You should delete the log group for the **RequestUnicorn** function.
127
120
128
-
</p></details>
129
-
130
-
131
-
### 6. CloudWatch Logs
132
-
AWS Lambda automatically creates a new log group per function in Amazon CloudWatch Logs and writes logs to it when your function is invoked. You should delete the log group for the **RequestUnicorn** function. Also, if you launched any CloudFormation stacks, there may be log groups associated with custom resources in those stacks that you should delete.
133
-
134
-
<details>
135
-
<summary><strong>Step-by-step instructions (expand for details)</strong></summary><p>
121
+
**:white_check_mark: Step-by-step directions**
136
122
137
123
1. From the AWS Console click **Services** then select **CloudWatch** under Management Tools.
138
-
139
124
1. Choose **Logs** in the navigation menu.
140
-
141
125
1. Select the **/aws/lambda/RequestUnicorn** log group. If you have many log groups in your account, you can type `/aws/lambda/RequestUnicorn` into the **Filter** text box to easily locate the log group.
142
-
143
126
1. Choose **Delete log group** from the **Actions** drop-down.
144
-
145
127
1. Choose **Yes, Delete** when prompted to confirm.
146
-
147
128
1. If you launched any CloudFormation templates to complete a module, repeat steps 3-5 for any log groups which begin with `/aws/lambda/wildrydes-webapp`.
148
129
149
-
</p></details>
130
+
### 8. Cloud9 Cleanup
131
+
Delete the Cloud9 Development environment created today.
132
+
133
+
**:white_check_mark: Step-by-step directions**
134
+
135
+
1. Launch the [Cloud9 console page][cloud9-console].
0 commit comments