Lec02-Publicip vs private ip

 What is public Ip address vs Private Ip address ?

 

Both public and private IP addresses play important roles in Azure resources, but they serve different purposes:

 

Public IP addresses:

 

  • Accessibility: Accessible from the internet, allowing resources like web servers to be directly accessed.
  • Use cases: Hosting websites, remote desktop access, public-facing applications, accessing external services.
  • Cost: Charges apply for using a public IP address.
  • Management: Can be assigned statically (dedicated) or dynamically (temporary), and can be associated with multiple resources.

 

Private IP addresses:

 

  • Accessibility: Only accessible within the virtual network where the resource is located.
  • Use cases: Internal communication between resources, secure hosting behind a load balancer or firewall.
  • Cost: No additional charges for using a private IP address.
  • Management: Automatically assigned by Azure within the subnet's address range and cannot be accessed directly from the internet.

 

Choosing between a public and private IP depends on your specific needs and security requirements.

 

Here are some additional things to consider:

 

  • Dynamic vs. static public IP: If you require consistent IP address, choose a static public IP. Otherwise, a dynamic IP might be sufficient.

 

  • Outbound connections: Even with a private IP, outbound connections to the internet are possible through Azure NAT (Network Address Translation).

 

  • Load balancers and firewalls: Public IP can be associated with a load balancer for distributing traffic among resources, while private IPs can be secured behind a firewall for enhanced protection.

 

Here's a breakdown of dynamic and static public IP addresses in Azure:

 

Dynamic Public IP:

 

  • Assignment: Not assigned immediately upon creation. IP is allocated when associated with a resource (like a VM).
  • Release: IP is released when the resource is stopped or deallocated, and might change when restarted.
  • Cost: Generally lower cost compared to static IPs.
  • Use cases:
    • Temporary resources
    • Resources without a dependency on a fixed IP address
    • Development and testing environments
    •  

Static Public IP:

 

  • Assignment: Assigned permanently when created and remains associated with your account until explicitly released.
  • Persistence: IP persists even if the associated resource is stopped, deallocated, or moved.
  • Cost: Typically higher cost than dynamic IPs.
  • Use cases:
    • Resources requiring a consistent, predictable IP address
    • Production environments
    • DNS records pointing to specific IPs
    • Access control lists (ACLs) based on IP addresses
    • VPN connections

 

 

 

 

 

 

 

Key differences:

 

  • Changeability: Static IPs remain constant, while dynamic IPs can change under certain conditions.
  • Cost: Static IPs usually have a higher cost than dynamic IPs.
  • Suitability: Static IPs are better suited for resources requiring a fixed IP, while dynamic IPs are appropriate for temporary or non-critical resources.

 

Additional considerations:

 

SKU: Azure offers Basic and Standard SKUs for public IP addresses.

    • Basic SKU supports only dynamic IPs.
    • Standard SKU supports both static and dynamic IPs.

 






 


Comments

Post a Comment

Popular posts from this blog

Script

# Change time to IST Set-TimeZone -Name “India Standard Time”  # Enable firewall to ping server each other :-   New-NetFirewallRule -DisplayName "Allow ICMPv4-In" -Protocol ICMPv4   # PowerShell command to install ISS # install IIS server role   Install-WindowsFeature -name Web-Server -IncludeManagementTools   # remove default htm file   remove-item   C:\inetpub\wwwroot\iisstart.htm   # Add a new htm file that displays server name   Add-Content -Path "C:\inetpub\wwwroot\iisstart.htm" -Value $("Hello World from " + $env:computername)     # Powershell command to install google chrome   $LocalTempDir = $env:TEMP; $ChromeInstaller = "ChromeInstaller.exe"; (new-object     System.Net.WebClient).DownloadFile('http://dl.google.com/chrome/install/375.126/chrome_installer.exe', "$LocalTempDir\$ChromeInstaller"); & "$LocalTempDir\$ChromeInstaller" /silent /install; $Process2Monitor = ...
Read more

Landing Zone

What is Azure landing zone   An Azure Landing Zone is a set of best practices and guidelines provided by Microsoft to help organizations establish a well-structured and standardized foundation for deploying workloads and applications in the Microsoft Azure cloud environment. It is essentially a framework that assists organizations in setting up their Azure environment with a focus on key areas such as security, governance, compliance, and operational efficiency. Here are the main aspects and objectives of an Azure Landing Zone: 1. ** Security **: Implementing robust security measures to protect data and resources in Azure, including network security, identity and access management, and compliance with security standards. 2. ** Governance **: Defining and enforcing policies and standards for resource provisioning, naming conventions, and compliance requirements. This ensures that Azure resources are created and managed consistently across the organization. 3. ** Networking **: ...
Read more

Migration

  Prepare a machine for the replication appliance The Migration and modernization tool uses a replication appliance to replicate machines to Azure. The replication appliance runs the following components. Configuration server : The configuration server coordinates communications between on-premises and Azure, and manages data replication. Process server : The process server acts as a replication gateway. It receives replication data; optimizes it with caching, compression, and encryption, and sends it to a cache storage account in Azure. Run a test migration When delta replication begins, you can run a test migration for the VMs, before running a full migration to Azure. We highly recommend that you do this at least once for each machine, before you migrate it. Running a test migration checks that migration will work as expected, without impacting the on-premises machines, which remain operational, and continue replicating. Test migration simulates the migration by creating an Azur...
Read more