Skip to Content
Get StartedSecurity Groups

Security Groups

Security groups control network access to your instances.

Use them to allow only the traffic your application needs.

With an agent (MCP)

Connect the redu MCP, then just ask your agent. Over the MCP, security groups are list-only: list_security_groups lets your agent list and inspect existing groups and their rules. When your agent launches an instance, it opens the SSH and app ports for you automatically, so most setups need no manual rule changes. To add or edit rules yourself, use the console steps below (there is no create-rule MCP tool yet).

1. Create a security group

Go to:

Menu → Network → Security Groups

Then:

  1. Click Create Group
  2. Enter a group name, for example web-frontend
  3. Optionally add a description
  4. Submit the form
Create security group

2. Add rules

Rules define what traffic is allowed.

Go to:

Menu → Network → Security Groups → Actions → Manage Rules

Then:

  1. Click Create Rule
  2. Choose the direction
  3. Choose the protocol
  4. Enter the port
  5. Submit the form
Create security group rule

Rule options

FieldDescription
Directioningress for incoming traffic, egress for outgoing traffic
EtherTypeIPv4 or IPv6
PortSingle port number from 1 to 65535
ProtocolTCP, UDP, or TCP & UDP

Selecting TCP & UDP creates two rules: one for TCP and one for UDP.

Common rules

Use caseDirectionPortProtocol
SSHingress22TCP
HTTPingress80TCP
HTTPSingress443TCP
Custom appingressyour app portTCP or UDP

3. Delete rules

To remove a rule:

  1. Open the rules list for the security group
  2. Open the actions menu for the rule
  3. Click Delete Rule
Delete security group rule

4. Attach security groups to instances

When creating an instance, select one or more security groups.

Rules apply to instances using that group.

Attach security group to instance

Best practices

  • Open only the ports your application needs
  • Allow SSH only when needed
  • Prefer specific rules over broad access
  • Review unused rules regularly

Troubleshooting

Rule creation fails

Check that:

  • Port is between 1 and 65535
  • Required fields are selected
  • Duplicate rules are not being created

Cannot connect to an instance

Check that:

  • The correct security group is attached
  • The rule direction is ingress
  • The correct port is allowed
  • The instance is running

SSH not working

Check that:

  • Port 22 is allowed
  • SSH was enabled during instance creation
  • The correct keypair was selected
Last updated on
NetworkingStorage