search

aws-samples / one-observability-demo

Sample microservice based application demonstrating observability capabilities on AWS
https://observability.workshop.aws/
MIT No Attribution
225 stars 122 forks source link

Two Cloud9 IDEs can be created when not using Custom Event Engine Template #37

Closed alahser closed 3 years ago

alahser commented 4 years ago

So, if you are setting this up in a regular (non-event engine account), you create a Cloud9 environment, then run these commands

curl -O https://raw.githubusercontent.com/aws-samples/one-observability-demo/main/cloud9-cfn.yaml

aws cloudformation create-stack --stack-name C9-Observability-Workshop --template-body file://cloud9-cfn.yaml --capabilities CAPABILITY_NAMED_IAM

I believe these commands setup another Cloud9 IDE. I took a screenshot

Screen Shot 2020-11-10 at 6 04 59 PM

When you finally get here: 

test -n "$AWS_REGION" && echo AWS_REGION is "$AWS_REGION" || echo AWS_REGION is not set

aws sts get-caller-identity --query Arn | grep observabilityworkshop-admin -q && echo "You're good. IAM role IS valid." || echo "IAM role NOT valid. DO NOT PROCEED."

You get an IAM role error. See another screenshot

Screen Shot 2020-11-10 at 6 07 39 PM

At this point, if you return to the Cloud9 selection, you see that a 2nd environment is there. If you enter that Cloud9 and repeat all the steps, you can get past the IAM role error.

Having watched customers struggle with the deployment, I strongly suggest separate pages for each kind of deployment (Event Engine, Standalone, and non-using Cloud9). Many of them were executing commands blindly (rebooting, etc) without reading fully.

awsimaya commented 3 years ago

The workshop only works with custom EE blueprint or using own AWS account with proper perms. In this case it seems the custom blueprint was not used, which is a scenario the workshop doesn't support. Please reach out and to get access to the blueprint.