Joe's Tech Blog

Just another Tech Blog

2026

AWS

How to Deploy OpenClaw on AWS Lightsail (Step-by-Step Guide)

Joseph Klimczak No Comments

Run your own autonomous AI assistant in the cloud in under 30 minutes.

Introduction

AI agents are rapidly evolving from simple chatbots into systems capable of performing real tasks such as managing workflows, executing commands, and integrating with external tools. One of the most exciting open-source projects in this space is OpenClaw, a self-hosted AI assistant designed to run automation workflows using large language models. 

Instead of running OpenClaw directly on your personal machine, many developers prefer deploying it on a cloud server. This approach provides better security, reliability, and uptime.

In this guide, we’ll walk through how to deploy OpenClaw using Amazon Lightsail, a simplified cloud platform from AWS that allows you to launch and manage virtual servers quickly. 

By the end of this tutorial you will have:

  • A running cloud server
  • OpenClaw installed and running
  • A web interface you can access from anywhere

What Is OpenClaw?

OpenClaw is an open-source AI assistant framework that connects to large language models and executes tasks on your behalf. It can integrate with messaging platforms, external APIs, and automation tools. 

Unlike traditional chatbots, OpenClaw is designed to act as a task-executing AI agent.

Key capabilities

  • Integrates with AI models such as OpenAI, Claude, or Gemini
  • Executes commands and automation workflows
  • Connects with services like Slack, Telegram, or Discord
  • Runs locally or in your own cloud infrastructure

Because the AI agent may execute commands or access external systems, running it in a dedicated cloud environment is often the safest option.

Why Use AWS Lightsail?

AWS Lightsail is a simplified cloud computing service that provides virtual servers, networking, storage, and monitoring in one interface. 

It’s designed to make cloud hosting much easier than traditional AWS services like EC2.

Benefits of Lightsail

  • Simple server deployment
  • Fixed monthly pricing
  • Built-in browser SSH access
  • Easy scaling and snapshots
  • Ideal for small apps and AI tools

Lightsail can launch a server in minutes and is perfect for hosting self-hosted tools like OpenClaw.

Prerequisites

Before starting this tutorial, make sure you have:

  • An AWS account
  • Access to the AWS Management Console
  • Basic knowledge of Linux commands

AWS recommends creating an administrative user and enabling multi-factor authentication rather than using the root account for daily operations. 

Step 1 — Create an AWS Lightsail Instance

  1. Log in to the AWS Console
  2. Search for Lightsail
  3. Click Create Instance

Recommended settings

Platform: Linux / Unix

Blueprint: Ubuntu 22.04

Instance plan:

PlanCPURAMRecommended
$51 vCPU512MBTesting
$101 vCPU1GBBetter
$202 vCPU2GBProduction

Choose a region close to you to minimize latency.

Then click Create Instance.

Screenshot – Create Lightsail Instance

Within a few minutes your server will be available.

Step 2 — Connect to Your Server

Lightsail provides a built-in browser terminal, meaning you don’t need to install an SSH client.

To connect:

  1. Open your instance in Lightsail
  2. Click Connect
  3. Launch the Browser-based SSH terminal

Screenshot – Lightsail SSH Terminal

You can now run Linux commands directly from your browser.

Step 3 — Update the Server

Run the following commands to update your system.

sudo apt update && sudo apt upgrade -y

Next install required dependencies.

sudo apt install git docker.io docker-compose -y

Enable Docker:

sudo systemctl enable docker
sudo systemctl start docker

Docker allows OpenClaw to run in containers, making installation easier and safer.

Step 4 — Install OpenClaw

Clone the OpenClaw repository:

git clone https://github.com/openclaw-ai/openclaw.git
cd openclaw

Start the OpenClaw services:

docker compose up -d

Docker will automatically download and configure the necessary containers.

Step 5 — Access the OpenClaw Dashboard

Once running, OpenClaw provides a web interface.

Open a browser and go to:

http://YOUR_SERVER_IP:18789

Replace YOUR_SERVER_IP with your Lightsail public IP.

From this interface you can:

  • Configure AI models
  • Install automation skills
  • Connect messaging platforms
  • Run workflows and commands

Screenshot – OpenClaw Dashboard

Security Best Practices

Because OpenClaw can run commands and access external systems, security is critical.

Recommended protections:

  • Enable HTTPS with a reverse proxy
  • Restrict open ports in Lightsail firewall
  • Store API keys in environment variables
  • Keep containers updated

Treat the OpenClaw server like any production workload.

