Lesson 075 · AWS Learning Path

AWS 075: Allocate, associate, observe, disassociate, and release an Elastic IP

Anil Jalela · Published Sep 8, 2025 · 7 min read

The problem

A team uses Allocate, associate, observe, disassociate, and release an Elastic IP 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 Allocate, associate, observe, disassociate, and release an Elastic IP. 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 paid optional lab;
2. explain allocation;
3. explain association;
4. explain observation;
5. explain reassociation;

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

The lab does not open inbound SSH or HTTP. Public addressing and reachability are separate from route, security group, NACL, host listener, and application controls.

Record cost before allocation and run for less than 15 minutes where practical. Billing data can lag, so resource absence is the immediate cleanup proof.

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 T2 - optional small paid lab. 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, Elastic IP addresses, choose Allocate Elastic IP address, tag it nw-p04-eip, and start a 15-minute timer.
2. Associate it with nw-p04-web-1, compare EC2 Networking and Session Manager address evidence, then disassociate.
3. Release the exact allocation and confirm the Elastic IP inventory no longer contains it.

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

Observe allocation and association without testing an inbound port.

aws ec2 describe-addresses --region ap-south-1 --filters Name=tag:Name,Values=nw-p04-eip --query 'Addresses[].{Allocation:AllocationId,Association:AssociationId,Public:PublicIp,Private:PrivateIpAddress,ENI:NetworkInterfaceId}' --output table

Association fields prove the public/private mapping. They do not prove an application is internet-reachable.

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

This is opt-in T2 work. Record the current public IPv4 hourly price, obtain owner approval, and start a 15-minute timer. If needed, start the retained nw-p04-web-1 instance and wait for both status checks. Allocate exactly one tagged Elastic IP, associate and observe it, disassociate, release, and verify absence. Do not create an inbound rule. Stop the instance after evidence collection unless AWS 076 starts immediately.

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. Does an EIP open a port?

Expected direction: No.

1. Does the guest normally bind the EIP?

Expected direction: No. It normally sees the private address.

1. Can an unassociated EIP charge?

Expected direction: Yes, and current public IPv4 pricing also charges in-use addresses.

1. What proves cleanup?

Expected direction: The allocation is released and absent.

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

• Elastic IP addresses
• Public IPv4 pricing
• EC2 address concepts