Visualizing Security Groups with Amazon Elasticsearch Service Rezensionen

not finished

Michael W. · Vor fast 6 Jahre überprüft

not finished

Michael W. · Vor fast 6 Jahre überprüft

not finished

Michael W. · Vor fast 6 Jahre überprüft

not finished

Michael W. · Vor fast 6 Jahre überprüft

not finished

Michael W. · Vor fast 6 Jahre überprüft

There's a lot going on here so not too much time for it to sink in given the elapsed time for elasticsearch to create its cluster.

Rob L. · Vor fast 6 Jahre überprüft

Evgeny K. · Vor fast 6 Jahre überprüft

Very satisfied. Would be nice to explain the account set up in order to get the lab to work.

Joe Z. · Vor fast 6 Jahre überprüft

Matt G. · Vor fast 6 Jahre überprüft

Cameron M. · Vor fast 6 Jahre überprüft

Poorly explained and often vague. This Lab seemed like less work was put into it and rushed.

Brian W. · Vor etwa 6 Jahre überprüft

Error while running the elasticdump command ``` /opt/node_modules/elasticdump/lib/parse-base-url.js:1 (function (exports, require, module, __filename, __dirname) { function parseBaseURL (_url, options = {}) { ^ SyntaxError: Unexpected token = at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:373:25) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (/opt/node_modules/elasticdump/lib/transports/elasticsearch.js:3:20) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) ``` Seems like it doesn't recognize ES6. I did a workaround by changing the `/opt/node_modules/elasticdump/lib/parse-base-url.js` to ``` function parseBaseURL (_url, options) { if (!options) { options = {} } var host = _url.replace(/\/+$/, '') var hostParts = host.split('/') var index ``` and was able to continue with the lab. Finished just in the nick of time, so would have liked some more duration of access to play around with Kibana Dashboard. Thank you!

Sanket P. · Vor etwa 6 Jahre überprüft

Got an error during elasticdump that prevented me from completing the lab.

Jon W. · Vor etwa 6 Jahre überprüft

Lab instructions didn't work at step 48

Christopher K. · Vor etwa 6 Jahre überprüft

4

Dale T. · Vor etwa 6 Jahre überprüft

The elasticdump command is completely broken with an internal error in its own parser - you should abandon that and just do a curl command for loading the kibana json - much easier - this stopped me from finishing the lab

Michael C. · Vor etwa 6 Jahre überprüft

Multiple missing data points and steps. Unable to complete lab as written.

Jason N. · Vor etwa 6 Jahre überprüft

Some typos on the lab steps and the dashboard that was created eg."protocal"

Gopinath S. · Vor etwa 6 Jahre überprüft

Overall, very helpful at getting introduced to using elasticsearch & kibana to analyze VPC FlowLogs. Two improvements that would help me feel like I could take this back to the office and make use of it: 1. filter out reply traffic since it does not represent an open port in a security group. 2. show how to map security group relationships (i.e. this traffic flow was allowed because the source was a member of sg-0000001 and the sg000002 that is associated with the destination permits this traffic from sg-000001, or IPCIDR, etc.) Visualize the web interconnectivity trust with a spiderweb diagram.

Christian P. · Vor etwa 6 Jahre überprüft

Christina P. · Vor etwa 6 Jahre überprüft

Cameron K. · Vor etwa 6 Jahre überprüft

more depth on the Kibana side would have been useful, but a good introduction.

Richard W. · Vor etwa 6 Jahre überprüft

河野 仁. · Vor etwa 6 Jahre überprüft

Vadim I. · Vor etwa 6 Jahre überprüft

This lab has you using a bunch of pre-configured tools, without learning a lot how they work.

Johnny E. · Vor etwa 6 Jahre überprüft