AWS SysOps Administrator - Associate | Online Training in July 2017

Hi guys,

I hope you have learned from the YouTube videos till now. I am organising an Online training for AWS SysOps Administrator - Associate level. Please let me know if you are interested.

Online Training starting in July 2017.
Duration: 24 hours
Timing: 7 to 11 AM (IST)
Dates: 8, 9, 15, 16, 22, 23 July (4 hours each day) all weekends
Cost: Rs. 16,999/-

SysOps Certification is the most practical oriented and hence you would find lots of #labs and #demos.

Agenda is attached below....
Please let me know if you are interested to join via comment or direct message.

AWS Solutions Architect - Associate | Classroom Training at Bangalore

The details of this training has been updated. Please click here to read current details.

Hi guys,

I hope you have learned from the Youtube videos till now. I am organising a 4 day Classroom training at Bangalore for AWS Solutions Architect - Associate level. Please let me know if you are interested.

Duration - 4 days
Track - AWS Solutions Architect - Associate
Location - Bangalore (27th to 30th July) #datesUpdated
Cost - Rs. 22,999/-
Course would have lots of #labs, case-studies and industry examples.

Please let me know if you are interested to join via comment or direct message. Agenda given below.

AWS ENI - Query from Viewers -- 005

Hi guys, 

I have got following doubts from one of our viewers on this video -- 

So by adding multiple ENI to AN INSTANCE 
1. Still its a single point of failure, Where in if the instance fails, all the attached ENI also fails right? 
ANS: Yes, if instance fails all the ENIs attached to that instance would not be of any use. Mutiple ENIs do not increase Availability or Bandwidth of the machine. Rather, they are there for the isolation purpose.

2. Normally in an ON-PREM INFRA, we used to have muti NIC for the webserver not to have a single point of failure in case of one NIC CARD fails? Where as in AWS its a virtual world and I assume its a managed service right? we don't have to worry about the Primary failing at all ? 
ANS: On AWS, we handle that scenario via Auto-scaling Group. So that if a machine becomes unreachable, another instance takes its place. 

3. Why should we disable the SOURCE/DESTINATION CHECK FLAG for the ENI? I think we disable the "SOURCE/DESTINATION" only when we create a NAT INSTANCE, that's right? 
ANS: That's correct. Other than NAT, you do not have to disable it. 

4. The primary ENI can't be detached, Becoz that's the one which makes the instance to have a public and/or private IP right? 
ANS: Not so. It is more of a restriction from AWS implementation perspective. In future, they might start allowing it (as you can detach ROOT EBS volume for a stopped machine).

5. So the best use case for multi eni would be, Where in a. In a single large instance with multi ENI, that one instance can be part of both private and public subnet b. Having said that, I can have web server facing the internet in the public ENI and the database also in the same instance in the private ENI and configure the security group accordingly. 
ANS: Sorry, Incorrect! When you create ENI, you can see that its scope is a Subnet (same way scope of an EC2 is also Subnet). Hence, an EC2 and an ENI would be there only in one subnet (not two). 
You can use multi ENI to give 2 different IPs to 2 different user groups. E.g. On an EC2 open port 8080 on IP1 and port 22 on IP2. Also, attach different security groups in above ENIs. Hence, the users would never know they are accessing the same machine. 

 6. So with multiNIC, I can have multiple websites on the same server, with each Nic attached to one website?
ANS: You can have multiple websites on one machine even without multi-NIC. Different webservers (like IIS) support the same. 

Selected videos!