<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justin Gardner on Medium]]></title>
        <description><![CDATA[Stories by Justin Gardner on Medium]]></description>
        <link>https://medium.com/@justin.gardner?source=rss-98496d08c5e7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I68dbi6u4K76Bf2L8pAPww.jpeg</url>
            <title>Stories by Justin Gardner on Medium</title>
            <link>https://medium.com/@justin.gardner?source=rss-98496d08c5e7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:00:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justin.gardner/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[User and Access Management on Linux (Digital Transformation Part 4: Linux on AWS EC2 continued)]]></title>
            <link>https://medium.com/@justin.gardner/user-and-access-management-on-linux-digital-transformation-part-4-linux-on-aws-ec2-continued-1634486b8e70?source=rss-98496d08c5e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1634486b8e70</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[linux-security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Justin Gardner]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 14:19:57 GMT</pubDate>
            <atom:updated>2026-02-09T14:19:57.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*s5gMXNiLbNgzLU0OZLHXgw.png" /></figure><p>Level Up Bank, our fictitious FinTech company, has doubled down on their use of Linux running on Amazon Web Services (AWS) Elastic Cloud Computer (EC2). After successfully migrating their corporate website to Apache running on AWS Linux 2023, they continue to explore all of use cases for transforming their IT and business operations by following a “cloud first” strategy. Next on their list of task list: facilitating seamless data accessibility while maintaining high standards of privacy and security.</p><p>Level Up Bank (LUB) will be hosting both departmental and user files on their Linux systems running on EC2. Their key business requirements are:</p><ul><li>Data segregation must map to separation of duties between department s (i.e. members of each team and department must only have access to data for their respective departments)</li><li>User generated data, hosted in individual’s Home directories, should only be accessible by the owners of those directories/files</li><li>Access permissions designed to reduce the risk of unauthorized data exposure</li></ul><p>To that end, this task will require us to configure their Linux environment so that:</p><ul><li>Configure departmental directories for Development, Operations, and Analytics</li><li>Create user groups that represent the departments and teams in scope for this part of the project: Developers, Operations, Data Analysts</li><li>Directory access permissions that map departments/groups to departmental shared directories</li><li>Creates user accounts for team members (with automated creation of Home Folders) and add them to appropriate groups for accessing shared folders</li></ul><h3>Configuring the Linux environment</h3><p>We will use the existing AWS Linux EC2 instance that we deployed during the earlier phases of the project.</p><p>We connected to the server via SSH using Terminal on MacOS (could also use PowerShell or Putty on Windows).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*HHscMiPlIVluCcIN-Nxt8A.png" /></figure><p>Next step, we created the Departmental Directories in the /srv folder.</p><pre>cd /srv<br>sudo mkdir Operations Development Analytics</pre><p>Next, we created the groups for each of the Departments</p><pre>sudo groupadd Developers<br>sudo groupadd Operations<br>sudo groupadd Data_Analysts</pre><p>We then changed the ownership of the Department directories/folders to the respective group:</p><pre>sudo chown :Developers Development/<br>sudo chown :Operations Operations/<br>sudo chown :Data_Analysts Analytics/</pre><p>Next, we changed permissions on Directories (and subsequent files) to ensure that file owners and members of each department could access (i.e. read, write, and execute permissions) each of the respective folders. We utilized the chmod command as well as numeric notation for permissions (see graphic below) across file owners, groups, “other” non-root users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*IEAsgC7C4W-ApLJaFZwLbQ.png" /></figure><pre>sudo chmod 770 Development/<br>sudo chmod 770 Operations/<br>sudo chmod 770 Analytics/</pre><p>Next, an important step: we executed the commands to created the user accounts, with email addresses and group memberships</p><pre>sudo useradd -m -c &quot;jwaller@levelupbank.com&quot; -g Developers jwaller<br>sudo useradd -m -c &quot;bdorsey@levelupbank.com&quot; -g Operations bdorsey<br>sudo useradd -m -c &quot;jewart@levelupbank.com&quot; -g Data_Analysts jewart</pre><p>Finally, we created some test files in each of the directories to test permissions and ensure proper access rights using the touch command:</p><pre>sudo touch Operations/opsfile1.txt Operations/opsfile2.txt Operations/opsfile3.txt<br>sudo touch Development/devfile1.txt Development/devfile2.txt Development/devfile3.txt<br>sudo touch Analytics/analytics1.txt Analytics/analytics2.txt Analytics/analytics3.txt</pre><p>After creating all directories, groups, users, and test content and then changing the necessary permissions, we ran a number of tests to validate that users could only access the relevant Department folders and their own home folders. We used the su (switch user) command to login as each users (after creating a default password for them using:</p><pre>passwd &lt;username&gt;</pre><p>See screenshots below for results.</p><p><strong>User</strong>: jewart <strong>Group</strong>: Analytics</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*cpiHSzp8D8aoKR2TrY3uVQ.png" /></figure><p><strong>User</strong>: bdorsey <strong>Group</strong>: Operations</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*ILLT0wHkI3cr2AJG1HvI0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*iXWEEFzpVPQJjlIwIUNlZQ.png" /></figure><p><strong>User</strong>: jwaller <strong>Group</strong>:Developers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*XhzemcOx7DRhdEhJFqVuPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*DkH_lPmfOAFyOUGeOvCeDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*XhzemcOx7DRhdEhJFqVuPQ.png" /></figure><h3><strong>Summary</strong>:</h3><p>In this phase of Level Up Bank’s digital transformation, we successfully established a secure, multi-user environment on AWS Linux 2023. By implementing strict user and group-level permissions, we ensured critical data segregation across the Development, Operations, and Analytics teams, aligning our cloud infrastructure with our internal separation of duties policies.</p><p><strong>Future Optimizations</strong></p><p>As we scale, we plan to enhance this security posture by implementing the <strong>Sticky Bit</strong> on shared directories. This permission setting restricts file deletion to the file owner only, preventing accidental data loss by other group members. Furthermore, to eliminate manual overhead and potential human error, we will move toward <strong>Infrastructure as Code (IaC)</strong> by automating user provisioning and directory management using <strong>Bash scripting</strong>. This will allow us to onboard new departments and users instantly while maintaining rigid security standards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1634486b8e70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation Continued: Installing Apache on Linux on AWS EC2]]></title>
            <link>https://medium.com/@justin.gardner/digital-transformation-continued-installing-apache-on-linux-on-aws-ec2-5a766b093afd?source=rss-98496d08c5e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a766b093afd</guid>
            <dc:creator><![CDATA[Justin Gardner]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 19:06:25 GMT</pubDate>
            <atom:updated>2026-01-31T19:06:25.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CRposoe9XpKa5tTM1c8NNw.png" /></figure><p>Level Up Bank, our fictitious fintech startup, is continuing their journey into Digital Transformation. They continue to evolve their cloud environment and expand their use of AWS. In this installment of their journey, they have decided to migrate their static website, currently hosted in an S3 bucket, to Apache running on an EC2 instance.</p><p>As their service portfolio grows, they want the flexibility to build more dynamic web sites and applications. Apache, one of the world’s most widely used web server software, is known for its flexibility and modularity. It gives Level Up the choice of programming language, database backend and wide range of security features, such as support for SSL/TLS and digital certificates.</p><p>Some of the key benefits of deploying Apache on Linux of which Level Up will be able to take advantage include:</p><p><strong>Stability and reliability:</strong> Apache web server is known for its stability and reliability, making it a popular choice for critical applications, such as those used by banks.</p><p><strong>Performance: </strong>Apache web server is highly scalable and can handle large amounts of traffic, making it an ideal choice for banks that need to support a high volume of online transactions.</p><p><strong>Security:</strong> Apache web server is considered very secure, with a strong focus on security features and a large community of users who work to identify and address security vulnerabilities.</p><p><strong>Flexibility:</strong> Apache web server is highly customizable, with a wide range of plug-ins and modules available that can be used to add functionality and tailor the server to meet the bank’s specific needs.</p><p><strong>Cost: </strong>Apache web server is open-source software, meaning it is free and can be used without licensing fees.</p><h3>Deploying Apache on a Linux EC2 Instance in AWS</h3><p>We will use an existing EC2 instance running Amazon Linux 2023 to use for our Apache webserver.</p><p>From Linux/Mac terminal, I connected to the chosen EC2 instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*3FB8J-g_HT4DPgmA8UrP7A.png" /></figure><p>I ran the following commands to install httpd (Apache web service):</p><p>sudo yum update -y ( to update package manager database to the latest software packages)</p><p>To install apache, I ran</p><pre>sudo yum install httpd -y</pre><p>To start the service</p><pre>sudo systemctl start httpd</pre><p>Then to enable the service to start whenever the instance boots</p><pre>sudo systemctl enable httpd</pre><h3>Editing Security Groups in AWS Console to Allow HTTP traffic to Apache webserver</h3><p>Back in the AWS Console, I edited the Security Groups on the instance to allow inbound HTTP and HTTPS traffic</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*aSC9wtL2pdjtsf6_BP94EQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*pVKwRMTaaRUZ7uU9Zunr2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tOIT_CnWJSYOc3PGFHU2PQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/173/1*mgSypvIMJhmpPEX8F2G0gQ.png" /></figure><p>After a few moments, I browsed to the public IP address of the EC2 instance and success!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*vhqAgTvCF6kAFRc2hhCouw.png" /></figure><h3>Uploading the Corporate Website</h3><p>I opened the file index.html that was originally used for the static site that was deployed to S3 (see <a href="https://medium.com/@justin.gardner/digital-transformation-step-1-hosting-a-static-website-on-amazon-s3-b891536948b4">https://medium.com/@justin.gardner/digital-transformation-step-1-hosting-a-static-website-on-amazon-s3-b891536948b4</a>) and opened it in Visual Studio Code, copying its contents to clipboard</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*RkDvOkpxnfF41llWPfxX_Q.png" /></figure><p>Back in my terminal connection to the EC2 Linux instance, browsed to /var/www/html directory</p><p>cd /var/www/html</p><p>Created and opened an index.html file using nano text editor in terminal</p><pre>sudo nano index.html</pre><p>Copy the contents of clipboard to file and exited</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70Ea17CfXaNb-1Vn6Hmm0w.png" /></figure><p>Control + o → enter (to save file)</p><p>Control + X to exit nano</p><p>After refreshing the page, I am able to see the LUB website</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fyZieDlArYEcuC6xtkKO4Q.png" /></figure><p>I wanted to generate some traffic for the site so that I can view connections in the Access logs. I connected to the site from two different computers as well as from an iPhone on WIFI and then cellular connections. I used the &lt;tail&gt; command to view the last 15 lines of the file and copied those lines to a text file</p><p>Command to view log files:</p><pre>sudo tail -n 15 /var/log/httpd/access_log &gt; access_log_012026.txt</pre><p>Used cat command to view the file:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-XshXgaQtvtB487U5fByQ.png" /></figure><p>I did the same for the error log:</p><pre>sudo tail -n 15 /var/log/httpd/error_log &gt; error_log_012026.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DP17ctK_B96XBclBdksD9g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a766b093afd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation Part 2: Secure Remote Access for Administration and Troubleshooting of EC2…]]></title>
            <link>https://medium.com/@justin.gardner/digital-transformation-part-2-secure-remote-access-for-administration-and-troubleshooting-of-ec2-bf0135468044?source=rss-98496d08c5e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf0135468044</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[itops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Justin Gardner]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 17:24:59 GMT</pubDate>
            <atom:updated>2026-01-25T17:24:59.909Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Digital Transformation Part 2: Secure Remote Access for Administration and Troubleshooting of EC2 Instances</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OlFK4284f2MCOA6jvsHWYg.png" /></figure><p><strong>Executive Summary</strong><br> Level Up Corporation, a (fictitious) mid-sized tech company, leverages AWS Elastic Compute (EC2) to host a growing fleet of Linux and Windows applications. As a truly remote company, their IT team is globally dispersed. As such, they need a set of tools to allow remote administration of these instances. This guide helps walk through how they have enabled SSH and RDP for quick/secure access to their Linux and Windows instances, respectively, as well as configuring Security Groups as additional layer of security. We will also how they can provided a more centralized experience using AWS Systems Manager (SSM) and Session Manager to manage their EC2 estate.</p><p><strong>SSH and RDP:</strong></p><p>SSH (Secure Shell) is natively available for Linux OS’ and provide an encrypted channel to directly connect to and managed Linux instances remotely. Similarly, RDP (Remote Desktop Protocol) allows for remote administration of Windows instances by providing access directly to the Windows desktop.</p><p><em>Benefits of using SSH and RDP:</em></p><p>Quick access and remote management for instances</p><ul><li>Level Up’s IT team can access their instances from wherever they have an internet connection</li><li>IT administrators can quickly identity and repair issues on those instance to ensure application availability</li></ul><p>Built-in Security</p><ul><li>Both SSH and RDP provide secure, encrypted communication channels than can be enhanced by Keys and certificates</li><li>Security can be enhanced using Security Groups, which are virtual firewalls that control inbound and outbound traffic to the EC2 instances. This could allow connections to be restricted to specific IP addresses or address ranges</li></ul><p><strong>AWS Systems Manager/Session Manager</strong></p><p>AWS System Manager (SSM) helps organizations centrally view, managed and operate nodes at scale in AWS (as well as on-prem and multi-cloud environments). It provides a centralized, consolidated view of resources like EC2 instances that will allow Level Up’s administrators to perform common tasks as their AWS estate grows across and regions. Session Manager is a capability of SSM that allows from a one-click, browser based shell access to the EC2 instances.</p><p>Benefits of using SSM and Session Manager:</p><ul><li>Enhanced visibility across entire Aws infrastructure, especially EC2</li><li>Administrators can quickly gather information about instances like OS details, instance name, etc.</li></ul><p>Node management at Scale</p><ul><li>As level up’s EC2 and AWS infrastructure continues to expand, SSM provides ability to fix issues and run automations across nodes, including if they ever expand in to other cloud providers or even on-prem/hybrid</li><li>Common task can be automated minimizing the need to log directly into every node</li></ul><p>Enhanced Security</p><ul><li>SSM can be integrated with IAM roles to help Level Up restrict who can access instances based on identity</li><li>Can provide just-in time access to nodes</li></ul><p><strong>SSH Access:</strong></p><p><strong><em>Adding SSH access to an existing EC Instance running Linux</em></strong></p><p>Adding SSH to an instance that has already been deployed in AWS account involve creating or editing the Security Group to allow access to SSH (TCP Port 22).</p><p>Log into the AWS console and navigate to the EC2 service using the Search bar or “Recently Visited” section in upper left of console</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*sjarTFHvWrMRfLGKO960wQ.png" /></figure><p>In left hand pane, click on Instances.</p><p>Find a running Linux instance and click on the Instance ID link</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*ZqBvSh7PN2AwZ8lNw7fm8A.png" /></figure><p>Navigate to the Security tab (scroll to middle of screen/panel) on the Instance Details pane</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*K7ZubNXg68pl_Bh_eUoRXA.png" /></figure><p>Find the Security Groups section and click on the link beginning with “sg-”</p><p>Under the Inbound Rules Tab, select Edit Inbound rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*Jm-gHc9BdFlM40WZwyFJog.png" /></figure><p>On the Inbound Rules screen, click Add Rule</p><p>Under Type, select SSH on the drop down</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*YLDKVsNuMbs69sRB2jZs3w.png" /></figure><p>Under Source, select Anywhere (less secure) or, for more security, select either Custom or My IP</p><p>We will select “My IP” for in this instance. With Custom, you can define a customer source IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*XqFd4qUTZmU2q_vHNZ-Yrg.png" /></figure><p>Add a description (optional)</p><p>Click Save rules</p><p>Go back to the EC2 Instance details and copy the Public IPv4 address</p><p>On local machine, open Terminal (MacOs) or PowerShell (Windows)</p><p>Ensure you have downloaded the keypair that was created/associated when machine was originally created</p><p>Enter the command:</p><pre>ssh -I &lt;path to keypair file&gt; ec2-user@public-Ipaddress-copied-from-above</pre><p>Enter “yes” when asked “are you sure you want to continue”</p><p>You should be presented with Linux shell of the EC2 instance (Amazon Linux in this example)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*PouwCIgE9jbJmLWSqfn9jw.png" /></figure><p><strong><em>Inbound Security Group rules can also be added during initial creation:</em></strong></p><p>On the “Launch an Instance” page, under Network Settings Section</p><p>Under Firewall (security groups)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*_xssHJTmiC4-MQasu2I2Yw.png" /></figure><p>Click button to “Create Security Group” and choose “Allow SSH traffic from” box and, in the dropdown, configure source Address (Anywhere, Custom or My IP)</p><p><strong>RDP Access :</strong></p><p>We will launch a new Windows instance for this use case</p><p>Launch a new EC2 instance</p><p>Give it a name (in our case “luc-winserv”)</p><p>Under Application and OS Images choose “Windows 2025 Base”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ot8cwU222WFkfHg4YY6WEA.png" /></figure><p>Choose an instance type (for this example, we will use “c7i-flex.large”)</p><p>Create a new keypair or use an existing keypair (for login): we will use an existing keypair in this instance (“ec2ccp_kp”)</p><p>Under Network Settings, select Create Security Group</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*1IGcuAMg3u1KpZPi9p-77g.png" /></figure><p>Select “Allow RDP traffic from” and define a source in the drop down (Anywhere, Custom, MyIP). We will choose My IP in this case.</p><p>Will not configure any Advance details for this instance</p><p>Select <strong>Launch Instance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*u0OfVZ2IQweF1WfI7GIA-g.png" /></figure><p>Once instance is in “Running” state, select it and hit the “Connect” button above it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SdvP7QyIAmo8VBKcHWmWA.png" /></figure><p>Select “RDP Client” and ensure “Connect Using RDP client” is selected</p><p>Click to “Download remote desktop file” and save to your local machine</p><p>Note the username “Administrator”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdIlSIZ_8KQxxugnFt2oiA.png" /></figure><p>Click “Get Password”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*OW5_JVX9idmqzKAeNOeQhA.png" /></figure><p>On the Get Windows Password screen upload the private key that was associated with the instance when it was created.</p><p>This will the .PEM file that you was downloaded/saved from previous instance deployments.</p><p>Once uploaded select, Decrypt Password:</p><p>Password will be now be visible on “Connect” screen. Copy it and save it to a secure place: Click Cancel on the screen.</p><p>Navigate to where you saved the .rdp file that was downloaded in the last step. Right click the file and select Open With</p><p>On Windows, select Remote Desktop Connection</p><p>On MacOS, select Windows App (if not installed, can be installed from the Apple Store)</p><p>On Linux, install RDP client like Remmina (<a href="https://remmina.org/">https://remmina.org/</a>) or Thincast (<a href="https://thincast.com/en/products/client">https://thincast.com/en/products/client</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*aCNYmBdrycozBr7oOEZ6ow.png" /></figure><p>Adding RDP Access to an existing Windows EC2 instance:</p><p>Adding RDP access to an existing instance involves editing the Security Group’s Inbound Rules (for the Windows EC2 instance) similar to adding SSH to a Linux EC2 instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wbzYVvuDt7Ye46fX8ChN8g.png" /></figure><p><strong>Configuring Session Manager for Accessing EC2 Instance Shells:</strong></p><p><em>Ensure the SSM agent is installed on each of the EC2 instances</em></p><p>For Amazon Linux 2 and Linux 2023 (which is running in our instances), SSM agent is installed by default</p><p>Type the following command to ensure it is running:</p><pre>sudo systemctl status amazon-ssm-agent</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*RBITTYqjmceFr0SoAF1A-w.png" /></figure><p>For Windows, connect to your Windows EC2 instance via RDP</p><p>Via the Web browser, install the SSM Agent using the following link</p><p><a href="https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/windows_amd64/AmazonSSMAgentSetup.exe">https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/windows_amd64/AmazonSSMAgentSetup.exe</a></p><p><em>Create a Custom IAM role with Session Manager permissions</em></p><p>Navigate to IAM console (using Search in upper left hand portion of AWS)</p><p>Select Policies on the left hand pane</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*jEaTAEwD3mpa__YF_jhe9Q.png" /></figure><p>Select Create Policy and on the next screen, select JSON button</p><p>Under Policy Editor, replace the default content with the following JSON</p><pre>{<br>&quot;Version&quot;: &quot;2012–10–17&quot;,<br>&quot;Statement&quot;: [<br>{<br>&quot;Effect&quot;: &quot;Allow&quot;,<br>&quot;Action&quot;: [<br>&quot;ssm:UpdateInstanceInformation&quot;,<br>&quot;ssmmessages:CreateControlChannel&quot;,<br>&quot;ssmmessages:CreateDataChannel&quot;,<br>&quot;ssmmessages:OpenControlChannel&quot;,<br>&quot;ssmmessages:OpenDataChannel&quot;<br>],<br>&quot;Resource&quot;: &quot;*&quot;<br>}<br>]<br>}</pre><p>Name the new policy (in this case “SessionManagerPermissions”)</p><p>Choose Create Policy</p><p>In the IAM console, go to Roles and Create Role</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*eehVl02bRE8v2uiq-nN_9g.png" /></figure><p>On the create role page, choose AWS Service and for Use Case, find/choose EC2 and hit next</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqKAUT7Znc-8aO04yDoqdw.png" /></figure><p>On add Permissions page, find the Policy created in the previous step (SessionManagerPermissions)</p><p>On Name, review, create page, give the new role a name (e.g. LUCSessionManagerRole)</p><p>(Please note, additional permissions can be added for accession session logs stored in S3 and Cloudwatch logs)</p><p><em>Add the IAM role to each of the EC2 Instances to which you want to connect/manage via Session Manager</em></p><p>On ec2 Console, choose instance (checking box next to it) and Select Actions →Security →Modify IAM Role</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*ruOTV9X6dguLtjmyP8o1SQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KuUhavT5D2dr8IRayJL5g.png" /></figure><p>In the drop down, select the IAM role created in the previous steps and select Update IAM Role</p><p>Now, from each instance, Session Manager should be an option by which you can connect to a Shell (Linux) or PoweShell (Windows) for centralized managed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HkLhAw1NaXAcZhfcfJYoMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*w3L41V3hBtia1cnXCrN8sg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2YXb2UyfFTLN7ejG-Pk5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*9vHb6-j3Jja_j8wZ6Y-qZQ.png" /></figure><p>This only scratches the surface of what SSM/Systems Manager can do for managing instances (Session manager is just one capability).</p><p><strong>Summary:</strong></p><p>By using the native remote access tolls available from AWS, Level Up’s IT team can quickly ensure that their EC2 instances running efficiently and the hosted applications are available to users and customers. SSH and RDP access, as well as the Session Manager module of AWS Systems Manager, make this possible.</p><p>As they continue to expand their use of AWS, they can add additional layers of security by way of services like IAM Identity Center and Virtual Private Cloud Connectivity Options like Client VPN or Software Client VPN (3rd party).</p><p>This guide only scratched the surface of what is possible for Level Up as they continue to expand their use the cloud and AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*L15_nK0QDcV2tpSMvn6HTA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf0135468044" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation Step 1: Hosting a Static Website on Amazon S3]]></title>
            <link>https://medium.com/@justin.gardner/digital-transformation-step-1-hosting-a-static-website-on-amazon-s3-b891536948b4?source=rss-98496d08c5e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b891536948b4</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Justin Gardner]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 18:03:59 GMT</pubDate>
            <atom:updated>2026-01-17T18:20:12.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*ZVuDlLh8VkEpngYZ8Ilpxw.png" /></figure><h3>Level Up Bank: Digital Transformation &amp; S3 Migration</h3><p>Level Up Bank is a fictional fintech startup offering digital banking services to customers. Ironically, they are currently hosting their company website, their primary means for acquiring new customers, on an on-premises virtual machine maintained by their internal IT team. As a “digital first” financial company, they are looking to migrate all of their operational IT to the cloud, specifically AWS.</p><p>As a first step, they will migrate their static website to AWS S3. What follows is a step-by-step outline of this first project as well as an overview of Level Up Bank’s goals as they embark on their digital transformation.</p><h3>Level Up’s Business Goals for Migrating to the Cloud</h3><ul><li><strong>Improved Business Agility:</strong> Level Up Bank continually offers new services to its customers. The cloud allows them to spin up services quickly without the wait and expense of procuring, installing, and managing servers or storage.</li><li><strong>Improved Scalability:</strong> As their business grows, the cloud allows them to scale up capacity quickly as demand for their services increases, as well as the ability to deal with fluctuations in demand.</li><li><strong>Reduced Management Overhead:</strong> Related to the previous outcomes, a cloud transformation will allow Level Up’s IT teams to focus on the digital work (i.e., service delivery, new initiatives, etc.) that is most impactful to the business (and revenue) and minimize the time they need to manage internal IT infrastructure.</li><li><strong>Cost Savings/Optimization:</strong> Cloud services, including AWS, allow Level Up to pay for the cloud resources that they use (pay as you go/on demand) versus the need to purchase and, potentially, over-provision on-prem resources in an attempt to predict what demand for services will be.</li></ul><h3>Advantages of Using AWS S3 as a Hosting Solution</h3><ul><li><strong>Reduced Management Overhead:</strong> AWS S3 is a fully managed service, allowing Level Up’s IT team to focus on more critical and impactful tasks.</li><li><strong>Improved Scalability and High Availability:</strong> AWS S3 provides automatic scalability, handling increased website traffic without any downtime. S3 is also highly available (achieving 99.999999999% durability) using multiple availability zones and redundancy, making it virtually available at all times to users and customers.</li><li><strong>Cost Savings:</strong> Hosting static content (like a website) on S3 is more cost-effective since Level Up will only be charged for the storage that is used as well as charged minimally for data transfer. Running the same site/content on a virtual machine, including on EC2, requires additional expenses for compute power, storage, and data transfer (plus the sunk costs of IT management).</li></ul><h3>Deploying the Site to AWS S3</h3><p><strong>Create the Bucket:</strong> Navigate to the AWS Console, search for <strong>S3</strong>, and select <strong>Create Bucket</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2N66iQh56ZSU6s4U_edJ2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*PNr1aRyYhro_3x_dc28sQQ.png" /></figure><p><strong>Configure Basics:</strong> Ensure the Bucket Type is set to <strong>General Purpose</strong>. Enter a globally unique name that complies with S3 naming conventions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s8afLt4yD68o2k49FSKLTQ.png" /></figure><p><strong>Finalize Creation:</strong> Accept all other defaults and click <strong>Create Bucket</strong>. Once complete, click <strong>View Details</strong> on the success banner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*d1eadaXroWC9mdM96aADdg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tjw36Ti8qdvVDexZ3s2tvg.png" /></figure><p><strong>Upload Content:</strong> Select <strong>Upload</strong> &gt; <strong>Add Files</strong> and browse for your index.html file. Once uploaded, click <strong>Close</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQASuwX9wDuq0Ab5_M_uhA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*PDfp-d3aMnOBLTQzZ6L92Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vuGlm_swnDR8GImcHTi8tw.png" /></figure><p><strong>Enable Hosting:</strong></p><ul><li>Go to the <strong>Properties</strong> tab and scroll to the <strong>Static website hosting</strong> section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9EWQ_c8BLbOlcpAmJRqRbQ.png" /></figure><ul><li>Click <strong>Edit</strong>, select <strong>Enable</strong>, and choose <strong>Host a Static Website</strong>.</li><li>In the “Index document” field, enter <strong>index.html</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cKO9Ceaai8OLbYI7Udsp1A.png" /></figure><ul><li>Click <strong>Save Changes</strong>.</li><li><em>Note:</em> Copy the <strong>Bucket Website endpoint</strong> URL found in this section (scroll to the bottom of the screen); you will need this later</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*3sl0BapugSb-mASLvYOfqA.png" /></figure><p><strong>Adjust Permissions:</strong></p><ul><li>Go to the <strong>Permissions</strong> tab.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/929/1*ofkvGhZgh2otKhKY2yEhsQ.png" /></figure><ul><li>Under <strong>Block public access (bucket settings)</strong>, click <strong>Edit</strong>, uncheck <strong>Block all public access</strong>, and click <strong>Save Changes</strong>. Type “confirm” in the warning box to proceed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qU64c0VrXe4kMNLjnlFF0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ld90WW-Kx0njl4EkFvn-sw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*Cke-5sNb3lf8rRQ7GO3wtQ.png" /></figure><p><strong>Add Bucket Policy:</strong></p><ul><li>While still in the <strong>Permissions</strong> tab, scroll to the <strong>Bucket Policy</strong> section and click <strong>Edit</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDT1RmiHsFupUPz1V-q3lQ.png" /></figure><ul><li>Paste the JSON policy below, replacing “Bucket-Name” with your actual bucket name.</li></ul><pre> {<br>     &quot;Version&quot;: &quot;2012-10-17&quot;,       <br>     &quot;Statement&quot;: [<br>         {<br>             &quot;Sid&quot;: &quot;PublicReadGetObject&quot;,<br>             &quot;Effect&quot;: &quot;Allow&quot;,<br>             &quot;Principal&quot;: &quot;*&quot;,<br>             &quot;Action&quot;: [<br>                 &quot;s3:GetObject&quot;<br>             ],<br>             &quot;Resource&quot;: [<br>                 &quot;arn:aws:s3:::Bucket-Name/*&quot;<br>             ]<br>         }<br>     ]<br>}</pre><p>Click <strong>Save Changes</strong>.</p><p><strong>Verify:</strong></p><p>Open an Incognito/Private browser window and paste the <strong>Bucket Website Endpoint</strong> URL you copied earlier. (Note: You may receive a “Not Secure” warning regarding the SSL certificate; proceed strictly for testing purposes).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6Nxh0SbeTHZvcWqOO4-Aw.png" /></figure><h3>Future Upgrades and Conclusion</h3><p>This project can be further enhanced by using AWS products like CloudFront (CDN) to leverage web caching for better global performance and enhanced security.</p><p>As Level Up Bank continues on their digital transformation, they will continue to accelerate their journey to AWS. The website migration to S3 is only the first step in this process. Stay tuned as we continue to document their experiences, projects, and lessons learned in upcoming postings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b891536948b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>