Monitoring and Backups

AWS Lightsail includes tools to monitor and protect your server.

Built-in features

  • CPU and network monitoring
  • Snapshots for backups
  • Additional storage disks
  • Instance resizing

Snapshots allow you to restore your entire environment if something goes wrong.

Final Thoughts

Deploying OpenClaw on AWS Lightsail provides a powerful yet simple way to run AI agents in the cloud.

In just a few steps you can:

  • Launch a cloud server
  • Install OpenClaw
  • Connect AI models and services
  • Run autonomous workflows 24/7

As AI agents become more capable, self-hosted platforms like OpenClaw offer developers full control over automation and data while leveraging the scalability of the cloud.

AWS Blog

AWS Certificate Manager Shortens Certificate Lifetimes: What It Means for Your Cloud Security Strategy

Joseph Klimczak No Comments

On February 18, 2026, AWS announced an important update to AWS Certificate Manager (ACM) that aligns public TLS certificate lifetimes with new industry-wide security standards.

Read the official announcement

This change reflects a broader shift across the web toward shorter-lived certificates, stronger automation, and reduced exposure to key compromise.

🔐 What Changed?

AWS Certificate Manager now issues public certificates with a maximum validity of 198 days, replacing the previous 395-day validity period. 

This update ensures compliance with the CA/Browser Forum mandate requiring certificate lifetimes to be no longer than 200 days starting March 15, 2026. 

Key Highlights

  • New certificates: Automatically issued with a 198-day validity by default. 
  • Existing certificates: Continue to work until they expire or renew—no manual changes required. 
  • Renewals: ACM automatically renews certificates 45 days before expiration under the new model. 
  • Legacy 395/398-day certs: Renew normally, then switch to the 198-day lifecycle. 

➡️ In short: No action is required from customers—ACM handles the transition seamlessly. 

📉 Pricing Adjusted to Match Shorter Lifetimes

Because certificates now live for roughly half as long, AWS reduced pricing for exportable public certificates:

Certificate TypeOld PriceNew Price
FQDN Certificate$15$7
Wildcard Certificate$149$79

These lower prices reflect the reduced validity window while keeping automated lifecycle management intact. 

🛡️ Why the Industry Is Moving to Shorter Certificate Lifetimes

Although this update is operationally small, it represents a significant evolution in TLS security philosophy.

1. Reduced Risk Window

If a private key is compromised, a shorter certificate lifetime limits how long attackers can exploit it.

2. Encouragement of Automation

Modern PKI assumes automated issuance and rotation rather than manual certificate management—something ACM already abstracts away.

3. Alignment With Zero-Trust Principles

Frequent credential rotation is a core tenet of Zero Trust architectures, making short-lived certificates a natural fit.

4. Standardization Across Browsers and CAs

The CA/Browser Forum mandate is an ecosystem-wide move—not AWS-specific—ensuring consistent security baselines across providers. 

⚙️ What This Means for AWS Customers

If You Already Use ACM (Most Users)

You’ll likely notice no operational difference:

  • Certificates still auto-renew.
  • Integrations with services like ALB, CloudFront, and API Gateway remain unchanged.
  • Deployment workflows do not need modification.

If You Export Certificates

Plan for:

  • More frequent renewal cycles.
  • Updated cost modeling (now cheaper per certificate).
  • Ensuring downstream systems expect shorter validity periods.

If You Manage Certificates Manually Elsewhere

This announcement is a signal to accelerate automation—manual rotation every ~6 months is not sustainable.

📊 Operational Impact Snapshot

AreaBeforeAfter
Default Validity395 days198 days
Renewal Timing~60 days prior (legacy)45 days prior
CompliancePre-mandateCA/B Forum aligned
Customer Action NeededSometimesNone
Exportable Cert CostHigherReduced

🚀 Strategic Takeaway

This change isn’t just a technical adjustment—it’s part of a broader movement toward ephemeral trust models in cloud security.

Organizations that:

  • Automate certificate lifecycle management
  • Treat credentials as short-lived assets
  • Integrate renewal into CI/CD and infrastructure pipelines

…will be best positioned for the next wave of PKI modernization.

✍️ Final Thoughts

AWS Certificate Manager’s shift to 198-day certificates demonstrates how cloud platforms are quietly enforcing stronger security hygiene across the internet. With automation handling the heavy lifting, customers gain improved security posture without additional operational burden.

Blog

Honored to Be a 2026 Omnissa Tech Insider (Year Two!)

Joseph Klimczak No Comments

