Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
Curtis Rissi edited this page Dec 21, 2017 · 3 revisions
  • Package Cloud9 environment?

    • As part of the pre-reqs, we can provide the user with a cloudformation template that will setup a VPC in their account. This VPC can then be used for both the remainder of the workshop to house the clusters we're building as well as the development environment for Cloud9. They would simply need to log into the Console and deploy the stack.
    • This template would include the following:
      • Creation of a VPC and all that goes with it
      • as part of that VPC, we will need to select a subnet that can be used to spin up the development server
      • Name for the Dev Environment
      • Description for the Dev Environment
      • Instance type for the dev server (t2.*?)
      • Optional: a code commit repo that will be cloned into this server (possibly this workshop?)
  • How do you share Cloud9 env at scale using CloudFormation or something similar

    • You can share an environment with IAM users within an account. For the simplicity of a group event, we can have an account created with predefined IAM users that are locked down to the specific permissions necessary for the workshop only. We could then share these users with participants in the workshop and then rotate the keys/passwords after each event.
    • The only challenge here is users will be working in a shared environment and may end up stomping on each other. Another option would be to have multiple environments provisioned and named for specific users, giving then each their own environment. However, while this helps during the workshop, it doesn't leave them with an environment that they can walk away from the workshop that they can continue to use.
Clone this wiki locally