Skip to content

docs(instance): updated security groups def#6597

Open
firdevs-a wants to merge 1 commit into
mainfrom
MTA-7214
Open

docs(instance): updated security groups def#6597
firdevs-a wants to merge 1 commit into
mainfrom
MTA-7214

Conversation

@firdevs-a

Copy link
Copy Markdown
Collaborator

Your checklist for this pull request

Description

Please describe what you added or changed.

@firdevs-a firdevs-a self-assigned this Jun 12, 2026
@firdevs-a firdevs-a requested review from a team as code owners June 12, 2026 12:34
@firdevs-a firdevs-a added the status: doc review Waiting for doc team review label Jun 12, 2026
## Stateless security groups

Stateless security groups strictly apply the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance or not. This is useful if you know exactly which ports you will always require for your Instance, e.g. port `22` for SSH. You can make your security group stateless, define a rule to allow traffic on port `22` and block incoming traffic on other ports regardless of whether a connection is initiated from your Instance on this port. [Learn how to use security groups](/instances/how-to/use-security-groups/).
Stateless security groups do not track connection states; they evaluate every single packet entirely on its own merits. If you define a rule to allow inbound traffic on a specific port (e.g., port 22 for SSH), you must also ensure your outbound rules explicitly permit the response traffic to flow back out to the client.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Stateless security groups do not track connection states; they evaluate every single packet entirely on its own merits. If you define a rule to allow inbound traffic on a specific port (e.g., port 22 for SSH), you must also ensure your outbound rules explicitly permit the response traffic to flow back out to the client.
Stateless security groups do not track connection states; they evaluate every single packet based only on its own characteristics. If you define a rule to allow inbound traffic on a specific port (e.g., port 22 for SSH), you must also ensure your outbound rules explicitly permit the response traffic to flow back out to the client.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm suggesting this change only for the sake of non-native speakers of English. Otherwise, there's nothing wrong with the sentence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: doc review Waiting for doc team review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants