Updated walkthrough and renamed ColorGateway to Frontend

Author: sshver

walkthroughs/howto-timeout-policy/README.md

@@ -48,7 +48,7 @@ export ENVIRONMENT_NAME=AppMeshTimeoutExample
 export MESH_NAME=ColorApp-Timeout
 export ENVOY_IMAGE=<get the latest from https://docs.aws.amazon.com/app-mesh/latest/userguide/envoy.html>
 export SERVICES_DOMAIN="default.svc.cluster.local"
-export COLOR_GATEWAY_IMAGE_NAME="colorgateway"
+export FRONTEND_IMAGE_NAME="frontend"
 export COLOR_TELLER_IMAGE_NAME="colorteller"
 ```
 
@@ -73,13 +73,13 @@ Finally, build and deploy the color app images.
 
 ```bash
 ./src/colorteller/deploy.sh
-./src/colorgateway/deploy.sh
+./src/frontend/deploy.sh
 ```
 Note that the example apps use go modules. If you have trouble accessing https://proxy.golang.org during the deployment you can override the GOPROXY by setting `GO_PROXY=direct`
 
 ```bash
 GO_PROXY=direct ./src/colorteller/deploy.sh
-GO_PROXY=direct ./src/colorgateway/deploy.sh
+GO_PROXY=direct ./src/frontend/deploy.sh
 ```
 
 ## Step 4: Create a Mesh 
@@ -185,7 +185,7 @@ aws appmesh-preview update-route --mesh-name $MESH_NAME --cli-input-json file://
 
 Confirm that we see request timeout as 20sec in the response
 
-Then update the ColorGateway Virtual Node and ColortellerWhite Virtual Node to add timeout of 20secs at the listener. The spec at ColortellerWhite Virtual Node looks like below, similar timeout is set at ColorGateway Virtual Node too.
+Then update the Frontend Virtual Node and ColortellerWhite Virtual Node to add timeout of 20secs at the listener. The spec at ColortellerWhite Virtual Node looks like below, similar timeout is set at Frontend Virtual Node too.
 
 ```json
 {
@@ -222,7 +222,7 @@ Then update the ColorGateway Virtual Node and ColortellerWhite Virtual Node to a
 }
 ```
 ```bash
-./mesh/mesh.sh update_colorgateway-vn mesh/colorgateway-vn-timeout20s.json
+./mesh/mesh.sh update_frontend-vn mesh/frontend-vn-timeout20s.json
 ./mesh/mesh.sh update_colorteller-white-vn mesh/colorteller-vn-timeout20s.json
 ```
 Confirm that the response contains the timeout as 20secs and wait for few seconds for envoys to receive the latest config. Then curl the endpoint again with latency as 17, and this time we should get a successful response.
@@ -237,7 +237,7 @@ Virtual Gateway and Gateway Routes are new App Mesh resources that are in previe
 
 Timeouts at Virtual Gateways are calculated implicitly based on the timeouts of the routes present in the Virtual Service that the Gateway Route points to. Currently there is no API to define the timeouts for gateways explicitly. In case you need any such feature, please request it using [App Mesh Github roadmap](https://github.com/aws/aws-app-mesh-roadmap/issues).
 
-Lets create a Virtual Gateway(VG) and route the requests through it (basically replacing ColorGateway Virtual Node with public gateway VG) to verify that the timeout works well with VG too.
+Lets create a Virtual Gateway(VG) and route the requests through it (basically replacing Frontend Virtual Node with public gateway VG) to verify that the timeout works well with VG too.
 
 ```bash
 ./mesh/mesh.sh add_virtual_gateway

walkthroughs/howto-timeout-policy/infrastructure/ecr-repositories.sh

@@ -10,5 +10,5 @@ aws --profile "${AWS_PROFILE}" --region "${AWS_DEFAULT_REGION}" \
     --capabilities CAPABILITY_IAM \
     --template-file "${DIR}/ecr-repositories.yaml" \
     --parameter-overrides \