I’m incredibly grateful to share that I’ve been selected once again as part of the 2026 Omnissa Tech Insiders —my second year in this inspiring community.

This year’s cohort brings together an exceptional group of professionals with deep experience across AI, cloud, security, developer tools, and beyond. The diversity of perspectives, real-world impact, and accomplishments across the group truly impressed me.

Being part of this community has been both energizing and humbling—learning from peers, exchanging ideas, and contributing to conversations that are shaping the future of technology. I’m proud to stand alongside such talented individuals and excited about what lies ahead.

A huge thank you to the Omnissa team and to everyone in this cohort. Congratulations to all the 2026 Tech Insiders—I’m looking forward to another great year of collaboration and growth.

👏

👉 View the full announcement here: https://lnkd.in/etxzrcVS

AWS

Creating an AWS Linux System and Using Amazon Polly (CLI, Python, and GUI)

Joseph Klimczak No Comments

Amazon Polly makes it easy to convert text into natural-sounding speech using AI-powered voices. Whether you prefer clicking through a web interface or automating everything on a Linux server, Polly has you covered.

In this guide, we’ll:

  • Launch an Amazon Linux EC2 instance
  • Use Amazon Polly from the AWS Console (GUI)
  • Generate speech using the AWS CLI
  • Create audio files programmatically with Python

What Is Amazon Polly?

Amazon Polly is a managed text-to-speech service that:

  • Converts text into lifelike speech
  • Supports multiple languages and neural voices
  • Outputs MP3, OGG, and PCM audio formats
  • Requires no infrastructure management

Prerequisites

You’ll need:

  • An AWS account
  • An EC2 key pair
  • Basic Linux knowledge
  • An IAM user or role with Polly permissions

Step 1: Launch an Amazon Linux EC2 Instance

  1. Go to AWS EC2 Console
  2. Click Launch Instance
  3. Choose Amazon Linux 2
  4. Select t2.micro or t3.micro
  5. Allow SSH (port 22) in the security group
  6. Launch the instance

Copy the public IP address once the instance is running.

Step 2: Connect to the EC2 Instance

ssh -i your-key.pem ec2-user@<EC2_PUBLIC_IP>

You are now logged into your Amazon Linux server.

Step 3: Using Amazon Polly via the AWS Console (GUI)

Before touching the command line, let’s explore Polly using the AWS Management Console — this is the fastest way to experiment.

Accessing the Polly Console

  1. Log in to the AWS Management Console
  2. Search for Polly
  3. Click Amazon Polly
  4. Open the Text-to-Speech page

No EC2 instance is required for this step.

Generating Speech in the GUI

  1. In the Text-to-Speech editor:
    • Enter your text:
Welcome to Amazon Polly. This audio was created using the AWS Console.

  2. Choose a voice (e.g., Joanna, Matthew)
  3. Select Engine:
    • Standard
    • Neural (more natural, recommended)
  4. Choose Language
  5. Click Listen ▶️

You’ll hear the generated speech instantly.

Downloading the Audio File

  1. Select Output format (MP3 or OGG)
  2. Click Download
  3. Save the file locally

This is perfect for:

  • Testing voices
  • Demos and presentations
  • Content creation workflows

Using SSML in the GUI (Optional)

Enable SSML to control speech:

<speak>
  Welcome to <emphasis level="strong">Amazon Polly</emphasis>.
  <break time="1s"/>
  This is an example using SSML.
</speak>

SSML allows:

  • Pauses
  • Emphasis
  • Speaking rate control
  • Pronunciation tuning

Step 4: Configure AWS Credentials on Linux

Recommended: IAM Role

Attach an IAM role to the EC2 instance with:

  • AmazonPollyFullAccess

No credentials required on the server.

Alternative: AWS CLI Credentials

aws configure

Enter:

  • Access key
  • Secret key
  • Region (e.g., us-east-1)

Step 5: Using Amazon Polly from the AWS CLI

Generate speech directly from Linux:

aws polly synthesize-speech \
  --voice-id Joanna \
  --output-format mp3 \
  --text "This audio was generated from the AWS CLI" \
  cli-output.mp3

Install an audio player:

sudo yum install -y mpg123

Play the file:

mpg123 cli-output.mp3

Step 6: Using Amazon Polly with Python

Install Dependencies

sudo yum install -y python3 pip
pip3 install boto3

Python Script Example

Create the script:

nano polly_tts.py

Add:

import boto3

polly = boto3.client("polly")

