Deployment guide

Firebird SQL on Windows

Overview

Firebird is a relational database management system that offers ANSI SQL compliance, ACID transactions, and support for stored procedures, triggers and views.

This guide covers deploying and configuring Firebird SQL on Windows Server from SecureAnyCloud's AMI on the AWS Marketplace. The AMI gives you a running Firebird server and a Remote Desktop session to manage it.

What you get:

  • Firebird SQL 4 with the database listener on port 3050
  • The FirebirdSQL Windows service, which starts automatically on boot
  • Windows Server with Remote Desktop access
  • 24/7 SecureAnyCloud support with a guaranteed 24-hour response SLA

Prerequisites

Before you launch this AMI, make sure you have:

  • An active AWS account.
  • An active subscription to the Firebird SQL on Windows listing on AWS Marketplace.
  • An EC2 key pair for password decryption.
  • A Remote Desktop client application.

Recommended instance type: t3.small (2 vCPU, 2 GB RAM) or larger. The minimum requirements are 1 vCPU, 1 GB RAM and 20 GB of disk space.

1

Launch the AMI

  • Open the AWS Marketplace and search for "Firebird SQL Windows SecureAnyCloud".
  • Click Continue to Subscribe, accept the terms, then click Continue to Configuration.
  • Select your preferred Region and Software Version.
  • Click Continue to Launch.
  • Choose Launch through EC2 for full control over instance configuration.
  • Select your instance type (t3.small recommended).
  • Configure storage: 20 GB gp3 minimum.
  • Configure your Security Group with the inbound rules listed below.
  • Select your EC2 key pair and launch the instance.

The security group needs these inbound rules (port, protocol, source, purpose):

Port 3389, TCP, from your IP: Remote Desktop (RDP) access.

Port 3050, TCP, from your IP: Firebird SQL database listener for remote connectivity.

Important: Restrict port 3050 to trusted application servers or your IP only.

2

Retrieve the Windows password

Wait for the EC2 instance to pass its 2/2 status checks, then:

  • Open the AWS Console and go to EC2 > Instances.
  • Select your instance.
  • Click Actions > Security > Get Windows password.
  • Click Browse and upload your EC2 key pair .pem file.
  • Click Decrypt password.
  • Note the Username (Administrator) and the decrypted Password.

Important: The Windows password can take up to 15 minutes after launch to become available.

3

Connect via Remote Desktop

Open your Remote Desktop client.

On Windows: Press Win + R, type mstsc and press Enter. Enter the public IP address of your instance, then click Connect.

On macOS: Open Microsoft Remote Desktop and click Add PC. Enter the public IP address, then double-click the connection to connect.

When prompted, enter Username: Administrator and Password: the decrypted value from Step 2.

If a certificate warning appears, click Continue.

4

Verify the Firebird SQL service

The FirebirdSQL service starts automatically on boot. To verify it in Windows Services:

  • From the Start Menu, search for Services and open it.
  • Locate FirebirdSQL in the list.
  • Confirm that the status shows Running.
5

Connect to Firebird SQL

Use a Firebird-compatible database client and these connection settings:

  • Host: localhost (from within the instance) or the public or private IP address (remote)
  • Port: 3050
  • Username: SYSDBA
  • Password: the default Firebird SYSDBA password (typically masterkey unless changed)

Managing the Firebird SQL service

FirebirdSQL runs as a Windows service and starts automatically on boot.

To manage it in Windows Services:

  • From the Start Menu, search for Services and open it.
  • Locate FirebirdSQL in the list.
  • Right-click the service and choose Start, Stop or Restart.

To manage it with PowerShell:

# Check Firebird service status Get-Service -Name "FirebirdServer*"
# Stop Firebird Stop-Service -Name "FirebirdServer*"
# Start Firebird Start-Service -Name "FirebirdServer*"

Server components

The server component is Firebird SQL 4.

Filesystem layout

The C:\ drive is the system drive, with Windows and the Firebird SQL installation.

Key directories:

C:\Program Files\Firebird: Firebird SQL installation

C:\Program Files\Firebird\Firebird_4_0: Firebird 4 binaries and configuration

Troubleshooting

Cannot connect to Firebird on port 3050

  • Verify that the FirebirdSQL service is running in Windows Services.
  • Check that your security group allows port 3050 from your IP.
  • Check that Windows Firewall is not blocking port 3050.
  • Verify that the listener is active: netstat -an | findstr 3050

Cannot connect via RDP

  • Verify that the instance has passed its 2/2 status checks.
  • Check that your security group allows port 3389 from your IP.
  • Wait up to 15 minutes for the Windows password to become available.

Security Recommendations

  • Change the SYSDBA password immediately after deployment.
  • Change the Windows Administrator password after your first login.
  • Restrict port access. Allow port 3050 only from trusted IP addresses.
  • Create application-specific users with limited privileges.
  • Enable Windows Update. Keep the operating system patched with the latest security updates.
  • Back up databases regularly using the Firebird gbak utility.

Support

If you run into any issues with this product, contact SecureAnyCloud support:

  • Email: sales@secureanycloud.com
  • Website: secureanycloud.com
  • Support hours: 24/7 with a guaranteed 24-hour response SLA

Deploy on AWS

Launch Firebird SQL on Windows with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com