Ubuntu 24.04 LTS | Production-Ready | Workflow Orchestration
Complete AMI guide for your Temporal Server deployment. Learn how to access the Web UI, connect via gRPC, create workflows, and configure your instance for production use.
Follow these steps to access your Temporal Server and start orchestrating workflows.
Connect to your EC2 instance using SSH with your key pair.
ssh -i your-key.pem ubuntu@<your-instance-ip>
Verify that Temporal Server is running properly.
sudo systemctl status temporal
Open the Temporal Web UI in your browser to monitor workflows.
http://<your-instance-ip>:8080
The Web UI provides a visual interface for monitoring workflows, activities, and task queues.
Connect your workers and clients to Temporal using gRPC.
# gRPC endpoint
<your-instance-ip>:7233
# Using tctl CLI
tctl --address <your-instance-ip>:7233 cluster health
Monitor and manage your workflows through the intuitive web interface.
Connect your Temporal workers and clients using the gRPC API.
The Temporal Server listens for gRPC connections on port 7233.
# gRPC Frontend Service
<your-instance-ip>:7233
Verify the server is healthy using tctl or the health endpoint.
# HTTP health check
curl http://<your-instance-ip>:7233/health
# Using tctl
tctl --address <your-instance-ip>:7233 cluster health
Connect from your Go application using the Temporal SDK.
c, err := client.Dial(client.Options{
HostPort: "<your-instance-ip>:7233",
})
Connect from your Python application using the Temporal SDK.
client = await Client.connect(
"<your-instance-ip>:7233"
)
Learn how to create namespaces and manage workflows using the Temporal CLI.
Namespaces isolate workflows and provide multi-tenancy support.
# Create a new namespace
tctl --address localhost:7233 \
--namespace my-namespace \
namespace register
# List all namespaces
tctl --address localhost:7233 namespace list
Execute workflows using tctl or the SDK.
# Start a workflow execution
tctl --address localhost:7233 \
--namespace my-namespace \
workflow start \
--taskqueue my-task-queue \
--workflow_type MyWorkflow \
--workflow_id my-workflow-id
View running and completed workflows in a namespace.
tctl workflow list
Get detailed information about a specific workflow.
tctl workflow describe -w id
Force stop a running workflow execution.
tctl workflow terminate -w id
Send a signal to a running workflow.
tctl workflow signal -w id -n signal
Query workflow state without affecting execution.
tctl workflow query -w id -qt type
View the complete event history of a workflow.
tctl workflow show -w id
Secure your Temporal deployment with proper firewall rules and best practices.
Important: By default, Temporal does not have authentication enabled. Restrict access using AWS Security Groups and consider enabling mTLS for production deployments.
Configure inbound rules to restrict access to trusted IPs only.
Restrict to your application servers and worker instances.
Restrict to admin IPs or use a reverse proxy with authentication.
| Port | Protocol | Source | Description |
|---|---|---|---|
22 |
TCP | Your IP | SSH access |
7233 |
TCP | VPC CIDR / Worker IPs | gRPC Frontend Service |
8080 |
TCP | Admin IPs | Web UI |
Common issues and how to resolve them.
Symptom: Connection refused or timeout when connecting to port 7233.
Solution:
7233sudo systemctl status temporalsudo journalctl -u temporal -fSymptom: Browser shows connection refused or timeout.
Solution:
8080sudo systemctl status temporal-uiSymptom: Temporal service fails to start or crashes.
Solution:
sudo journalctl -u temporal -n 100sudo systemctl status postgresqldf -hSymptom: "namespace not found" error when running workflows.
Solution:
tctl namespace register my-namespacetctl namespace listdefaultCommon commands for managing the Temporal services.
# Start Temporal
sudo systemctl start temporal
# Stop Temporal
sudo systemctl stop temporal
# Restart Temporal
sudo systemctl restart temporal
# View Temporal logs
sudo journalctl -u temporal -f
# View Web UI logs
sudo journalctl -u temporal-ui -f
# View last 100 lines
sudo journalctl -u temporal -n 100
Our team is available 24/7 to assist you with any questions or issues.
support@flowopsconsulting.co.uk