WESTERN GOVERNORS UNIVERSITY | BSCNE-AWS
E030 - TASK 3
FINAL POST-IMPLEMENTATION REPORT
Secure Hybrid-Cloud Network | Cedarline Distribution Cooperative
DOCUMENT CONTROL DETAILS
Assessment designation Task 3 - proposed final report phase (official third assessment not verified)
Project organization Cedarline Distribution Cooperative - fictional case study
Implementation baseline Task 1 design and Task 2 implementation package, November 2026
Student / instructor [STUDENT NAME] / [INSTRUCTOR NAME]
AWS region / account [APPROVED REGION] / [REDACTED ACCOUNT REFERENCE]
Submission date / revision [DATE] / Version 1.0
Deployment / tests NOT VERIFIED - no live account, GNS3 logs or test records provided
Purpose. This original report is an evidence-ready final review, not a claim of a completed implementation. Its
results are marked PENDING until real artifacts are supplied. It must not be described as WGU-approved,
evaluated, or passed.
Course clarification. WGU publicly describes E030 as an evaluated, working AWS capstone. Student reports
indicate a signed approval form and functionality report, but do not establish a separate official Task 3 rubric. Use
this package as a supplemental final review unless current course instructions say otherwise. [1, 2]
WGU E030 | Task 3 model report | Live evidence not supplied Page 1
,CEDARLINE DISTRIBUTION / CAPSTONE REPORT
Executive Summary
This report defines the post-implementation evaluation and operational handover for the Cedarline Distribution
Cooperative proof-of-concept hybrid network. The previously prepared design connects a GNS3 simulated
headquarters to Amazon Web Services using an IPsec Site-to-Site VPN. Headquarters clients reside in VLAN 10
(10.40.10.0/24); local services reside in VLAN 20 (10.40.20.0/24). The cloud network is 10.70.0.0/16 with two
private /24 subnets and a private EC2 instance hosting a synthetic HTTP service on TCP port 8080.
The AWS resource model is expressed in an original CloudFormation template. A virtual private gateway
terminates a VPN connection with two tunnels, while BGP exchanges the required headquarters routes from a
VyOS customer gateway. The intended permitted application path is a headquarters VLAN 10 client reaching the
private EC2 application over the VPN. Unapproved inbound connections are to be denied by security controls.
The final evaluation examines six planned outcomes: local segmentation; AWS infrastructure; encrypted
connectivity; effective bidirectional routing; authorized and denied access; and a documented troubleshooting
cycle. It additionally reviews automation, security coverage, operational constraints, cost exposure, and evidence
retention.
Current finding: Implementation completion cannot be certified. The Task 2 source files are present, but no
deployed-resource inventory, gateway status logs, client HTTP output, change record, or signed approval has been
supplied. Consequently the project is classified as DOCUMENTED DESIGN / DEPLOYMENT UNVERIFIED, and no live
test may be labeled PASS. This is an intentional distinction between proposed operation and measured operation.
Evaluation disposition
Dimension Assessment as of document preparation
Design completeness Logical topology, nonoverlapping IP allocation and acceptance criteria documented
CloudFormation Original source exists; previous local structural checks reported, not AWS deployment
AWS runtime and tunnel state PENDING - requires live AWS evidence
Functional traffic and negative tests PENDING - requires traffic sent from real approved test hosts
Official assessment alignment PARTIAL - public description verified; exact E030 rubric not obtained
Readiness for final evaluator submission NOT READY until approved environment and required evidence are verified
1. Scope and source-of-truth boundaries
This report inherits the same scope and fictional context as Task 1 and Task 2. It does not change the project to a
production migration or introduce unapproved technologies. The authoritative technical baseline is the actual
deployed environment after instructor approval; this model report is a controlled specification for how to assess
that environment.
Source Reliability and use
WGU public AWS-track course description Official course-level intent: working deployed AWS evaluation
[1]
WGU E030 | Task 3 model report | Live evidence not supplied Page 2
, CEDARLINE DISTRIBUTION / CAPSTONE REPORT
Source Reliability and use
June 2026 E030 student discussion [2] Useful submission anecdote; not an official rubric
Task 1 original design Proposed VLANs, AWS CIDRs, application and acceptance standards
Task 2 technical PDF and YAML Implementation runbook and IaC source; not proof of deployed operations
Actual AWS/GNS3 exports and test logs Required decisive evidence after deployment
2. Project baseline and configuration management
2.1 Baseline resource inventory
Resource Expected baseline Required actual reference
HQ client subnet VLAN .40.10.0/24 [GNS3 client hostname, IP, config]
HQ service subnet VLAN .40.20.0/24 [GNS3 server hostname, IP, config]
Customer gateway VyOS / AS 65010 / approved public VPN endpoint [router version, interface, sanitized config]
AWS network VPC 10.70.0.0/16 [VPC ID / AWS Region]
Private subnets 10.70.10.0/24, 10.70.20.0/24 [Subnet IDs / AZs]
Virtual gateway VGW / AWS-side AS 64512 [VGW ID]
VPN connection One AWS connection with two tunnels [VPN ID / both tunnel states]
Private application EC2, HTTP TCP/8080, no public IPv4 [Instance ID / private IP / AMI]
CloudFormation cedarline-e030 stack [Stack ID / deployment events]
2.2 Change-control requirement
Maintain a signed or timestamped change log identifying every modification from the approved diagram, including
the reason, approving contact if applicable, affected AWS resources, test impacts, and rollback steps. Disclose
substantive deviations rather than silently revising the proposal to match a later build.
WGU E030 | Task 3 model report | Live evidence not supplied Page 3
E030 - TASK 3
FINAL POST-IMPLEMENTATION REPORT
Secure Hybrid-Cloud Network | Cedarline Distribution Cooperative
DOCUMENT CONTROL DETAILS
Assessment designation Task 3 - proposed final report phase (official third assessment not verified)
Project organization Cedarline Distribution Cooperative - fictional case study
Implementation baseline Task 1 design and Task 2 implementation package, November 2026
Student / instructor [STUDENT NAME] / [INSTRUCTOR NAME]
AWS region / account [APPROVED REGION] / [REDACTED ACCOUNT REFERENCE]
Submission date / revision [DATE] / Version 1.0
Deployment / tests NOT VERIFIED - no live account, GNS3 logs or test records provided
Purpose. This original report is an evidence-ready final review, not a claim of a completed implementation. Its
results are marked PENDING until real artifacts are supplied. It must not be described as WGU-approved,
evaluated, or passed.
Course clarification. WGU publicly describes E030 as an evaluated, working AWS capstone. Student reports
indicate a signed approval form and functionality report, but do not establish a separate official Task 3 rubric. Use
this package as a supplemental final review unless current course instructions say otherwise. [1, 2]
WGU E030 | Task 3 model report | Live evidence not supplied Page 1
,CEDARLINE DISTRIBUTION / CAPSTONE REPORT
Executive Summary
This report defines the post-implementation evaluation and operational handover for the Cedarline Distribution
Cooperative proof-of-concept hybrid network. The previously prepared design connects a GNS3 simulated
headquarters to Amazon Web Services using an IPsec Site-to-Site VPN. Headquarters clients reside in VLAN 10
(10.40.10.0/24); local services reside in VLAN 20 (10.40.20.0/24). The cloud network is 10.70.0.0/16 with two
private /24 subnets and a private EC2 instance hosting a synthetic HTTP service on TCP port 8080.
The AWS resource model is expressed in an original CloudFormation template. A virtual private gateway
terminates a VPN connection with two tunnels, while BGP exchanges the required headquarters routes from a
VyOS customer gateway. The intended permitted application path is a headquarters VLAN 10 client reaching the
private EC2 application over the VPN. Unapproved inbound connections are to be denied by security controls.
The final evaluation examines six planned outcomes: local segmentation; AWS infrastructure; encrypted
connectivity; effective bidirectional routing; authorized and denied access; and a documented troubleshooting
cycle. It additionally reviews automation, security coverage, operational constraints, cost exposure, and evidence
retention.
Current finding: Implementation completion cannot be certified. The Task 2 source files are present, but no
deployed-resource inventory, gateway status logs, client HTTP output, change record, or signed approval has been
supplied. Consequently the project is classified as DOCUMENTED DESIGN / DEPLOYMENT UNVERIFIED, and no live
test may be labeled PASS. This is an intentional distinction between proposed operation and measured operation.
Evaluation disposition
Dimension Assessment as of document preparation
Design completeness Logical topology, nonoverlapping IP allocation and acceptance criteria documented
CloudFormation Original source exists; previous local structural checks reported, not AWS deployment
AWS runtime and tunnel state PENDING - requires live AWS evidence
Functional traffic and negative tests PENDING - requires traffic sent from real approved test hosts
Official assessment alignment PARTIAL - public description verified; exact E030 rubric not obtained
Readiness for final evaluator submission NOT READY until approved environment and required evidence are verified
1. Scope and source-of-truth boundaries
This report inherits the same scope and fictional context as Task 1 and Task 2. It does not change the project to a
production migration or introduce unapproved technologies. The authoritative technical baseline is the actual
deployed environment after instructor approval; this model report is a controlled specification for how to assess
that environment.
Source Reliability and use
WGU public AWS-track course description Official course-level intent: working deployed AWS evaluation
[1]
WGU E030 | Task 3 model report | Live evidence not supplied Page 2
, CEDARLINE DISTRIBUTION / CAPSTONE REPORT
Source Reliability and use
June 2026 E030 student discussion [2] Useful submission anecdote; not an official rubric
Task 1 original design Proposed VLANs, AWS CIDRs, application and acceptance standards
Task 2 technical PDF and YAML Implementation runbook and IaC source; not proof of deployed operations
Actual AWS/GNS3 exports and test logs Required decisive evidence after deployment
2. Project baseline and configuration management
2.1 Baseline resource inventory
Resource Expected baseline Required actual reference
HQ client subnet VLAN .40.10.0/24 [GNS3 client hostname, IP, config]
HQ service subnet VLAN .40.20.0/24 [GNS3 server hostname, IP, config]
Customer gateway VyOS / AS 65010 / approved public VPN endpoint [router version, interface, sanitized config]
AWS network VPC 10.70.0.0/16 [VPC ID / AWS Region]
Private subnets 10.70.10.0/24, 10.70.20.0/24 [Subnet IDs / AZs]
Virtual gateway VGW / AWS-side AS 64512 [VGW ID]
VPN connection One AWS connection with two tunnels [VPN ID / both tunnel states]
Private application EC2, HTTP TCP/8080, no public IPv4 [Instance ID / private IP / AMI]
CloudFormation cedarline-e030 stack [Stack ID / deployment events]
2.2 Change-control requirement
Maintain a signed or timestamped change log identifying every modification from the approved diagram, including
the reason, approving contact if applicable, affected AWS resources, test impacts, and rollback steps. Disclose
substantive deviations rather than silently revising the proposal to match a later build.
WGU E030 | Task 3 model report | Live evidence not supplied Page 3
