Given the network topology, what can be the issue?

Refer to the exhibit

You attempted to access the Linux1 EC2 instance directly from the internet using its public IP address in AWS.

However, your connection is not successful.

Given the network topology, what can be the issue?

A. There is no connection between VPC A and VPC B.

B. There is no elastic IP address attached to FortiGate in the Security VPC.

C. The Transit Gateway BGP IP address is incorrect.

D. There is no internet gateway attached to the Spoke VPC A.

View Answer

Answer: D

Explanation:

This is because the Linux1 EC2 instance is not accessible directly from the internet using its public IP address in AWS.

An internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between instances in your VPC and the internet. Without an internet gateway, the Linux1 EC2 instance cannot receive or send traffic to or from the internet, even if it has a public IP address assigned to it.

To fix this issue, you need to attach an internet gateway to the Spoke VPC A and configure a route table that directs internet-bound traffic to the internet gateway. You also need to ensure that the Linux1 EC2 instance has a security group that allows inbound and outbound traffic on the desired ports.

: [Internet Gateways – Amazon Virtual Private Cloud] : [Attach an Internet Gateway to Your VPC – Amazon Virtual Private Cloud] : [Security Groups for Your VPC – Amazon Virtual Private Cloud]