It is used to translate public IP address to private IP address or vise versa. It allows instance(s) in private subnet to connect to internet or on premises or other VPC.
Yes, it is a very common and powerful use case for VPC peering to enable communication between resources in private subnets across different VPCs.
The purpose of launching a private subnet instances is to isolate from internet access. Hence, assigning a public IP to instances in private subnet is not useful.
When using AWS CLI, there is a major security risk that AWS warns about. What is that risk and how to mitigate that risk?
Major security risk that AWS warns is the storage of credentials (Access Key ID and Secret Access Key) on local machines and in source code. If the machine is compromised, an attacker gaining access to these credentials can immediately obtain them. By prioritizing temporary credentials and applying the principle of lease privilege, we can mitigate the security risk associated with using the AWS CLI.
Blackhole