{"id":48479,"date":"2017-12-11T15:50:23","date_gmt":"2017-12-11T15:50:23","guid":{"rendered":"https:\/\/www.whizlabs.com\/?p=48479"},"modified":"2024-05-17T09:15:05","modified_gmt":"2024-05-17T03:45:05","slug":"elastic-network-interface","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/elastic-network-interface\/","title":{"rendered":"Introduction to Elastic Network Interface"},"content":{"rendered":"<blockquote><p>Recently, we have covered a topic on <a href=\"https:\/\/www.whizlabs.com\/blog\/nat-gateway\/\" target=\"_blank\" rel=\"noopener noreferrer\">Implementation of to NAT Gateway<\/a>. In this article, let&#8217;s understand the implementation of Elastic Network Interface.<\/p><\/blockquote>\n<p style=\"text-align: justify;\"><b>Exam Objective<\/b><\/p>\n<p style=\"text-align: justify;\">The topic &#8220;Elastic Network Interface&#8221; addresses the Design and Implementation of AWS Networks topic as highlighted in the AWS Blueprint for the exam guide<\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/d1.awsstatic.com\/training-and-certification\/docs-advnetworking-spec\/AWS_Certified_Advanced_Networking_Blueprint.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/d1.awsstatic.com\/training-and-certification\/docs-advnetworking-spec\/AWS_Certified_Advanced_Networking_Blueprint.pdf<\/a><\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/aws-advanced-networking-speciality\/\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-48638\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/WRITING-101.jpg\" alt=\"AWS Certified Advanced Networking Specialty \" width=\"728\" height=\"90\" \/><\/a><\/p>\n<h2 style=\"text-align: justify;\">What is Elastic Network Interface?<\/h2>\n<p style=\"text-align: justify;\">AWS Elastic Network Interface is simply a virtual interface that can be attached to an instance in a Virtual Private Cloud (VPC). Followings are the attributes of a network interface:<\/p>\n<ul style=\"text-align: justify;\" type=\"disc\">\n<li>A primary private IPv4 address<\/li>\n<li>One Elastic IP address (IPv4) per private IPv4 address<\/li>\n<li>One or more secondary private IPv4 addresses<\/li>\n<li>One public IPv4 address<\/li>\n<li>One or more security groups<\/li>\n<li>One or more IPv6 addresses<\/li>\n<li>A source\/destination check flag<\/li>\n<li>A MAC address<\/li>\n<li>A description<\/li>\n<\/ul>\n<p style=\"text-align: justify;\">By default, each instance will have a primary network interface. This can be seen while the instance is being created.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network1.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48483 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network1.png\" alt=\"Elastic Network Interface\" width=\"636\" height=\"109\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">This IP will get a Private IP address. It will also get a public IP address if the setting has been enabled for the Subnet in which the instance is located in. You can also add Secondary IP addresses to an Elastic Network Interface.<\/p>\n<p style=\"text-align: justify;\">You can also add Secondary Network Interfaces to an Instance.<\/p>\n<p style=\"text-align: justify;\">In our Implement example, we will see how to swap network interfaces between 2 instances. This can be done for implementing fault tolerance for an application.<\/p>\n<p style=\"text-align: justify;\">Let\u2019s say we have 2 Instances, one is a primary instance which hosts a web application. This has been assigned a secondary network interface. This interface has an Elastic IP assigned which is accessed by external Users. Let\u2019s say that you have a standby instance which has the same web server installed but is in the non-active state. Only if the primary instance fails for any reason, then a failover happens to the secondary instance.<a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network2.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48484 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network2.png\" alt=\"Primary Instance\" width=\"434\" height=\"196\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">So now to ensure that the failover happens from the primary to secondary instance seamlessly so that the same Elastic IP address can be used for standby instance, the ENI can be shifted to the secondary Instance. It needs to be ensured that the subnets for the instances belong to the same availability zone.<\/p>\n<p style=\"text-align: justify;\">So now let\u2019s look at the implementation of this.<\/p>\n<p style=\"text-align: justify;\"><span class=\"s1\"><strong>Note:<\/strong> CIDR is one of the important terms an AWS Network Engineer should know about. CIDR offers the benefits of effective management of available IP address space and reduces the number of routing table entries. If you are still wondering <a href=\"https:\/\/www.whizlabs.com\/blog\/cidr-classless-inter-domain-routing\/\" target=\"_blank\" rel=\"noopener\">what does CIDR stand for<\/a>, learn more!<\/span><\/p>\n<h4 style=\"text-align: justify;\"><b>Implementation of Failover using the Elastic Network Interface<\/b><\/h4>\n<p>Followings are the steps to implement Elastic Network Interface:<\/p>\n<p style=\"text-align: justify;\">Step 1) Firstly we will create 2 Instances of the type Amazon Machine Image. These Instances will be created in the subnet of the same availability zone<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network3.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48485 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network3.png\" alt=\"Network Interface\" width=\"627\" height=\"176\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Here the Servers have been named as Primary and Standby Server. Each of these servers only has the primary network interface<\/p>\n<p style=\"text-align: justify;\">Step 2) On the PrimaryServer and Standby Server, we are going to install a Web server known as nginx via the following commands<\/p>\n<p style=\"text-align: justify;\">sudo yum update<\/p>\n<p style=\"text-align: justify;\">sudo yum install nginx<\/p>\n<p style=\"text-align: justify;\">Once done, we need to start the nginx service on the primary server<\/p>\n<p style=\"text-align: justify;\">sudo service nginx start<\/p>\n<p style=\"text-align: justify;\">When you go to the Public IP of the Primary Server, you should get the following page. Ensure that the Security Group of the PrimaryServer allows traffic on port 80.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network4.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48486 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network4.png\" alt=\"AWS Elastic Network Interface\" width=\"626\" height=\"205\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Step 3) Now let\u2019s create a Secondary Network Interface. This will be attached to the Primary Server. In the EC2 Dashboard, click on Create Network Interface<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network5.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48487 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network5.png\" alt=\"AWS Certified Advanced Network Specialty\" width=\"628\" height=\"286\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Give a description of the new network interface. Create it in Subnet A, because that is where the PrimaryServer resides. Attach the Security Group of the Primary Server to the Elastic Network Interface.<\/p>\n<p style=\"text-align: justify;\">Then Create the Interface.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network6.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48488 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network6.png\" alt=\"Create Network Interface\" width=\"628\" height=\"234\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Once the Interface has been created, click the Interface and click on Attach<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network7.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48489 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network7.png\" alt=\"Network Interface\" width=\"629\" height=\"276\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Attach it to the Primary Server<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network8.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48490 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network8.png\" alt=\"Attach Network Interface\" width=\"596\" height=\"241\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Once the network interface has been attached, this will reflect in the Instance configuration.<\/p>\n<p style=\"text-align: justify;\">In the EC2 dashboard, for the Primary Server, you will see 2 Private IP\u2019s now.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network9.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48491 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network9.png\" alt=\"IPv4 \" width=\"360\" height=\"162\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Note that we chose the Amazon Machine Image because the configuration happens automatically for this AMI. If you choose another Linux Instance like Ubuntu, you need to do the configuration manually for the secondary network interface.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network10.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48492 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network10.png\" alt=\"Elastic Network Interface\" width=\"626\" height=\"463\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Step 4) Now let\u2019s attach an Elastic IP to the Secondary ENI which we have attached to the primary instance.<\/p>\n<p style=\"text-align: justify;\">Go to the Elastic IP section. Allocate a new Elastic IP address if one is not present.<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network11.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48493 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network11.png\" alt=\"Elastic IP\" width=\"627\" height=\"330\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Let\u2019s now associate it to the Secondary Private IP on the PrimaryServer<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network12.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48494 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network12.png\" alt=\"AWS Elastic Network Interface\" width=\"632\" height=\"261\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Step 5) To ensure the web server is running on the Elastic IP of the primary server, you need to ensure the Secondary private IP is entered in the configuration file for the Web server. For nginx, this setting will be in the \/etc\/nginx\/nginx.conf file. First, stop the nginx server, change the Private IP and port number to the below. This IP is the private IP of the secondary ENI attached to the primary server.<\/p>\n<p style=\"text-align: justify;\">server {<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 20.0.1.25:80;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:80 default_server;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server_name\u00a0 localhost;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 root\/usr\/share\/nginx\/html;<\/p>\n<p style=\"text-align: justify;\">Then start the nginx server to confirm it is running, now on the Elastic IP<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network13.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48495 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network13.png\" alt=\"nginx on Amazon Linux AMI\" width=\"638\" height=\"230\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Step 6)\u00a0 Now to initiate a proper failover we need to perform the following<\/p>\n<ol style=\"text-align: justify;\" start=\"1\" type=\"1\">\n<li>Install nginx on the SecondaryServer<\/li>\n<li>Now we are going to modify the home page displayed by nginx just to understand that when we browse to this server, it is reflecting the page on this server<\/li>\n<\/ol>\n<p style=\"text-align: justify;\">We need to go to the \/usr\/share\/nginx\/html folder and modify the index.html file. So if you browse to the home page of the web server on the Secondary Server, it would look like the below<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network14.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48496 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network14.png\" alt=\"nginx on secondary server\" width=\"627\" height=\"228\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Here the Welcome to message says \u201cWelcome to nginx on Secondary Server\u201d<\/p>\n<ol style=\"text-align: justify;\" start=\"1\" type=\"1\">\n<li>Next, we need to ensure to modify the nginx.conf file on this server as well to ensure it listens to the private IP as shown below. This is so that when the switch happens, the Elastic IP would anyway point to the below private IP and that would point to the web server on the secondary server.<\/li>\n<\/ol>\n<p style=\"text-align: justify;\">server {<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 20.0.1.25:80;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 listen\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:80 default_server;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server_name\u00a0 localhost;<\/p>\n<p style=\"text-align: justify;\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 root\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/usr\/share\/nginx\/html;<\/p>\n<p style=\"text-align: justify;\"><b><u>\u00a0<\/u><\/b><\/p>\n<p style=\"text-align: justify;\">Step 7) Now let\u2019s swap the Secondary ENI from the primary to the standby server<\/p>\n<p style=\"text-align: justify;\">First Detach the Secondary Network Interface<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network15.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48497 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network15.png\" alt=\"Network Interface\" width=\"628\" height=\"280\" \/><\/a><\/p>\n<p style=\"text-align: justify;\">Once detached, attach it to the Standby Server<\/p>\n<p style=\"text-align: justify;\">Now when you browse to the Elastic IP, you will get the home page of the Standby Server<\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network16.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48498 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-network16.png\" alt=\"Attach Network Interface\" width=\"592\" height=\"242\" \/><\/a><\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-Network17.png\"><img decoding=\"async\" class=\"aligncenter wp-image-48499 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2024\/05\/Elastic-Network17.png\" alt=\"nginx on Secondary Server\" width=\"636\" height=\"248\" \/><br \/>\n<\/a><\/p>\n<h4><b>Important Points About Elastic Network Interface<\/b><\/h4>\n<ul type=\"disc\">\n<li style=\"text-align: justify;\">You can attach a network interface in one subnet to an instance in another subnet in the same VPC; however, both the network interface and the instance must reside in the same Availability Zone.<\/li>\n<li style=\"text-align: justify;\">You may require to bring up the second interface manually for the hot or warm attach of the additional network interface. So, it is advised to first configure the private IPv4 address, and then modify the route table according to that.<\/li>\n<li style=\"text-align: justify;\">The procedure of the attachment of another network interface to an existing instance (for example, a NIC teaming configuration) cannot be used to increase the network bandwidth to or from the dual-homed instance.<\/li>\n<li style=\"text-align: justify;\">If two or more network interfaces from the same subnet are attached to an instance, you may encounter networking issues such as asymmetric routing. It is recommended to use a secondary private IPv4 address on the primary network interface, if possible.<\/li>\n<\/ul>\n<p><i>The aim of Whizlabs is to help the individuals in their journey of preparing and passing AWS Certified Advanced Networking Specialty certification exam. We deliver the best and high-quality preparation material to evolve professional career. Whizlabs content is prepared by the industry experts who have a great knowledge and passion for cloud computing. We are continuously growing our cloud expert\u2019s community.<\/i><\/p>\n<blockquote><p><em>Preparing for AWS Certified Advanced Networking Speciality Certification? Pass in 1st Attempt. Start with Whizlabs\u00a0<a href=\"https:\/\/www.whizlabs.com\/aws-advanced-networking-speciality\/free-test\/\" target=\"_blank\" rel=\"noopener noreferrer\">Free<\/a>\u00a0and\u00a0<a href=\"https:\/\/www.whizlabs.com\/aws-advanced-networking-speciality\/practice-tests\/\" target=\"_blank\" rel=\"noopener noreferrer\">Practice<\/a>\u00a0Tests Now!<\/em><\/p><\/blockquote>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Recently, we have covered a topic on Implementation of to NAT Gateway. In this article, let&#8217;s understand the implementation of Elastic Network Interface. Exam Objective The topic &#8220;Elastic Network Interface&#8221; addresses the Design and Implementation of AWS Networks topic as highlighted in the AWS Blueprint for the exam guide https:\/\/d1.awsstatic.com\/training-and-certification\/docs-advnetworking-spec\/AWS_Certified_Advanced_Networking_Blueprint.pdf What is Elastic Network Interface? AWS Elastic Network Interface is simply a virtual interface that can be attached to an instance in a Virtual Private Cloud (VPC). Followings are the attributes of a network interface: A primary private IPv4 address One Elastic IP address (IPv4) per private IPv4 address One [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":48641,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"default","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[4],"tags":[201,228,278,730,1123],"class_list":["post-48479","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aws-certifications","tag-aws-certifications","tag-aws-certified-network-specialty","tag-aws-elastic-network-interface","tag-elastic-ip-address","tag-network-interface"],"uagb_featured_image_src":{"full":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1-150x150.png",150,150,true],"medium":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1-300x169.png",300,169,true],"medium_large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"1536x1536":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"2048x2048":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"profile_24":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",24,14,false],"profile_48":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",48,27,false],"profile_96":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",96,54,false],"profile_150":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",150,84,false],"profile_300":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",300,169,false],"tptn_thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1-250x250.png",250,250,true],"web-stories-poster-portrait":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",560,315,false],"web-stories-publisher-logo":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",96,54,false],"web-stories-thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2017\/12\/Introduction-to-Elastic-Network-Interface-1.png",150,84,false]},"uagb_author_info":{"display_name":"Pavan Gumaste","author_link":"https:\/\/www.whizlabs.com\/blog\/author\/pavan\/"},"uagb_comment_info":15,"uagb_excerpt":"Recently, we have covered a topic on Implementation of to NAT Gateway. In this article, let&#8217;s understand the implementation of Elastic Network Interface. Exam Objective The topic &#8220;Elastic Network Interface&#8221; addresses the Design and Implementation of AWS Networks topic as highlighted in the AWS Blueprint for the exam guide https:\/\/d1.awsstatic.com\/training-and-certification\/docs-advnetworking-spec\/AWS_Certified_Advanced_Networking_Blueprint.pdf What is Elastic Network Interface?&hellip;","_links":{"self":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/48479","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/comments?post=48479"}],"version-history":[{"count":4,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/48479\/revisions"}],"predecessor-version":[{"id":95851,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/48479\/revisions\/95851"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media\/48641"}],"wp:attachment":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media?parent=48479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/categories?post=48479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/tags?post=48479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}