NAT Gateway | Notion

Based on the provided transcript on NAT Gateways and NAT Instances in the context of AWS DevOps, NAT Gateway needs to be initiated in a public subnet. here's a concise and organized summary:

NAT Gateways

Managed Service: Unlike NAT instances, NAT Gateways are a managed service, offering ease of use and no need for manual administration.
Higher Bandwidth: They automatically scale from 5 Gbps up to 100 Gbps.
High Availability: NAT Gateways provide high availability within a single Availability Zone (AZ).
No Security Groups Required: Simplifies management as there's no need to configure security groups.
Cost: Charges are based on the hour of usage and the amount of data transferred.
Elastic IP Association: NAT Gateways are associated with an Elastic IP address.
Subnet Usage: They must be placed in a public subnet and can only route traffic from instances in private subnets.
Dependency on Internet Gateway: Can only function with an Internet Gateway.
High Availability Setup: Requires multiple NAT Gateways across different AZs for fault tolerance.

Untitled

NAT Instances

Manual Management: Requires manual setup and administration, including security group configurations.
Variable Bandwidth: Bandwidth depends on the instance type chosen.
Scripted Failover: High availability and failover must be managed through custom scripting.
Cost: Charges are based on instance size and the amount of data transferred.
Use as Bastion Host: This can be used as a Bastion host for SSH access to instances in private subnets.

Comparison

Feature	NAT Gateway	NAT Instance
Management	Managed by AWS	Manual management required
Bandwidth	Up to 100 Gbps, automatically scaling	Depends on instance type
High Availability	Within a single AZ	Requires scripts for failover
Security Groups	Not required	Required
Cost	Hourly rate + data transfer	Hourly rate (instance type) + data transfer
Elastic IP Association	Yes	Yes
It can be used as a Bastion Host	No	Yes