Updated API Gateway Gateway Reponse to return default CORS headers

Author: justonian

Auth/2_ServerlessAPI/README.md

@@ -248,8 +248,8 @@ Now that you've deployed the new authorizer configuration to production, all API
 
 If the API now invokes correctly and application funcions as expected summoning unicorns, you may **proceed to complete either**:
 
-- **Optional module extension** with [Fine-grained IAM-based authorization with API Gateway](./Optional-APIGateway-IAMAuth.md)
+- **Optional module 2 extension** with [Fine-grained IAM-based authorization with API Gateway](./Optional-APIGateway-IAMAuth.md)
 
 	OR
 
-- To proceed to he next module, *without completing the optional module extension*, choose [client-side IAM-based Authorization](../3_IAMAuthorization).
+- To proceed to the module 3 *without completing the optional module extension*, choose [client-side IAM-based Authorization](../3_IAMAuthorization).

Auth/2_ServerlessAPI/ServerlessBackend.yaml

@@ -176,6 +176,9 @@ Resources:
     Type: AWS::ApiGateway::RestApi
     Properties:
       Name: WildRydes
+      EndpointConfiguration:
+        Types:
+          - REGIONAL
       Body:
         swagger: 2.0
         info:
@@ -241,7 +244,7 @@ Resources:
                 passthroughBehavior: "when_no_match"
                 type: "mock"
 
-  GatewayResponse:
+  Default4XXGatewayResponse:
     Type: AWS::ApiGateway::GatewayResponse
     Properties:
       ResponseParameters:
@@ -250,7 +253,7 @@ Resources:
       ResponseType: DEFAULT_4XX
       RestApiId: !Ref WildRydesApi
 
-  GatewayResponse:
+  Default5XXGatewayResponse:
     Type: AWS::ApiGateway::GatewayResponse
     Properties:
       ResponseParameters:

Auth/9_CleanUp/README.md

@@ -50,7 +50,7 @@
 
 #### Remove WildRydes Backend
 
-1. Next, we will need to remove the *CloudFormation stack* for the API. This stack should be named **WildRydesBackend**. Once again, from the your terminal window, run:
+1. Next, you will need to remove the *CloudFormation stack* for the API. This stack should be named **WildRydesBackend**. Once again, from the your terminal window, run:
 
 	```
 	aws cloudformation delete-stack --stack-name WildRydesBackend
@@ -59,9 +59,11 @@
 
 #### Remove Cloud9 and VPC Stack
 
-1. Lastly, we will need to remove the *CloudFormation Stack* for the **Cloud9 instance** and the its VPC. This stack should be named **WildRydes-Cloud9**
+1. Lastly, you will need to remove the *CloudFormation Stack* for the **Cloud9 instance** and the its VPC. This stack should be named **WildRydes-Cloud9**. Deleting this stack will **shut down and permanently delete your Cloud9 environment** and all code or projects within so be sure you want to proceed before executing this command.
 
 	```
 	aws cloudformation delete-stack --stack-name WildRydes-Cloud9
 	```
+	
+	
 	> If you changed the name of your stack from the default, you will need to update the stack name to what you changed it to.  If you clicked the quick link in the instructions, no adjustment to the command above is needed.  You can run `aws cloudformation describe-stacks` to find your stack name.