E030 is the four-unit capstone of the AWS version of WGU's Bachelor of Science, Cloud and Network Engineering. It follows the same structure as the standard capstone, but all tasks are completed in an AWS environment.
The guidebook says students choose from a fixed set of workplace tasks and submit them in a working, deployed environment. Tasks use either the AWS command line interface or web-based tools and standard AWS platform components, and an evaluator checks the results by inspecting configurations or testing services.
Students who are fluent in general networking sometimes stumble on AWS specifics, such as how route tables, security groups and gateways interact. The capstone rewards those who understand how the pieces connect.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course | E030, BSCNE-AWS Capstone Project |
| Competency units | 4 |
| Level | Undergraduate capstone |
| Program | BS Cloud and Network Engineering, AWS |
| Platform | AWS CLI or web-based tools and standard AWS components |
What E030 Covers
| Competency (WGU wording, summarized) | What it asks of you |
|---|---|
| Deploy a hybrid network environment combining an on-premises network and a cloud network in AWS | Build and connect both sides using AWS |
| Design a hybrid network environment in AWS | Plan address ranges, connections and security |
| Troubleshoot connectivity within a hybrid network in AWS | Diagnose and repair faults |
Key Concepts Explained
The Pieces of an AWS Network
A virtual private cloud (VPC) contains subnets. Route tables decide where traffic goes, gateways connect the VPC to the internet or to an on-premises network, and security groups and network access control lists filter traffic. Understanding how these interact is central to the capstone.
Stateful and Stateless Filters
Security groups are stateful: return traffic for an allowed connection is permitted automatically. Network access control lists are stateless, so rules must allow traffic in both directions. This difference explains many connectivity faults.
Illustration: A server in a private subnet cannot be reached from the office over a VPN. The tunnel is up and the security group allows the office range. The subnet's route table, however, has no route back to the office range, so replies are lost. Adding that route, or enabling route propagation if it is used, restores connectivity.
Documenting for an Evaluator
Name resources clearly, tag them, and keep a note of configuration choices and the tests that prove each requirement is met.
Typical Assignments and How to Approach Them
| Task element | What it tests | How to approach it |
|---|---|---|
| Deploying in AWS | Working configuration | Build step by step and test after each stage |
| Design | Planning in an AWS context | Show ranges, subnets, routes and filters in a diagram |
| Troubleshooting | Systematic method | Check routes, filters and gateways in order |
An AWS Connectivity Checklist
When traffic does not flow, work through the same list each time. This habit is faster than guessing, and it makes your troubleshooting notes easy to follow.
| Check | Question |
|---|---|
| Link | Is the connection between the sites up? |
| Routes | Do both sides have routes to each other's ranges? |
| Filters | Do security groups and access lists allow the traffic both ways? |
| Service | Is the target actually listening and healthy? |
Choosing and Scoping Your Task
Read each available task against the rubric and choose the one where you can demonstrate deployment, design and troubleshooting clearly in AWS. A smaller build that works and is well documented is safer than a broad one that is only partly finished.
Write a short scope before you start: networks and ranges, how the on-premises side connects, which filters apply and how you will test. Because you may use the command line or the console, pick the approach you can repeat reliably and keep notes of the commands or steps. At the end, confirm that every resource the evaluator needs is running and reachable.
Weak and Strong Troubleshooting Notes
The evaluator looks for order and evidence in how you diagnose faults.
| Weak | Stronger |
|---|---|
| The server was not reachable so I rebuilt it. | The tunnel was established and the security group allowed the office range. The subnet route table had no route back to the office, so replies were dropped. I added the route and confirmed with a test from the office. |
Rebuilding rarely solves a routing fault. Working through link, routes, filters and service finds the cause faster.
Where Students Get Stuck
- Missing return routes. One-way routing is the classic cause of silent failures.
- Stateless filter rules. Remember the reply direction.
- Costs left running. Keep an eye on resources and clean up after evaluation.
- Insufficient evidence. Record tests, not just configuration.
Study Tips for E030
- Practice building a small VPC with a tunnel before the real task.
- Learn both the command line and the console way of doing the same step.
- Use tags and names that explain purpose.
- Verify each requirement against the rubric before submitting.
How We Help with E030
Send the task options and rubric. A tutor can help you plan the design, explain AWS networking concepts and review your documentation. We do not build, access or log in to your AWS environment: the deployed work must be your own, completed under WGU's academic integrity policy.
GradeEssays is independent of Western Governors University and of Amazon Web Services. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Get Your AWS Capstone Plan Clear
Share the task, your design notes and feedback. We help you organize documentation and test evidence.
Start My E030 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
The guidebook lists 4.
AWS, using the AWS CLI or web-based tools and standard platform components.
An evaluator inspects configurations or tests services in the working environment.
The competencies are the same in structure, but all work is in AWS.
None is stated in the course description.
Yes. We check structure and reasoning, but we do not access or build your environment.