jimleach.co.uk Report : Visit Site

Technical data of the jimleach.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host jimleach.co.uk. Currently, hosted in United States and its service provider is E.I. du Pont de Nemours and Co. Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

jim's ether ramblings of life's adventures 23,333 arc 2017 coastal yachtmaster resume about me pirate-jim here we come posted: may 5, 2017 | author: jim-23333 | filed under: uncategorized | tags: sailaway | comments off on pirate-jim here we come amongst the diving and working it seems this year i’ll also be partaking in some sailing too.. may – quick whiz around the solent with commodore yachting to reacquaint myself with a yacht june – sailing around norway from bergen to aalesund november – all being well , i may be sailing the atlantic rally for cruisers from las palmas (spain) to st lucia simple aws diagrams posted: march 28, 2017 | author: jim-23333 | filed under: uncategorized | comments off on simple aws diagrams so my most recent post included some visio-style diagrams but not done in visio.. try draw.io out, it’s pretty good. basic, but good. my first vpc posted: march 28, 2017 | author: jim-23333 | filed under: aws | comments off on my first vpc my first attempt at building some form of basic infrastructure constructs in aws.. keep in mind that this is the learning curve, so in no way represents best-practice deployments! the building blocks internet gateway single vpc in london region (eu-west) two subnets, one in each availability zone (eu-west-2a and eu-west-2b) for web servers two subnets, one in each availability zone for bastion hosts two launch configurations – one for bastion hosts, one for webservers one auto scaling group for web servers – min instances 2, linked to webserver launch configuration one auto scaling group for bastion host – min instances 1, linked to bastion launch configuration elastic load balancer – inbound http/s connected to the web server auto-scaling group one security group for web servers – enables inbound http / https from anywhere, and ssh from the bastion subnets one security group for bastion hosts – enables inbound ssh from anywhere one iam role – to enable read-only access to s3 web server launch configuration each web server is built using a launch configuration which has a bootstrap script to do the following: update standard ami packages install apache and php start apache set apache to start on bootup copy custom index.php from s3 (this is why it needs an iam role to access s3!) copy health-check html from s3 make index.php executable the index.php is a basic “hello world” which also shows the internal ip of the host serving it.. this way when tweaking with load-balancers i can tell which instance has served the request. the two pages are stored in an s3 bucket and the iam role applied to the launch configuration allows the instances to copy the files down to the web server. #! /bin/bash yum update -y yum install http php -y service httpd start chkconfig httpd on aws s3 --region eu-west-2 cp s3://e02-lab-scripts/index.php /var/www/html/ aws s3 --region eu-west-2 cp s3://e02-lab-scripts/healthcheck.html /var/www/html/ chmod +x /var/www/html/index.php summary this stuff is bloody complicated – but – certainly not impossible. once you know what all the components are, how they work and interact with each other, it’s easy to start building services and constructs based on them. and it all started so well posted: march 25, 2017 | author: jim-23333 | filed under: aws | leave a comment well – my first foray into aws was going so well.. i’ve been using a cloud guru for my aws architect associate training and following each of the labs and doing a bit of playing in the background myself. since getting through the initial s3 and ec2 videos, i brought up a bitnami wordpress instance to host this site and did the relevant route53 transfer and what have you. i also moved our wedding website to an s3-static site bucket as post-wedding it didn’t need php or anything fancy to run. all seemed well and good. then i decided that since i was now hosting ‘live’ sites from my aws account, i didn’t really want to be meddling with labs and accidentally destroy something.. so i created a new account and went about building a little lab environment: new vpc, subnets for web services, subnets for bastion hosts, scaling groups.. the works! i thought i was doing so well until i tried connecting to the first bastion instance i’d created and got a dreaded ssh time-out! cut to the chase: if you don’t want to read the rest, just remember this: don’t forget a default gateway in the routing table – it doesn’t add itself! the idiot network engineer “user error” – i thought. obviously. so i walked through my configuration: elasticip associated.. check. instance attached to subnet.. duh, check. subnet associated in routing table.. check. vpc associated with internet gateway.. check. security group has sensible ruleset (ssh and http/s inbound from 0.0.0.0/0).. check. so i still couldn’t see what the issue was. now, at this point, i hadn’t done any training on cloudwatch, but i noticed in the vpc configuration i could do something with flow logs. so a bit of playing around and following the on-screen “ you’re trying to do something you’re not ready for yet “-type instructions, i got flow information for the vpc going into a log and i could drill down on a per-instance basis. now i could see what was going on.. nothing wrong with the rules, my ping’s and ssh attempts clearly had ‘accept’ next to them, so the inbound path was fine. then it dawn on me… stuff is getting in, but how is it getting out – or more precisely – does it know how to get out? so back to look at the routing table i went, with the sudden realisation that there was no default route! doh! and i’m supposed to be a network engineer! so what’s the lesson here: an aws internet gateway isn’t given the default route by default.. makes sense, you might want to use a vasa or something what good came out of this.. i learnt how to use cloudwatch the house has moved posted: march 8, 2017 | author: jim-23333 | filed under: aws | leave a comment that’s right.. in bowing to the mentality that you should do what you preach, the 23,333 blog has moved home to aws! more in the next post how this was accomplished… moving markets and upskilling posted: december 8, 2016 | author: jaleach | filed under: aws , ccie , personal , uncategorized | comments off on moving markets and upskilling i had absolutely no idea that aws in its contemporary form came into existence in 2006, right around the time i started at cisco and my first venture into the network industry. i was aware of aws as a platform a few years later but like many (and with my lack of experience and insight) didn’t realise the impact or potential of it. having worked in networking for 10-years now (oct 2006-2016) and seen the dramatic change from old c6500 switching to modern soc-based /merchant-silicon, as well as the more recent influx of ‘sdx’ technologies, i can see clearly now that platforms like aws and azure are quickly becoming the de-facto choice for future it strategies for both infrastructure and services. with this in mind, it’s time to upshift the skill set and move on. i had originally planned to complete the vcdx-nv qualification and i may well still do this over the long term but, in the short-term i’m going to focus on retaining my ccie r&s until it becomes emeritus and put significant efforts into training for aws, azure and some more general architecture specialisations such as togaf. 2017 will be the year of architecture for me. docker-pi – db and visualisation posted: december 8, 2016 | author: jaleach | filed under: docker , pi2 , uncategorized | comments off on docker-pi – db and visualisation during my docker trials and tribulations, i found two great tools for storing measurement and then displaying them.. influxdb it’s not a complex database like mysql – it’s a simple way of storing time-lapse measurements. i’ll late use it for storing temperature and humidity measurements, but for now we’ll get it setup and drop in some resource stats from the pi. thankfully, someone’s already compiled influx for th

