A SysOps administrator launched an EC2 instance in a private subnet. From that instance, curl https://www.example.com fails to connect. What should the administrator do to restore outbound HTTPS connectivity from the instance?

For an EC2 instance to initiate an outbound HTTPS connection to the internet (like https://www.example.com), its security group must explicitly allow outbound traffic on TCP port 443. Security groups are stateful, meaning a response to an allowed outbound connection is automatically permitted inbound. The destination 0.0.0.0/0 represents all IP addresses, necessary for connecting to external websites. Incorrect options: Inbound rules on a security group control incoming traffic, not outgoing. While Network ACLs (NACLs) are stateless and require rules for both directions, the primary issue for an instance-initiated connection is usually the security group. Furthermore, the ephemeral port range is for inbound responses to outbound connections, not the initial outbound request itself. TCP port 80 is for HTTP, not HTTPS. The problem explicitly states https://www.example.com, which uses port 443.