-    GatewayImageName="${COLOR_GATEWAY_IMAGE_NAME}" \
+    FrontendImageName="${FRONTEND_IMAGE_NAME}" \
     ColorTellerImageName="${COLOR_TELLER_IMAGE_NAME}"

walkthroughs/howto-timeout-policy/infrastructure/ecr-repositories.yaml

@@ -1,6 +1,6 @@
 Parameters:
 
-  GatewayImageName:
+  FrontendImageName:
     Description: The name for the gateway image
     Type: String
 
@@ -10,10 +10,10 @@ Parameters:
 
 
 Resources:
-  GatewayRepository:
+  FrontendRepository:
     Type: AWS::ECR::Repository
     Properties:
-      RepositoryName: !Ref GatewayImageName
+      RepositoryName: !Ref FrontendImageName
 
   ColorTellerRepository:
     Type: AWS::ECR::Repository

walkthroughs/howto-timeout-policy/infrastructure/ecs-service.sh

@@ -14,5 +14,5 @@ aws --profile "${AWS_PROFILE}" --region "${AWS_DEFAULT_REGION}" \
     ECSServicesDomain="${SERVICES_DOMAIN}" \
     AppMeshMeshName="${MESH_NAME}" \
     EnvoyImage="${ENVOY_IMAGE}" \
-    ColorGatewayImageName="${COLOR_GATEWAY_IMAGE_NAME}" \
+    FrontendImageName="${FRONTEND_IMAGE_NAME}" \
     ColorTellerImageName="${COLOR_TELLER_IMAGE_NAME}"

walkthroughs/howto-timeout-policy/infrastructure/ecs-service.yaml

@@ -16,7 +16,7 @@ Parameters:
     Type: String
     Description: The image to use for the Envoy container
 
-  ColorGatewayImageName:
+  FrontendImageName:
     Description: The name for the gateway image
     Type: String
 
@@ -281,11 +281,11 @@ Resources:
             - 'Fn::ImportValue': !Sub "${EnvironmentName}:PrivateSubnet2"
       TaskDefinition: { Ref: ColorTellerRedTaskDefinition }
 
-  ### colorgateway.default.svc.cluster.local
-  ColorGatewayServiceDiscoveryRecord:
+  ### frontend.default.svc.cluster.local
+  FrontendServiceDiscoveryRecord:
     Type: 'AWS::ServiceDiscovery::Service'
     Properties:
-      Name: "colorgateway"
+      Name: "frontend"
       DnsConfig:
         NamespaceId:
           'Fn::ImportValue': !Sub "${EnvironmentName}:ECSServiceDiscoveryNamespace"
@@ -295,7 +295,7 @@ Resources:
       HealthCheckCustomConfig:
         FailureThreshold: 1
 
-  ColorGatewayTaskDefinition:
+  FrontendTaskDefinition:
     Type: AWS::ECS::TaskDefinition
     Properties:
       RequiresCompatibilities:
@@ -324,7 +324,7 @@ Resources:
             Value: '169.254.170.2,169.254.169.254'
       ContainerDefinitions:
         - Name: 'app'
-          Image: !Sub '${AWS::AccountId}.dkr.ecr.${AWS::Region}.amazonaws.com/${ColorGatewayImageName}'
+          Image: !Sub '${AWS::AccountId}.dkr.ecr.${AWS::Region}.amazonaws.com/${FrontendImageName}'
           Essential: true
           DependsOn:
             - ContainerName: 'envoy'
@@ -377,13 +377,13 @@ Resources:
               awslogs-stream-prefix: 'gateway-envoy'
           Environment:
             - Name: 'APPMESH_VIRTUAL_NODE_NAME'
