---
title: "Discussion on \"Bridging Legacy Ports in AWS: \" | Hashnode"
description: "Discussion on \"Bridging Legacy Ports in AWS: \". Exposing Port 20280 on Standard HTTP Port 80"
url: "https://hashnode.com/posts/bridging-legacy-ports-in-aws/699b280f8afcd364f5fadfa7"
---

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

Discussion

# [Bridging Legacy Ports in AWS:](https://cloudops-solutions.hashnode.dev/bridging-legacy-ports-in-aws?utm_source=hashnode&utm_medium=feed)

Exposing Port 20280 on Standard HTTP Port 80

Feb 22 · 4 min read · cloudops-solutions.hashnode.dev  
Read the article

-   [#aws-services](https://hashnode.com/tag/aws-services)
-   [#applicationloadbalancer](https://hashnode.com/tag/applicationloadbalancer)
-   [#linux-for-devops](https://hashnode.com/tag/linux-for-devops)
-   [#iptables](https://hashnode.com/tag/iptables)
-   [#port-forwading](https://hashnode.com/tag/port-forwading)

## Written by

[Pratiksha kadam](https://hashnode.com/@pinacolada)

@pinacolada · Pune Maharashtra India

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

Technical Support Engineer @NewWings IT

As a associate system administrator I worked on Redhat Linux servers, including user management, permissions, services, and performance monitoring Automated routine administrative tasks using Bash scripting and cron jobs, reducing manual effort by ~30% I am aws certified sysops administrator and Google Certified Cloud Engineer. Determined to transition my career into cloud architect /Cloud Support role

## Responses

Markdown supported · ⌘↵ to post

No responses yet.