When setting up a cloud server, understanding basic configuration parameters and how to manage them through the console is essential. This guide covers core concepts like security groups and provides actionable steps for configuring network access controls.
Setting Up Your First Cloud Server Instance
This is a hypothetical setup scenario, not a record of a completed deployment. An author preparing a short illustrated guide sits down with a blank configuration form and three draft items for the first chapter. One item is titled “Basic Parameters for a First Instance,” a second is called “What the Management Panel Shows,” and a third is labeled “Choosing an Image Before Launch.” The form’s own headers are deliberately plain: Instance Label, Operating System Image, Data Center Region, Compute Size, Storage Volume, Access Network, Administrator Account, and Public Access Toggle.
The author fills two clearly invented rows to show how the headers work. Row one, labeled Learning Sandbox, pairs a Linux image with a nearby region, a small compute size, a modest system disk, a shared access network, a named administrator account, and public access switched off. Row two, labeled Documentation Preview, pairs the same image family with a second region, a larger compute size, a separate data volume, a dedicated access network, and public access switched on. Each row stays within the same eight fields, so a reader can see where a choice belongs rather than memorizing a list.
For the third item, the author works through one explicit trade-off. A general-purpose image with a familiar package set is chosen over a minimal image carrying only the essentials, because the guide’s screenshots depend on standard tools already being present; the minimal image would save space but force extra installation steps the chapter does not cover. A short note beside the entry explains that images are revisited when the provider’s catalog changes, without asserting what any specific catalog currently offers.
The panel chapter is drafted from field descriptions rather than screenshots: it lists where start, stop, restart, console access, and delete actions sit, and what each action is expected to change. The author adds no claim that a button worked, no timing figures, and no statement about what an external page will display. These are self-made explanatory examples meant to keep the form readable before the later sections explain how a reader should prepare their own parameter sheet.
Understanding Security Groups as Virtual Firewalls
Alibaba Cloud ECS security groups act as virtual firewalls, using rules to provide network isolation and access control. Two example rules with separate directions are described on the page: an inbound rule allows a specific IP to reach an instance over SSH on port 22, while an outbound rule denies the instance access to a known risky IP.1
Security group rules are stateful, so only inbound rules need configuring and corresponding outbound response traffic is automatically allowed. Under the same priority, deny rules take effect first, and some specific traffic is allowed by default.1
You can extend the same invented configuration sheet with a short port-permission row and then draft the paragraph yourself. Add a header such as “Allowed source, port, purpose,” followed by an example value like “office subnet, 443, web access,” and a second line for “admin workstation, 22, SSH.” This is a hypothetical entry, not a record of a completed setup. Your draft can say: “This rule permits HTTPS access from the office network.” Then revise it to name the consequence: “Only the office network may reach HTTPS; other sources are denied.” That revision shows the security boundary more plainly than the original.
Consider noting one rejected alternative beside the row, such as opening port 22 to every address for convenience. You might write why you did not choose it: broad access would expose remote login beyond the intended administrator group. The choice remains yours; the example simply demonstrates how a selected value and a rejected value can sit side by side without claiming a real deployment.
For the next step, carry the same method into your security-group paragraph: pair each allowed source with its port and purpose, state what the rule blocks, and mark the whole entry clearly as an author's illustrative example.
Configuring Inbound Rules for Remote Access
Alibaba Cloud's ECS security groups act as a virtual firewall for cloud instances. The documented example permits remote management through one inbound rule that allows a specific address to reach the instance over SSH on port 22, paired with an outbound rule denying access to a known risky address.1
The console's quick configuration offers common ports and protocols as checkboxes; selecting one allows all IP addresses in 0.0.0.0/0 to reach the target port. The source notes that quick configuration during instance purchase does not support fine-grained rule settings, so rules can be adjusted after the instance is created. It also advises restricting SSH (22), RDP (3389), and panel ports to trusted fixed IPs rather than 0.0.0.0/0 or ::/0, while 80 and 443 may be opened publicly as needed. Rules are stateful, so only inbound rules need configuration, and under the same priority a deny rule takes effect first. The source suggests cloning a security group and validating changes in a test environment before adjusting production rules.1
For the next step, return to your invented configuration sheet and turn the port-permission row into a short set of inbound rules, one rule per line. You can reuse the header “Allowed source, port, purpose, what it blocks” and fill it for the learning sandbox only. A sample value might read: office network range, port 22, remote administration, all other addresses. Beside it, you might add a second line for a web preview: any address, port 443, viewing the test page, unencrypted traffic.
You can then decide which rules belong to the same sheet and which should stay in a separate draft table. If you are comparing current and archived notices, the same fields still work: for a current entry, write the active source range and its purpose; for an archived one, write the old range, mark it retired, and note the date it stopped applying. Keeping both in one place helps you see what changed without mixing the two.
Before you write the paragraph, choose one rejected alternative and record why. For example, you might consider allowing port 22 from every address, then decide against it because the purpose applies only to your office. Writing that reason in the row makes the paragraph more specific. You can also leave one cell blank and mark it “to confirm” rather than guessing; that keeps the example honest about what you have not decided.
Finally, draft the paragraph around those two filled rows, naming the source, port, and purpose for each and stating what the rule leaves closed. Keep the wording plain and your own; the rows are a writing aid, not a record of any real setup.
Managing Outbound Traffic and Risk Prevention
The Alibaba Cloud ECS security group guide describes an outbound-rule example that denies an instance access to a known risky IP address, paired with an inbound rule permitting a specific IP to reach the instance over SSH on port 22. To add an outbound rule through the API, the guide lists the AuthorizeSecurityGroupEgress call; outbound rules can be modified with ModifySecurityGroupEgressRule and removed with RevokeSecurityGroupEgress.1
The same guide advises limiting SSH, RDP, and panel ports to trusted IPs rather than leaving them open to all addresses, and states that under equal priority a deny rule takes effect first, with certain traffic allowed by default. It also recommends avoiding direct changes to production security groups, instead cloning the group and validating changes in a test environment first.1
Take your invented configuration sheet and add one outbound column beside the inbound notes you already drafted. For the Learning Sandbox row, you can fill the cell with a single line such as “outbound: default policy, destination all, purpose package updates,” then add a deliberately narrow second line for a fictional reporting job: “outbound: destination one named host, port stated in the purpose field, purpose status upload.” Keep that second host as a placeholder name, since the point is to practise recording the destination and its reason, not to settle a real address.
You might then draft one short sentence of rationale under each outbound line. For the open default policy, an example is that a learning sandbox prioritises convenience and expects the reader to revisit the setting later; for the narrowed reporting job, an example is that limiting the destination keeps the draft honest about what the job actually needs. Both are author demonstrations, so mark them in your notes as assumptions rather than findings.
Next, consider one rejected outbound alternative and write it beside the row: leaving every destination open for the reporting job because it was quicker to describe. You can note the reason you set it aside, then decide whether that rejected line stays in the same sheet or moves to a separate draft table, depending on whether you are comparing current and archived entries.
Best Practices for Port Authorization and Priority
When configuring inbound authorization, Alibaba Cloud's documentation recommends restricting SSH (port 22), RDP (port 3389), and panel ports to trusted IP addresses. HTTP (80) and HTTPS (443) may be opened to the public as needed. The documentation's listed guidance pairs port 22 with TCP for Linux remote connection and port 3389 with TCP for Windows remote desktop, advising an office network or fixed public IP rather than long-term use of 0.0.0.0/0.1
On rule priority, the page states that at the same priority level, deny rules take effect first, and that for some specific network traffic the security group grants access by default. It further notes that when an instance is associated with multiple security groups, a lower-priority allow rule is overridden by a higher-priority deny rule. For changes, the documentation advises cloning the security group and verifying in a test environment before adjusting production rules.1
You can take the two filled rows on your invented configuration sheet and turn the port-permission notes into a short priority sequence. Beside each allowed source, port, and purpose, add a column headed “Priority” and fill an example value such as 1 for the learning sandbox’s administrative access and 3 for a reporting job’s outbound destination. You might then write one sentence explaining the order, for instance that narrower sources sit above broader ones because they are easier to review later.
Consider keeping a separate draft table for rules you are unsure about rather than blending them into the main sequence. A row labeled “Deferred” with the source, port, and reason for postponement lets you move it into the priority list once the purpose is clear. You can decide which table an entry belongs to by asking whether you can already name its purpose and what it leaves closed.
You might also add one rejected alternative beneath the sequence, such as allowing port 22 from every address, with a brief note that it widens exposure beyond what the learning sandbox needs. This keeps the reasoning visible without turning the draft into a finished claim.
For the next step, return to your port-permission paragraph and place the priority numbers in the same order as the rules appear, so the prose and the sheet read consistently.
Verifying and Modifying Existing Security Group Settings
In the ECS console, open the security group details page for the target group and use the access rules area to manage existing rules. To modify, locate the rule and choose edit in its operation column; to remove it, choose delete. Rules are stateful, so inbound configuration alone suffices because the system automatically permits corresponding outbound response traffic.1
Before changing a production security group, best practice is to clone the group, validate the adjusted rules in a test environment, and then change the online rules.1
Take the security-group section in your draft and replace any vague claim that traffic is “restricted” with a paired sentence naming the allowed source, the port, and the purpose. You can mark that pair as a hypothetical example first: source “office network range,” port 22, purpose “administration,” then write what the rule leaves closed. This keeps the prose aligned with the port-permission row you already drafted.
If you are describing an archived notice alongside a current one, reuse exactly those three fields for both entries. Write the current entry as source “office range,” port 443, purpose “dashboard access,” and the archived one as source “single test address,” port 22, purpose “temporary setup,” noting which entry is retired. You might add a short line beside each titled “Status” so the two do not blur together.
You can also draft one rejected alternative in plain words and keep it separate from the confirmed rows. A possible example is allowing port 22 from every address for convenience, with a note that it widens access beyond the intended administrators. Consider recording why you set it aside rather than deleting it, so the paragraph shows your reasoning.
For the closing sentence, you might state which setting you would change first if the purpose shifted, such as narrowing the source once setup ends. Next, check that the priority order in your prose matches the order of the rows on your sheet.
Frequently asked questions
How can I add a port-permission row and example values to an invented configuration sheet?
You can extend the same invented configuration sheet with a short port-permission row and then draft the paragraph yourself. Add a header such as “Allowed source, port, purpose,” followed by an example value like “office subnet, 443, web access,” and a second line for “admin workstation, 22, SSH.”
How should I decide which rules belong on the same sheet and which stay in a separate draft table?
You can then decide which rules belong to the same sheet and which should stay in a separate draft table. If you are comparing current and archived notices, the same fields still work: for a current entry, write the active source range and its purpose; for an archived one, write the old range, mark it retired, and note the date it stopped applying.
What should I add beside the allowed source, port, and purpose to turn my port-permission notes into a priority sequence?
You can take the two filled rows on your invented configuration sheet and turn the port-permission notes into a short priority sequence. Beside each allowed source, port, and purpose, add a column headed “Priority” and fill an example value such as 1 for the learning sandbox’s administrative access and 3 for a reporting job’s outbound destination.