Why AWS recommends to avoid the use of public internet gateways in favor of AWS PrivateLink and VPC endpoints

Question

A VPC endpoint enables connections between a virtual private cloud (VPC) and supported services, without requiring that you use an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Therefore, your VPC is not exposed to the public internet.

AWS PrivateLink is a highly available, scalable technology that enables you to privately connect your VPC to supported AWS services, services hosted by other AWS accounts (VPC endpoint services), and supported AWS Marketplace partner services. You do not need to use an internet gateway, NAT device, public IP address, AWS Direct Connect connection, or AWS Site-to-Site VPN connection to communicate with the service. Therefore, your VPC is not exposed to the public internet.

What's so insecure of using public internet if all my incoming(to AWS)/outgoing(from AWS) connections use https? Could this still be decrypted?

I'm not very knowledgeable in networking/security that's why I'm asking.

Answer 1

Applications that can be accessed via the internet are known as public applications. They need access to the internet that is either direct or peroxided. HTTPS, as you do, is one technique to secure them. Your VPC will also require an internet gateway and/or NAT in order for them to function properly.
Private applications are ones that are only available from within an Amazon Web Services account. As a result, internet access is not required for these programmes, and it is not recommended. AWS PrivateLink can help in this situation. It enables you to share your application with other AWS users without requiring them to have access to the internet or even your VPC. From their own accounts and VPCs, they can access your private applications.