---
title: "Discussion on \"Why I Stopped Using Bastion Hosts for EC2 Access & You should too\" | Hashnode"
description: "Discussion on \"Why I Stopped Using Bastion Hosts for EC2 Access & You should too\". How VPC Endpoint internally resolved DNS to allow private access to AWS Services\nWe’ve all been there, trying to connect to an EC2 instance in a private subnet, only to end up fighting in a web of NAT Gateways, route tables, and Bastion Hosts. You as..."
url: "https://hashnode.com/posts/why-i-stopped-using-bastion-hosts-for-ec2-access-and-you-should-too/6877881aed38a3c7d9b4975f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why I Stopped Using Bastion Hosts for EC2 Access & You should too](https://awsdocs.hashnode.dev/why-i-stopped-using-bastion-hosts-for-ec2-access-and-you-should-too?utm_source=hashnode&utm_medium=feed)

How VPC Endpoint internally resolved DNS to allow private access to AWS Services We’ve all been there, trying to connect to an EC2 instance in a private subnet, only to end up fighting in a web of NAT Gateways, route tables, and Bastion Hosts. You as...

Jul 16, 2025 · 5 min read · awsdocs.hashnode.dev  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#bastion-hosts](https://hashnode.com/tag/bastion-hosts)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Aakash Choudhary](https://hashnode.com/@ifaakash)

@ifaakash · India

  
[View profile](https://hashnode.com/@ifaakash)

DevOps Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
