You have SSH access via bastion. The EC2 is in a private subnet with a NAT Gateway supposedly configured.
The interviewer asks“A newly launched EC2 instance in your VPC cannot make outbound internet requests. The instance is running, SSH works from your bastion, but curl fails. Walk me through your debugging process.”
Check Security Groups, NACL rules, Route Tables, NAT Gateway status and association, Internet Gateway attachment, and instance's public IP or NAT attachment. Work through the OSI model — IP connectivity before DNS.
A free account unlocks the rest of it, and saves your progress across every track.
aws configure Set up AWS CLI credentials, region and profilesaws s3 Copy, sync and list files in Amazon S3aws ec2 Find, start and stop EC2 instances from the CLIaws iam Inspect users, roles and policies, and debug accessaws eks Connect kubectl to EKS and manage cluster accessaz Manage Azure resources with the Azure CLIgcloud Manage Google Cloud with the gcloud CLI