URL analysis for jimleach.co.uk

https://jimleach.co.uk/2013/09/
https://jimleach.co.uk/category/cisco/
https://jimleach.co.uk/2014/11/
https://jimleach.co.uk/tag/vcdx-nv/
https://jimleach.co.uk/2017/03/28/my-first-vpc/
https://jimleach.co.uk/category/aws/
https://jimleach.co.uk/tag/virl/
https://jimleach.co.uk/tag/onepk/
https://jimleach.co.uk/2016/09/17/pi-docker-failure/
https://jimleach.co.uk/2016/12/08/docker-pi-db-and-visualisation/
https://jimleach.co.uk/2015/11/
https://jimleach.co.uk/2016/12/08/moving-markets-and-upskilling/
https://jimleach.co.uk/2015/08/
https://jimleach.co.uk/tag/cisco/
https://jimleach.co.uk/resume/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Error for "jimleach.co.uk".

the WHOIS query quota for 2600:3c03:0000:0000:f03c:91ff:feae:779d has been exceeded
and will be replenished in 547 seconds

WHOIS lookup made at 09:23:20 07-Oct-2017

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2017.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS jimleach.co.uk

  PORT 43

  TYPE domain

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2017.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

DOMAIN

  NAME jimleach.co.uk

NSERVER

  NS-1190.AWSDNS-20.ORG 205.251.196.166

  NS-1578.AWSDNS-05.CO.UK 205.251.198.42

  NS-267.AWSDNS-33.COM 205.251.193.11

  NS-708.AWSDNS-24.NET 205.251.194.196

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .