Hello Tom,
First, thank you for giving us acces to you platform and all its AMIs!
I know you are overwhelmed by your job, but I have a few notes concerning the documentation.
In the medium documentation (step1, step2, ...) the command lines to deploy the CyberRange do not use terraformcommands directly, but makecommands. This is not the same in getting_started.md, so it is confusing.
The Makefile is very simple to understand, once we have understood to add environment variables ENV and REGION, like:
make init ENV=demo REGION=eu-west-2
make plan ENV=demo REGION=eu-west-2
make cyberRange ENV=demo REGION=eu-west-2
...
make destroy-force ENV=demo REGION=eu-west-2
Furthermore, the make cyberRange command needs to have previously installed inspec, because of checkLab sub-command call.
At the begining, the ENV variable rule was not clear to me, but it is only an arbitrary name for the deployed platform.
Please Tom, could you upgrade the getting_started.md file, or simplify it by giving links to medium documentation?
Thanks in advance,
Regards, Remy
Hello Tom, First, thank you for giving us acces to you platform and all its AMIs! I know you are overwhelmed by your job, but I have a few notes concerning the documentation.
In the medium documentation (step1, step2, ...) the command lines to deploy the CyberRange do not use
terraformcommands directly, butmakecommands. This is not the same ingetting_started.md, so it is confusing.The Makefile is very simple to understand, once we have understood to add environment variables
ENVandREGION, like:Furthermore, the
make cyberRangecommand needs to have previously installed inspec, because ofcheckLabsub-command call.At the begining, the
ENVvariable rule was not clear to me, but it is only an arbitrary name for the deployed platform.Please Tom, could you upgrade the
getting_started.mdfile, or simplify it by giving links to medium documentation? Thanks in advance, Regards, Remy