mediummultiple choiceObjective-mapped

Your EC2 instances run in private subnets with no NAT gateway. The instances use the AWS SDK to call STS AssumeRole to obtain temporary credentials for other services. Application logs show errors like: "EndpointConnectionError: Could not connect to https://sts.<region>.amazonaws.com".

Which change most directly resolves this while keeping instances private?

Question 1mediummultiple choice
Full question →

Your EC2 instances run in private subnets with no NAT gateway. The instances use the AWS SDK to call STS AssumeRole to obtain temporary credentials for other services. Application logs show errors like: "EndpointConnectionError: Could not connect to https://sts.<region>.amazonaws.com".

Which change most directly resolves this while keeping instances private?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Create an interface VPC endpoint for STS (com.amazonaws.<region>.sts) and associate it with the instance subnets and a security group that allows HTTPS.

Interface endpoints provide private, in-VPC connectivity to AWS APIs like STS without requiring internet access or NAT.

B

Distractor review

Create a gateway VPC endpoint for S3 and route the STS traffic through the S3 endpoint gateway.

Gateway endpoints are for specific services (like S3/DynamoDB) and cannot be used to route STS traffic to the correct API.

C

Distractor review

Open an inbound rule in the instances’ security group to allow outbound HTTPS to the internet CIDR block directly.

Security groups control allowed traffic, but the subnet route table still needs a path. Without NAT/endpoint routing, traffic cannot reach STS.

D

Distractor review

Attach an Internet Gateway to the private subnet route table so the STS API can be reached over public internet.

Adding an Internet Gateway to private subnets contradicts the requirement to keep instances private and increases exposure.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Create an interface VPC endpoint for STS (com.amazonaws.<region>.sts) and associate it with the instance subnets and a security group that allows HTTPS. — When you remove NAT gateway and keep instances in private subnets, AWS public API calls (such as STS) require an in-VPC network path. The correct approach is to create a VPC interface endpoint for STS (com.amazonaws.<region>.sts), then associate it with the subnets and permit HTTPS via the endpoint security group. This provides private connectivity to the STS API without making instances internet-routable. Opening outbound rules or modifying routes to use an Internet Gateway undermines the private-subnet security posture. Why others are wrong: Option B incorrectly attempts to route STS through an S3 gateway endpoint; gateway endpoints are service-specific and do not route arbitrary AWS API traffic. Option C addresses only security group rules; it does not create a route to reach sts.<region>.amazonaws.com. Option D would violate the design constraint by making private subnet instances reachable via public internet routing instead of using endpoints.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.