Guzzle software gets deployed on a EC2 instance using the pre-built image on the AWS cloud. You can deploy Guzzle on an existing Virtual Network or a new Virtual Network.
You need an AWS account to proceed. You will be billed only for the EC2 instance. The Guzzle image itself is free.
- Open the Guzzle page on AWS marketplace from here. Alternatively, you can login to AWS console, go to AWS Marketplace Subscriptions -> discover products and search Guzzle - DataOps Platform
- If you are creating guzzle instance for first time you have to subscribe the Guzzle - DataOps Platform product by clicking the Continue to Subscribe button on right hand side. Then click on continue to configuration and then below page will open.
- Choose action from where you want to launch the product if it is choosen Launch from website then follow below steps.
- Select the EC2 instance type for the guzzle vm.
- Create or select VPC settings.
- Then select or create new security group with defined firewall rules.
- Select or create a new key pair value to authenticate the EC2 instance.
- Click on launch button to launch the website and the instance is deployed on EC2.
- If the action is choosen Launch from EC2 then follow below steps
- Click on Launch button.
- After that below page will open and define configurations of EC2 instance like the instance type, VPC settings, subnet settings, to define key pair and define security groups with defined firewall rules.
- Click on the Launch instance button to lauch the vm.
Guzzle is available on HTTPS, on the port 443 on the AWS EC2 instance.
To access Guzzle - Launch browser with the URL https://public_IPv4_DNS where public_IPv4_DNS is the instance public IP address (available in the details of your EC2 instance in AWS console).
Guzzle is pre-loaded with a self-signed certificate, so you will get a security warning when you launch it for the first time. Later on you can replace this self-signed certificate with the valid certificate in the VM.
The default username and password for the guzzle software is admin/admin.
Before starting to use Guzzle it is recommended to upgrade Guzzle to latest avaliable version. This can be done by going to top menu Manage->Maintenance->Upgrade.
For better experience it is recommended to use guzzle in chrome browser.
Administrative (command-line) access can be obtained by logging-in through SSH using the credentials specified when creating the virtual machine.
Note: Guzzle app does not run under this VM administrator account, but under
guzzle user id. The administrative account is sudoer, so from its shell, you can use
sudo su — guzzle to get a shell as
You cannot directly login as the
guzzle user. Also
guzzle user is not sudoer.
The Guzzle has one key directory that gets deployed on the VM. These are referred in Guzzle app using following environment variables.
- GUZZLE_PRODUCT_HOME: This is located in the path /guzzle
Environment variables GUZZLE_PRODUCT_HOME are defined in guzzle service startup related configuration. These environment variables are accessible to Guzzle App but by default they are not available when you are on shell as
All operations on these directories (like installing JDBC drivers, …) must be performed as
Guzzle image is based on Ubuntu Server 22.04 LTS. It contains below third party softwares:
- Guzzle (2.4.5) - A standard installation of Guzzle App running under Linux user account
- MySQL Server (8.0) - A local MySQL server database, with a connection to it pre-configured in Guzzle App.
- OpenJDK (1.8.0_292)
- Nginx (1.18) - Nginx reverse proxy exposing Guzzle API server and Guzzle static resources on the standard HTTPS port 443 using a self-signed certificate. For better security, you can provide your own certificate in the directory /guzzle/cacerts.
- Apache Spark (3.1.2)
JDBC drivers and external libraries must be installed by copying the relevant files in the "$GUZZLE_PRODUCT_HOME/libs/ext" folder (See Installing database drivers).
You can either download files from the virtual machine instance or upload them using SSH. Copying into the "$GUZZLE_PRODUCT_HOME/libs/ext" folder must be done as guzzle user.