@@ -73,47 +73,91 @@ <h1>Field Notes</h1>
7373 < section class ="field-notes-list ">
7474 < div class ="container ">
7575
76- < article class ="field-note-card ">
76+ < article class ="field-note-card ">
77+
78+ < div class ="field-note-thumbnail ">
79+
80+ < a href ="/field-notes/organising-domains-dns-and-ssl-in-aws.html ">
81+
82+ < img
83+ src ="../assets/images/field-notes/organising-domains-dns-and-ssl-in-aws/domain-redirect-architecture.png "
84+ alt ="AWS domain redirect architecture diagram using Route 53, CloudFront, ACM and S3 redirect buckets ">
85+
86+ </ a >
87+
88+ </ div >
89+
90+ < div class ="field-note-content ">
91+
92+ < p class ="field-note-meta ">
93+ AWS • DNS • Networking
94+ </ p >
95+
96+ < p class ="field-note-date ">
97+ Published 5 June 2026
98+ </ p >
99+
100+ < h2 >
101+ < a href ="/field-notes/organising-domains-dns-and-ssl-in-aws.html ">
102+ Organising Domains, DNS and SSL in AWS
103+ </ a >
104+ </ h2 >
105+
106+ < p class ="field-note-summary ">
107+ How I consolidated Cliffable domains into a dedicated AWS account and built HTTPS redirects for secondary
108+ domains using Route 53, CloudFront, ACM and S3.
109+ </ p >
110+
111+ < a href ="/field-notes/organising-domains-dns-and-ssl-in-aws.html " class ="field-note-link ">
112+ Read note →
113+ </ a >
77114
78- < div class =" field-note-thumbnail " >
115+ </ div >
79116
80- < a href =" /field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html " >
117+ </ article >
81118
82- < img
83- src ="../assets/images/field-notes/when-a-1gb-lightsail-instance-wasnt-enough/cpu-spike-before-instance-upgrade.png "
84- alt ="AWS Lightsail CPU overview showing a spike before the instance upgrade ">
119+ < article class ="field-note-card ">
85120
86- </ a >
121+ < div class =" field-note-thumbnail " >
87122
88- </ div >
123+ < a href =" /field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html " >
89124
90- < div class ="field-note-content ">
125+ < img
126+ src ="../assets/images/field-notes/when-a-1gb-lightsail-instance-wasnt-enough/cpu-spike-before-instance-upgrade.png "
127+ alt ="AWS Lightsail CPU overview showing a spike before the instance upgrade ">
128+
129+ </ a >
130+
131+ </ div >
132+
133+ < div class ="field-note-content ">
91134
92- < p class ="field-note-meta ">
93- AWS • Capacity • Operations
94- </ p >
135+ < p class ="field-note-meta ">
136+ AWS • Capacity • Operations
137+ </ p >
95138
96- < p class ="field-note-date ">
97- Published 30 May 2026
98- </ p >
139+ < p class ="field-note-date ">
140+ Published 30 May 2026
141+ </ p >
99142
100- < h2 >
101- < a href ="/field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html ">
102- When a 1GB Instance Wasn't Enough
103- </ a >
104- </ h2 >
143+ < h2 >
144+ < a href ="/field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html ">
145+ When a 1GB Instance Wasn't Enough
146+ </ a >
147+ </ h2 >
105148
106- < p class ="field-note-summary ">
107- A production outage revealed how little headroom remained on a 1 GB Lightsail instance, leading to a deeper look at capacity planning, memory pressure and the decision to upgrade.
108- </ p >
149+ < p class ="field-note-summary ">
150+ A production outage revealed how little headroom remained on a 1 GB Lightsail instance, leading to a
151+ deeper look at capacity planning, memory pressure and the decision to upgrade.
152+ </ p >
109153
110- < a href ="/field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html " class ="field-note-link ">
111- Read note →
112- </ a >
154+ < a href ="/field-notes/when-a-1gb-lightsail-instance-wasnt-enough.html " class ="field-note-link ">
155+ Read note →
156+ </ a >
113157
114- </ div >
158+ </ div >
115159
116- </ article >
160+ </ article >
117161
118162 < article class ="field-note-card ">
119163
0 commit comments