response = polly.synthesize_speech(
    Text="Hello from Amazon Polly using Python on Amazon Linux",
    OutputFormat="mp3",
    VoiceId="Matthew"
)

with open("python-output.mp3", "wb") as file:
    file.write(response["AudioStream"].read())

print("Audio file created: python-output.mp3")

Run it:

python3 polly_tts.py
mpg123 python-output.mp3

Comparing GUI vs CLI vs Code

MethodBest For
AWS Console (GUI)Voice testing, demos, learning
AWS CLIAutomation, scripting
Python / SDKApplication integration

Security Best Practices

  • Prefer IAM roles over access keys
  • Use least-privilege IAM policies
  • Monitor usage with CloudWatch
  • Avoid committing credentials to Git

Conclusion

Amazon Polly is flexible enough for beginners and powerful enough for production systems. Whether you use the AWS Console GUI, CLI, or Python SDK, Polly lets you bring natural-sounding speech to your applications quickly and securely.

Once you’re comfortable, you can combine Polly with:

  • S3 for audio storage
  • Lambda for serverless processing
  • Transcribe for full speech workflows

Happy building—and enjoy giving your apps a voice 🔊🚀

AWS

Creating an AWS Linux System Running Docker and Managing It with Portainer

Joseph Klimczak No Comments

Running containers in the cloud doesn’t have to be complicated. In this guide, we’ll walk through creating an AWS EC2 Linux instance, installing Docker, and setting up Portainer to manage containers visually and effortlessly.

By the end, you’ll have a lightweight, production-ready Docker host you can control from your browser.

Prerequisites

Before we begin, make sure you have:

  • An AWS account
  • Basic familiarity with Linux and SSH
  • An EC2 key pair for secure access
  • A local machine with SSH installed

Step 1: Launch an AWS EC2 Linux Instance

  1. Log in to the AWS Management Console
  2. Navigate to EC2 → Launch Instance
  3. Choose an AMI:
    • Select Amazon Linux 2 (recommended for stability and AWS compatibility)
  4. Choose an instance type:
    • t2.micro or t3.micro (free tier eligible)
  5. Configure key settings:
    • Attach your key pair
    • Allow SSH (port 22) in the security group
    • Add port 9000 (Portainer UI) and port 80 if you plan to run web apps
  6. Launch the instance 🚀

Once running, copy the public IPv4 address.

Step 2: Connect to the EC2 Instance

From your local terminal:

ssh -i your-key.pem ec2-user@<EC2_PUBLIC_IP>

If successful, you’ll be logged into your Amazon Linux server.

Step 3: Install Docker on Amazon Linux

Update the system:

sudo yum update -y

Install Docker:

sudo amazon-linux-extras install docker -y

Start and enable Docker:

sudo systemctl start docker
sudo systemctl enable docker

(Optional) Allow your user to run Docker without sudo:

sudo usermod -aG docker ec2-user
exit

Reconnect to apply the changes.

Verify installation:

docker --version

Step 4: Run Docker Containers

Test Docker by running a container:

docker run hello-world

If you see the success message, Docker is working correctly 🎉

Step 5: Install Portainer

Portainer gives you a clean web UI to manage containers, images, networks, and volumes.

Create a Docker volume for Portainer

docker volume create portainer_data

Run Portainer

docker run -d \
  -p 9000:9000 \
  --name portainer \
  --restart always \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v portainer_data:/data \
  portainer/portainer-ce

Check that it’s running:

docker ps

Step 6: Access the Portainer Dashboard

Open your browser and go to:

http://<EC2_PUBLIC_IP>:9000

On first launch:

  1. Create an admin password
  2. Select Docker (local) as the environment
  3. Click Connect

You now have full visual control over your Docker host 🎯

What You Can Do with Portainer

With Portainer, you can:

  • Deploy containers using forms or Docker Compose
  • Monitor container health and logs
  • Manage volumes, networks, and images
  • Stop, start, or scale services
  • Secure access with user roles

It’s perfect for:

  • Small production workloads
  • Learning Docker visually
  • Managing remote servers with ease

Security Best Practices

Before using this in production, consider:

  • Restricting port 9000 to your IP only
  • Enabling HTTPS with a reverse proxy
  • Using IAM roles instead of access keys
  • Regularly updating Docker and the OS

Conclusion

By combining AWS EC2, Amazon Linux, Docker, and Portainer, you get a powerful yet simple container platform that scales with your needs. Whether you’re deploying side projects or learning container orchestration, this setup is an excellent foundation.

Happy containerizing 🐳🚀