-              Value: !Sub 'mesh/${AppMeshMeshName}/virtualNode/ColorGateway'
+              Value: !Sub 'mesh/${AppMeshMeshName}/virtualNode/Frontend'
             - Name: 'APPMESH_PREVIEW'
               Value: '1'
             - Name: 'ENVOY_LOG_LEVEL'
               Value: 'debug'  
 
-  ColorGatewayService:
+  FrontendService:
     Type: 'AWS::ECS::Service'
     DependsOn:
       - WebLoadBalancerRule
@@ -397,7 +397,7 @@ Resources:
       LaunchType: FARGATE
       ServiceRegistries:
         - RegistryArn:
-            'Fn::GetAtt': ColorGatewayServiceDiscoveryRecord.Arn
+            'Fn::GetAtt': FrontendServiceDiscoveryRecord.Arn
       NetworkConfiguration:
         AwsvpcConfiguration:
           AssignPublicIp: DISABLED
@@ -406,7 +406,7 @@ Resources:
           Subnets: 
             - 'Fn::ImportValue': !Sub "${EnvironmentName}:PrivateSubnet1"
             - 'Fn::ImportValue': !Sub "${EnvironmentName}:PrivateSubnet2"
-      TaskDefinition: { Ref: ColorGatewayTaskDefinition }
+      TaskDefinition: { Ref: FrontendTaskDefinition }
       LoadBalancers:
           - ContainerName: app
             ContainerPort: 80

walkthroughs/howto-timeout-policy/mesh/colorgateway-vn-timeout20s.json renamed to walkthroughs/howto-timeout-policy/mesh/frontend-vn-timeout20s.json

@@ -242,7 +242,7 @@ main() {
     case "$action" in
     up)
         create_mesh "${TEST_MESH_DIR}/mesh.json"
-        create_vnode "${TEST_MESH_DIR}/colorgateway-vn.json" "ColorGateway" "colorgateway"
+        create_vnode "${TEST_MESH_DIR}/frontend-vn.json" "Frontend" "frontend"
         create_vnode "${TEST_MESH_DIR}/colorteller-vn.json" "ColorTellerWhite" "colorteller"
 
         create_vrouter "${TEST_MESH_DIR}/colorteller-vr.json" "colorteller-vr"
@@ -254,7 +254,7 @@ main() {
         delete_vservice "colorteller.${SERVICES_DOMAIN}"
         delete_route "colorteller-vr" "colorteller-route"
         delete_vrouter "colorteller-vr"
-        delete_vnode "ColorGateway"
+        delete_vnode "Frontend"
         delete_vnode "ColorTellerWhite"
         delete_mesh
         ;;
@@ -280,8 +280,8 @@ main() {
     update_colorteller-red-vn)
         update_vnode "$2" "ColorTellerRed" "colorteller-red"
         ;;
-    update_colorgateway-vn)
-        update_vnode "$2" "ColorGateway" "colorgateway"
+    update_frontend-vn)
+        update_vnode "$2" "Frontend" "frontend"
         ;;
     *)
         err "Invalid action specified: $action"

walkthroughs/howto-timeout-policy/mesh/colorgateway-vn.json renamed to walkthroughs/howto-timeout-policy/mesh/frontend-vn.json

@@ -26,11 +26,11 @@ Resources:
     Properties:
       MeshName: !Ref MeshName
 
-  ColorGatewayVirtualNode:
+  FrontendVirtualNode:
     Type: AWS::AppMesh::VirtualNode
     Properties:
       MeshName: !GetAtt Mesh.MeshName
-      VirtualNodeName: ColorGateway
+      VirtualNodeName: Frontend
       Spec:
         BackendDefaults:
           ClientPolicy:
@@ -49,7 +49,7 @@ Resources:
               Protocol: http
         ServiceDiscovery:
           DNS:
-            Hostname: !Sub "colorgateway.${ServicesDomain}"
+            Hostname: !Sub "frontend.${ServicesDomain}"
 
   ColorTellerVirtualNode:
     Type: AWS::AppMesh::VirtualNode