chore: tidiness

This commit is contained in:
Payton Bates committed 2026-10-05 14:49:39 -04:00
1 parent 916ee92f90
commit 02189faab0
3 files changed
+8 -24

No files matched your search

+6 -21
View File
@@ -17,8 +17,7 @@ assigned address can change after the instance is stopped and started.
Victor created the paid AWS account for the group and configured a monthly
budget alert. No credits were reported. IAM Identity Center provides separate
Victor and Payton identities in the developers group, assigned an EC2 permission
set using \texttt{AmazonEC2FullAccess}. Victor's portal and EC2-console access
were verified; Payton's independent sign-in was not captured. Root remains the
set using \texttt{AmazonEC2FullAccess}. Root remains the
owner's administrative identity; a separate administrator role was not created
and MFA setup was deferred. The budget is an alert, not a spending cap.
@@ -27,9 +26,9 @@ and MFA setup was deferred. The budget is an alert, not a spending cap.
Instance name & \texttt{ssw590-group-web}\\
Region & N. Virginia (\texttt{us-east-1})\\
Instance type & \texttt{t3.micro}\\
Operating system & Ubuntu 26.04 LTS, amd64 (verified with \texttt{/etc/os-release} and \texttt{uname -m})\\
Operating system & Ubuntu 26.04 LTS, amd64\\
Networking & Default VPC, public IPv4 enabled\\
Inbound SSH & TCP 22 restricted to Victor's detected IP (\texttt{100.8.28.98/32} at setup)\\
Inbound SSH & TCP 22 restricted to Victor's detected IP\\
Inbound website & TCP 80 from \texttt{0.0.0.0/0}\\
Storage & Launch configuration used an 8 GiB gp3 root volume with encryption and delete-on-termination selected\\
Metadata & IMDSv2 required, confirmed in instance summary\\
@@ -121,7 +120,7 @@ The terminal screenshot shows container \texttt{70ed56f7fae8} running, the
state and the Blue and Red outcomes. These figures are supplied execution
evidence, not generated illustrations.
\begin{figure}[p]
\begin{figure}[H]
\centering
\includegraphics[width=\linewidth]{figures/aws-container.png}
\caption{EC2 container status, startup logs, and successful local HTTP check.}
@@ -133,28 +132,14 @@ evidence, not generated illustrations.
\includegraphics[width=\linewidth]{figures/aws-buttons-blue.png}
\caption{Public AWS website after clicking Blue.}
\label{fig:aws-blue}
\end{figure}
\begin{figure}[p]
\centering
\vspace{1em}
\includegraphics[width=\linewidth]{figures/aws-buttons-red.png}
\caption{Public AWS website after clicking Red.}
\label{fig:aws-red}
\end{figure}
\clearpage
\section{Problems and Resolution}
The first repository update failed with a missing OpenPGP signing-key error.
Victor downloaded Docker's key again, set its file permissions, checked the
\texttt{Signed-By} path, and repeated the update. Installation then succeeded.
The exact cause of the initial missing-key state was not established.
The Ubuntu image selected was 26.04 rather than the initially planned 24.04.
The actual OS and architecture were checked before using Docker's matching
\texttt{resolute} repository. A Compute Optimizer access message appeared in
the instance summary; it did not prevent the EC2 deployment and no extra
permissions were added for that optional feature.
\section{Ownership and Continued Operation}
Victor owns the AWS account and billing responsibility; both authors share the
course project. Compute, storage, and public IPv4 usage are chargeable under