Lesson 058 · AWS Learning Path

AWS 058: Security groups

Anil Jalela · Published Aug 22, 2025 · 7 min read

The problem

A team uses Security groups as a label or Console setting without proving the identity, scope, behavior, failure boundary, cost, or operational result. The configuration appears complete but the real requirement remains untested.

Final outcome

The learner will inspect, explain, test, and document Security groups. The submission must connect the Console and CLI view to the same AWS control, state what the evidence proves, diagnose one likely failure, and make a requirement-based architecture decision.

Learning outcomes

You will be able to:

1. explain a security group is a stateful virtual firewall;
2. explain rules allow only;
3. explain inbound and outbound are separate starts;
4. explain references express identity;
5. explain rules can use cidrs, prefix lists, or groups;

1. distinguish successful configuration from successful workload behavior;
2. preserve redacted evidence and complete the stated cleanup or retention decision.

Mental model

requirement
   -> identity and permission
   -> account, Region, and resource scope
   -> configuration or request
   -> observable state
   -> workload result
   -> failure evidence
   -> cleanup or controlled retention

Never begin with a create button or a copied command. Start with the result that must be proven and the boundary that must remain protected.

Core facts

How to reason about it

Model rules by application relationships: load-balancer group to application port, application group to database port, and controlled egress to required endpoints. Avoid rules that expose management ports to 0.0.0.0/0 or ::/0 and avoid relying on the default outbound-all rule without review.

Use the following decision table as a starting point, then change the answer when the scenario changes.

Prerequisites, permissions, Region, and cost

Run this lesson as the approved non-root course identity. Begin with aws sts get-caller-identity, confirm the private account record, and set the fixed project Region before any regional query. IAM resources are global within an account, while STS endpoints and the services reached by an identity can be regional.

Use only the read or change actions required for this lesson. An AccessDenied result is evidence to analyse, not permission to switch to root or attach AdministratorAccess. Record the action, resource, principal type, request context, and smallest justified correction.

The listed cost tier is T0 - no resource creation. Free Tier eligibility and credits are account-specific. Before a mutating lab, identify every resource that can charge, estimate its duration, start a timer, and write the reverse cleanup order. A budget reports cost after billing data arrives and is not a real-time stop control.

AWS Management Console method

1. Open EC2 Security Groups and select every group attached to the target network interface.
2. Inspect inbound and outbound rules, including IPv4, IPv6, prefix-list, and security-group references.
3. Open the EC2 instance Networking tab to confirm which interface and combined groups actually receive the rules.

For every step record the service page, selected account and Region, exact object, visible state, and why that state matters. A Console label or green status is not enough unless it is tied to the final workload outcome.

AWS CLI or API evidence

Inspect all groups attached to the network interface because their allows combine.

aws ec2 describe-network-interfaces --network-interface-ids eni-0123456789abcdef0 --query 'NetworkInterfaces[0].Groups'
aws ec2 describe-security-groups --group-ids sg-0123456789abcdef0

Evaluate protocol, port range, IPv4 and IPv6 sources, prefix lists, and referenced groups. A rule in any attached group can permit the traffic.

Before running the command, replace every placeholder, explain each option, and decide whether the operation is read-only or mutating. Capture the exit code immediately. Redact account IDs, ARNs, public addresses, request identifiers, and personal data before sharing.

The CLI and Console are clients of AWS APIs. Matching state across them increases confidence, but neither substitutes for data-plane or application verification.

Practical work

Create p04-security-group-plan.md for nw-p04-ec2-sg. The approved standard lab has no inbound rules because Session Manager is the administration path. Record the reviewed outbound needs for DNS, HTTPS to Systems Manager and package endpoints, and the project evidence. Compare stateful return behavior with the stateless NACL and reject 0.0.0.0/0 SSH.

The evidence package must include:

• non-root principal type, account verified privately, and Region;
• exact intended and observed state;
• one Console observation and the matching CLI or API result;
• one successful result and one denied, failed, or counterexample result;
• what each result does not prove;
• cost state and elapsed lab time;
• cleanup evidence or a named retained-state owner and next lesson.

Verification standard

Use three levels of proof:

1. Control plane: the object or policy exists with the intended configuration.
2. Data plane or behavior: the request, packet, session, storage path, or application does what the requirement states.
3. Operations: monitoring, failure diagnosis, cost, ownership, and cleanup are known.

A control-plane response can precede final readiness. Use waiters or state polling where supported, then test the actual behavior. If a request times out, do not assume it failed. Inspect state and use documented idempotency before retrying a mutation.

Troubleshooting method

Keep the original symptom and timestamp. State one hypothesis, make one reversible change, repeat the original test, and record rollback. Never open a management port to the world, expose credentials, disable TLS verification, format an unknown disk, or add broad permissions as a generic fix.

Architecture and certification decisions

Professional-level questions provide competing valid features. Identify the requirement that decides between them: human or workload identity, same-account or cross-account access, regional or zonal scope, stateful or stateless filtering, durable or ephemeral data, latency, RTO/RPO, cost, or operational ownership.

Explain why the selected option fits and why each plausible alternative fails one stated requirement. Do not rely on feature memorization or reproduce protected certification questions.

Knowledge check

1. Do security groups process numbered rules in order?

Expected direction: No. All applicable allow rules are evaluated together.

1. Must return ephemeral ports be added for a tracked allowed connection?

Expected direction: Not in the reverse security-group direction; state tracking permits the response. NACLs remain stateless.

1. Does referencing a security group import its rules?

Expected direction: No. It selects private addresses of interfaces associated with that group in supported paths.

1. Can a security group explicitly deny one bad source?

Expected direction: No. Use another suitable control for explicit deny.

Cost, cleanup, and retained state

Retain only the state explicitly required by the next P04 lesson and record it in the private resource ledger.

Cleanup evidence includes the final state query, not only a successful delete response. Search related resources, other Regions used by the lab, retained storage, public IPv4 addresses, logging destinations, and service-managed dependencies. Schedule a later billing review because cost data can lag.

Completion gate

Pass when the practical artifact explains the real problem, matches Console and CLI evidence, answers every knowledge check, diagnoses one failure without broadening access, records cost, and proves cleanup or approved retention. The learner must defend one decision orally and name the requirement that would change it.

Official sources

• Control traffic with security groups
• Security group rule referencing