You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the discussed starting points for exploration of the various AWS data sources we intend to cover is a tile map with summary stats concerning the resources at hand as located on the globe.
This requires two types of geo coding:
dynamic - this covers IP address based data and is easily handled with the Logstash geoip filter
static - this covers well known, yet unspecified locations like AWS regions and CloudFront edge locations etc.
while these are nicely documented as such within AWS Global Infrastructure for example, surprisingly a resp. geo coded data set doesn't seem to be available
accordingly, one might start with the edge locations and denote one of them per region as the region's location
alternatively, I've found a single Amazon Web Services AWS Global Map and the _pageData element in the page source code contains the geo locations for the visualized subjects - not sure where the data stems from though
The text was updated successfully, but these errors were encountered:
One of the discussed starting points for exploration of the various AWS data sources we intend to cover is a tile map with summary stats concerning the resources at hand as located on the globe.
This requires two types of geo coding:
_pageData
element in the page source code contains the geo locations for the visualized subjects - not sure where the data stems from thoughThe text was updated successfully, but these errors were encountered: