diff --git a/userguide/assets/aws/single-ami-application-images.png b/userguide/assets/aws/single-ami-application-images.png new file mode 100644 index 000000000..b35752e9c Binary files /dev/null and b/userguide/assets/aws/single-ami-application-images.png differ diff --git a/userguide/assets/aws/single-ami-configuration.png b/userguide/assets/aws/single-ami-configuration.png deleted file mode 100644 index 80c39427f..000000000 Binary files a/userguide/assets/aws/single-ami-configuration.png and /dev/null differ diff --git a/userguide/assets/aws/single-ami-first-screen.png b/userguide/assets/aws/single-ami-first-screen.png new file mode 100644 index 000000000..24d0e99ca Binary files /dev/null and b/userguide/assets/aws/single-ami-first-screen.png differ diff --git a/userguide/assets/aws/single-ami-inbound-new.png b/userguide/assets/aws/single-ami-inbound-new.png deleted file mode 100644 index 1dc03d938..000000000 Binary files a/userguide/assets/aws/single-ami-inbound-new.png and /dev/null differ diff --git a/userguide/assets/aws/single-ami-inbound.png b/userguide/assets/aws/single-ami-inbound.png deleted file mode 100644 index dfb4b2d4c..000000000 Binary files a/userguide/assets/aws/single-ami-inbound.png and /dev/null differ diff --git a/userguide/assets/aws/single-ami-instance-type.png b/userguide/assets/aws/single-ami-instance-type.png new file mode 100644 index 000000000..394f2b249 Binary files /dev/null and b/userguide/assets/aws/single-ami-instance-type.png differ diff --git a/userguide/assets/aws/single-ami-key-pair.png b/userguide/assets/aws/single-ami-key-pair.png new file mode 100644 index 000000000..6ae2c2b73 Binary files /dev/null and b/userguide/assets/aws/single-ami-key-pair.png differ diff --git a/userguide/assets/aws/single-ami-launch.png b/userguide/assets/aws/single-ami-launch.png deleted file mode 100644 index 2f0a84965..000000000 Binary files a/userguide/assets/aws/single-ami-launch.png and /dev/null differ diff --git a/userguide/assets/aws/single-ami-name-tags.png b/userguide/assets/aws/single-ami-name-tags.png new file mode 100644 index 000000000..90754e707 Binary files /dev/null and b/userguide/assets/aws/single-ami-name-tags.png differ diff --git a/userguide/assets/aws/single-ami-network-settings.png b/userguide/assets/aws/single-ami-network-settings.png new file mode 100644 index 000000000..140549729 Binary files /dev/null and b/userguide/assets/aws/single-ami-network-settings.png differ diff --git a/userguide/assets/aws/single-ami-storage.png b/userguide/assets/aws/single-ami-storage.png new file mode 100644 index 000000000..2f937eab7 Binary files /dev/null and b/userguide/assets/aws/single-ami-storage.png differ diff --git a/userguide/aws/how-to-login-to-your-ec2-instance.adoc b/userguide/aws/how-to-login-to-your-ec2-instance.adoc new file mode 100644 index 000000000..e4b8cdf2e --- /dev/null +++ b/userguide/aws/how-to-login-to-your-ec2-instance.adoc @@ -0,0 +1,33 @@ += How to Log In to Your EC2 Instance via SSH + +:card-badge: Premium +:card-title: AWS Deployment +:card-link: https://aws.amazon.com/marketplace/pp/prodview-jvcsq4phzaclw +:card-description: +include::{sourcedir}/includes/premium-card.adoc[] + +== Overview + +Logging in to your EC2 instance is *not required* to run Kill Bill — it is only needed if you want to perform configuration, maintenance, or troubleshooting tasks directly on the instance. This applies to the Single-Tier, Multi-Tier, and CloudFormation AWS deployments. + +To log in, you need: + +* A *key pair*, created or selected when you launched your instance. The private key file must have been downloaded and saved, and its permissions set so it is readable by the owner only. +* An inbound rule in your instance's security group allowing *SSH* access on port `22`. +* The *public IPv4 address* of your instance, available on the EC2 *Instances* dashboard. + +== Logging In + +To login, use the secure shell command: + +`ssh -i PRIVATE_KEY.pem ubuntu@INSTANCE_IP` + +Here PRIVATE_KEY is the pathname where you have stored the private key that was downloaded when you generated your key pair, and INSTANCE_IP is the public IPv4 address of your instance. The private key will not work unless its access controls are set to readable by the owner only. + +On Windows versions before Windows 10, you may need to download a program called PuTTY to enable `ssh`. On Windows 10 and 11, `ssh` is available but may need to be activated through the Settings screen. + +The first time you login, you will see a warning message asking if you want to add this host to your list of hosts. You should answer `yes`. + +You will now be able to explore your instance and perform various configuration and maintenance tasks. To exit from your login, type `exit`. + +NOTE: If you only opened the SSH rule temporarily to perform a maintenance task, consider removing it from your security group afterward to reduce your instance's exposure to the internet. diff --git a/userguide/aws/how-to-maintain-a-single-tier-system.adoc b/userguide/aws/how-to-maintain-a-single-tier-system.adoc index 966c1f91e..fbd1eaf14 100644 --- a/userguide/aws/how-to-maintain-a-single-tier-system.adoc +++ b/userguide/aws/how-to-maintain-a-single-tier-system.adoc @@ -12,7 +12,7 @@ This guide explains how to maintain your single-tier Kill Bill installation on A == Log in -To perform most maintenance tasks you will need to log in to your EC2 instance. Be sure that SSH is enabled on Port 22 in your security group. Login procedures are described in the setup guide (See https://docs.killbill.io/latest/how-to-set-up-a-single-tier-system.html#step_7_login_to_your_instance[Step 7: Login to an Instance]) +To perform most maintenance tasks you will need to log in to your EC2 instance. Be sure that SSH is enabled on Port 22 in your security group. Login procedures are described in https://docs.killbill.io/latest/how-to-login-to-your-ec2-instance.html[How to Log In to Your EC2 Instance via SSH]. == Troubleshooting diff --git a/userguide/aws/how-to-set-up-a-single-tier-system.adoc b/userguide/aws/how-to-set-up-a-single-tier-system.adoc index 6c6b5e74d..16d30b6ec 100644 --- a/userguide/aws/how-to-set-up-a-single-tier-system.adoc +++ b/userguide/aws/how-to-set-up-a-single-tier-system.adoc @@ -3,14 +3,14 @@ :card-badge: Premium :card-title: AWS Deployment :card-link: https://aws.amazon.com/marketplace/pp/prodview-jvcsq4phzaclw -:card-description: +:card-description: include::{sourcedir}/includes/premium-card.adoc[] == Introduction This document describes the procedures for setting up Kill Bill under AWS using the *single-tier* option. This option has limited capabilities but is very easy to setup. It uses a minimum of resources and may be suitable for very simple use cases. Everything you need for this option is bundled in the Kill Bill Amazon Machine Image (AMI) and will be launched on a single virtual Linux system, which AWS calls an *EC2 instance*. -The components of this system include Kill Bill, Kaui, a database manager (DBM), and a load balancer. The EC2 instance runs Ubuntu Linux. The DBM is an instance of https://mariadb.org[MariaDB], an open source version of MySQL. The load balancer is the open source package https://www.nginx.com[Nginx]. This package serves as a front end or reverse proxy, distributing the incoming traffic to either Kill Bill or Kaui based on the incoming port. +The components of this system include Kill Bill, Kaui, a database manager (DBM), and a load balancer, all running on this single EC2 instance. The instance runs Ubuntu Linux. The DBM is an instance of https://mariadb.org[MariaDB], an open source version of MySQL. The load balancer is the open source package https://www.nginx.com[Nginx]. This package serves as a front end or reverse proxy, distributing the incoming traffic to either Kill Bill or Kaui based on the incoming port. The organization of the single-tier system looks like this: @@ -18,18 +18,18 @@ image::../assets/aws/single-tier-ami_deployment.svg[width=750,align=center] In this configuration, Kill Bill and Kaui are deployed within the `tomcat` application server. Requests are handled by `nginx`. Requests received on port 443 are delivered to Kaui, and those received on port 8443 are delivered to Kill Bill. Both Kill Bill and Kaui communicate as needed with the `mysql` databases. -The setup procedure includes nine steps: +The setup procedure includes the following steps: . <> . <> -. <> +. <> . <> . <> -. <> -. <> -. <> -. <> -. <> +. <> +. <> +. <> + +Once your instance is up and running, see <> below for logging in via SSH and replacing the default self-signed certificate. [[step1]] @@ -54,105 +54,114 @@ You should see the following image at the top of your screen: image::../assets/aws/single-ami-subscribe.png[align=center] -Click *Continue to Subscribe*. The next page will give the AWS Terms and Conditions. Accept the terms if asked. You will then see a new message confirming that you have subscribed. Next, click *Continue to Configuration*. +Click *Continue to Subscribe*. The next page will give the AWS Terms and Conditions. Accept the terms if asked. You will then see a new message confirming that you have subscribed. Next, click *Continue to Configuration*, and select *Launch through EC2* as the launch method. + +You should then see the following page, which lets you pick the software version and region and start the launch: + +image::../assets/aws/single-ami-first-screen.png[align=center] + +Accept the defaults (the version dropdown always points at the latest stable release), confirm the *Region* matches the one you selected in Step 1, and click *Launch from EC2*. [[step3]] -== Step 3: Set Up EC2 Configuration +== Step 3: Launch the Instance -The next page will give several configuration options. +This takes you to the *Launch an Instance* page in the EC2 console. This page is organized into several sections that you will fill in one at a time. The first three sections normally need no changes: -image::../assets/aws/single-ami-configuration.png[align=center] +image::../assets/aws/single-ami-name-tags.png[align=center] -Be sure to select the correct region for your account. Also be sure that your software version is 2023.3 or later. Accept the other defaults, and click *Continue to Launch*. +*Name and tags* — Optionally give your instance a name, such as `kill-bill-single-tier`. This is only a label for your own reference in the EC2 dashboard and has no effect on the installation. -The next page will give you several options for the launch method. Choose *Launch through EC2*. +image::../assets/aws/single-ami-application-images.png[align=center] -image::../assets/aws/single-ami-launch.png[align=center] +*Application and OS Images (Amazon Machine Image)* — Because you arrived here from the AWS Marketplace subscription, the Kill Bill AMI is already selected for you. There is nothing to change here; just confirm it shows the Kill Bill AMI as a *Verified provider*. -All other options will disappear. Click *Launch*. +image::../assets/aws/single-ami-instance-type.png[align=center] + +*Instance type* — Defaults to `t2.medium`, which is the minimum instance type recommended for Kill Bill. You can select a larger instance type if you expect heavier load, but `t2.medium` is fine to get started. [[step4]] == Step 4: Create a Key Pair -The next page is headed *Launch an Instance*. Scroll down to the middle of this page, to the box titled *Key Pair (login)* Here you are asked to choose or create a *key pair*. +Scroll down to the *Key Pair (login)* section. Here you are asked to choose or create a *key pair*. -image::../assets/aws/single-tier-keypair.png[align=center] +image::../assets/aws/single-ami-key-pair.png[align=center] -We will create a new key pair. Click *Create Key Pair* to display a pane to be used for the creation. Give the key pair a simple, easy to remember name such as `My-Key-Pair`. Do not change the other options on this pane. Then click *Download Key Pair*. *Important:* You *must* save the private key that will be generated in this step. If you lose this key, you will *not* be able to login to your instance. In addition, you must set the protection for this file so it is readable by the owner only. +We will create a new key pair. Click *Create new key pair* to display a pane to be used for the creation. Give the key pair a simple, easy to remember name such as `My-Key-Pair`. Do not change the other options on this pane. Then click *Download Key Pair*. *Important:* You *must* save the private key that will be generated in this step. If you lose this key, you will *not* be able to login to your instance. In addition, you must set the protection for this file so it is readable by the owner only. [[step5]] == Step 5: Configure Network Settings -Before launching the instance, configure the network settings: +Scroll down to the *Network settings* section: -* Select the VPC where you want to deploy the EC2 instance. -* Choose a *public subnet* within that VPC. -* Ensure *Auto-assign public IP* is *enabled*. +image::../assets/aws/single-ami-network-settings.png[align=center] -This allows the instance to receive a public IP address and be accessible from the internet. If Auto-assign public IP is disabled or a private subnet is selected, you may not be able to access the instance without additional networking configuration. +=== 5.1. VPC and subnet -[[step6]] -== Step 6: Launch Your Instance +Select the *VPC* where you want to deploy the EC2 instance. Every AWS account starts with a *default VPC*, and that default VPC already ships with a *public subnet* in every availability zone, so in most cases there is nothing to create here. -When the key pair is generated, click *Launch Instances*. You should see the screen below: +A subnet is *public* when the route table associated with it has a route for destination `0.0.0.0/0` pointing to an *Internet Gateway* (target `igw-xxxxxxxx`) attached to the VPC, rather than to a NAT Gateway or no route at all. If you are using a custom VPC instead of the default one, use the *Subnet* dropdown to check the details shown for each subnet (availability zone, CIDR), or click *Create new subnet* if you need one. Then, in the VPC console, confirm its route table has a `0.0.0.0/0 -> igw-xxxxxxxx` route before continuing. -image::../assets/aws/single-tier-launching.png[align=center] +=== 5.2. Auto-assign public IP -Your instance is finally launching! To follow what is happening on the EC2 Dashboard, scroll all the way down to the bottom, and click *View all instances* at the bottom right. This will take you to the *Instances* screen which is part of the EC2 Dashboard. +*This defaults to Disable — you must change it to Enable.* Without a public IP, you will not be able to reach the instance from the internet in Step 8, nor log in to it over SSH afterward. -image::../assets/aws/single-ami-instances.png[align=center] +=== 5.3. Firewall (security group) +Leave *Create security group* selected. AWS pre-fills two inbound rules for you, for ports `443` and `8443`. These are the correct ports for this AMI: `443` is handled by `nginx` and forwarded to Kaui, and `8443` is handled by `nginx` and forwarded to the Kill Bill server. Confirm both rules have Source set to `Anywhere (0.0.0.0/0)`. -In a short time, the *Instance State* for your instance should indicate *Running*. Select the checkbox to the left of your instance ID. An information pane should open below with details about your instance. +While you are here, you can also click *Add security group rule* to add SSH access. This is optional — it is only needed if you plan to log in to your instance directly (see <> below): -[[step7]] -== Step 7: Set up Security Group +* Type *SSH*, Protocol `TCP`, Port range `22`, Source `Anywhere (0.0.0.0/0)`. +Your security group should now have two required inbound rules, `443` and `8443`, open to `0.0.0.0/0`, plus the optional `22` rule if you added it. -You are almost set, but there is one more thing you should do, and that is to scroll down in the menu on the left side to select *Security Groups*. You should see a list of two or more groups. Select the group whose name begins with `Kill Bill on AWS`, then scroll to the bottom and select the tab for *Inbound Rules*. You should see: +[[step6]] +== Step 6: Configure Storage -image::../assets/aws/single-ami-inbound.png[align=center] +Scroll down to the *Configure storage* section: -These rules enable the ports that must be open to access Kaui and Kill Bill from a browser. To enable direct login to your instance using SSH, you need to add one more port. Click on *Edit Inbound Rules*. Then add a rule with the following elements: Type: SSH, Protocol: TCP, Port Range: 22, Source: 0.0.0.0/0. Your Inbound Rules should now look like this: +image::../assets/aws/single-ami-storage.png[align=center] -image::../assets/aws/single-ami-inbound-new.png[align=center] +The default of a single 8 GiB `gp3` root volume is sufficient to get started, and no additional file systems (S3, EFS, FSx) are required. Leave *None* selected and leave the rest of this section at its defaults. -Your Kill Bill installation is ready to go! +[[step7]] +== Step 7: Launch Your Instance -[[step8]] -== Step 8: Login to Your Instance +Review the summary panel on the right, then click *Launch Instance*. You should see the screen below: -You have setup access to port 22 in your security group. This will allow you to login directly to your instance from a terminal or command window. You may need to do this to perform some configuration and maintenance tasks that will be described below. +image::../assets/aws/single-tier-launching.png[align=center] -To login, use the secure shell command: +Your instance is finally launching! To follow what is happening on the EC2 Dashboard, scroll all the way down to the bottom, and click *View all instances* at the bottom right. This will take you to the *Instances* screen which is part of the EC2 Dashboard. -`ssh -i PRIVATE_KEY.pem ubuntu@INSTANCE_IP` +image::../assets/aws/single-ami-instances.png[align=center] -Here PRIVATE_KEY is the pathname where you have stored the private key that was downloaded when you generated your key pair, and INSTANCE_IP is the IPV4 address described earlier. The private key will not work unless its access controls are set to readable by the owner only. +In a short time, the *Instance State* for your instance should indicate *Running*. Select the checkbox to the left of your instance ID. An information pane should open below with details about your instance. -On Windows versions before Windows 10, you may need to download a program called PuTTY to enable `ssh`. On Windows 10 and 11, `ssh` is available but may need to be activated through the Settings screen. +[[step8]] +== Step 8: Test your Installation -The first time you login, you will see a warning message asking if you want to add this host to your list of hosts. You should answer `yes`. +Congratulations! Your single-tier installation is ready to go! -You will now be able to explore your instance and perform various configuration and maintenance tasks. To exit from your login, type `exit`. +You can now try to login to Kaui from your browser using the URL `\https://INSTANCE_IP:443` (or simply `\https://INSTANCE_IP`), where INSTANCE_IP is the IPV4 address for your instance, given on your dashboard as *Public IPV4 Address*. If all goes well, this should display the Kaui login screen. +The AMI ships with a self-signed certificate, so your browser will warn you that the connection is not secure or private (for example, Chrome shows *"Your connection is not private"*). This is expected at this stage — it just means the certificate was not issued by a CA your browser trusts yet. You can proceed past the warning (e.g., in Chrome, click *Advanced*, then *Proceed*) to reach the login screen. See <> below for how to replace it with a certificate from a trusted CA. -[[step9]] -== Step 9: Test your Installation +For an introduction to Kaui, see our https://docs.killbill.io/latest/userguide_kaui.html[Kaui Guide]. The default credentials are: `admin` / `INSTANCE_ID`, where INSTANCE_ID is the Instance ID for your EC2 instance (*not* the IP!). The first few requests might be a bit slow as Kill Bill initializes itself. -Congratulations! Your single-tier installation is ready to go! +In addition, you can visit the Kill Bill server using the URL `\https://INSTANCE_IP:8443`. This provides access to certain detailed reports that may be needed for maintenance, including metrics, event logs, and the Swagger API pages. The same certificate warning applies here. -You can now try to login to Kaui from your browser using the URL `\https://INSTANCE_IP:443`, where INSTANCE_IP is the IPV4 address for your instance, given on your dashboard as *Public IPV4 Address*. If all goes well, this should display the Kaui login screen. The browser may complain that your connection is not secure, but it should offer you a way to bypass the problem. +If these logins do not work correctly, review your setup steps carefully, then proceed to the https://docs.killbill.io/latest/how-to-maintain-a-single-tier-system.html[Single-Tier Maintenance Guide]. -For an introduction to Kaui, see our https://docs.killbill.io/latest/userguide_kaui.html[Kaui Guide]. The default credentials are: `admin` / `INSTANCE_ID`, where INSTANCE_ID is the Instance ID for your EC2 instance (*not* the IP!). The first few requests might be a bit slow as Kill Bill initializes itself. +[[optional]] +== Optional Post-Deployment Tasks -In addition, you can visit the Kill Bill server using the URL `\https://INSTANCE_IP:8443`. This provides access to certain detailed reports that may be needed for maintenance, including metrics, event logs, and the Swagger API pages. +The tasks below are not required to run Kill Bill, but you may want to perform them once your instance is up and running. -If these logins do not work correctly, review your setup steps carefully, then proceed to the https://docs.killbill.io/latest/how-to-maintain-a-single-tier-system.html[Single-Tier Maintenance Guide]. +=== Login to Your Instance via SSH -[[step10]] -== Step 10: Add a Certificate +You may want to log in to your instance directly, for example to perform configuration or maintenance tasks. This requires the optional SSH rule from Step 5, and is described in a separate document since it is common to all of our AWS deployments: see https://docs.killbill.io/latest/how-to-login-to-your-ec2-instance.html[How to Log In to Your EC2 Instance via SSH]. -In order to make your site secure, you will need to add a valid X.509 SSL/TLS certificate. The easiest way to add this certificate is to make use of the tool `certbot`, which relies on the free Certificate Authority (CA) `Let’s Encrypt`. This method provides a simple way to obtain and install free certificates. For instructions on creating a certificate using `certbot`, see https://docs.killbill.io/latest/how-to-add-a-certificate-using-certbot.html[How to Add a Certificate Using Certbot]. Once your certificate is setup, you can login securely to Kaui using your CNAME as the URL (e.g., `\https://kaui.mydomain.com`). +=== Add a Trusted Certificate +The self-signed certificate that ships with the AMI is enough to get started, but browsers will always flag it as untrusted. To remove this warning, replace it with a valid X.509 SSL/TLS certificate from a trusted CA. The easiest way to do this is with the tool `certbot`, which relies on the free Certificate Authority (CA) `Let's Encrypt`. This method provides a simple way to obtain and install free certificates. For instructions on installing and using `certbot`, see https://certbot.eff.org[the Certbot documentation]. Once your certificate is setup, you can login securely to Kaui using your CNAME as the URL (e.g., `\https://kaui.mydomain.com`). diff --git a/userguide/aws/tutorial-single-tier.adoc b/userguide/aws/tutorial-single-tier.adoc deleted file mode 100644 index 5571c8daa..000000000 --- a/userguide/aws/tutorial-single-tier.adoc +++ /dev/null @@ -1,83 +0,0 @@ -= Tutorial: Single-Tier Option - - -== Introduction - -In this tutorial you will set up a working environment on AWS with Kill Bill and Kaui using the *single-tier* option. Everything you need for this option is bundled in the Kill Bill Amazon Machine Image (AMI) and can be launched on a single virtual Linux system, which AWS calls an *EC2 instance*. - -== Step 1: Login to AWS - -To begin, log in to Amazon Web Services at https://aws.amazon.com. If you are new to AWS, you will be asked to create an account and provide billing information. You will need to sign in as a *Root User*. This should take you to the *AWS Management Console*, which provides links to all available services. - -Check the upper right corner of your screen to be sure you are in the appropriate *region*. Your EC2 instance will be placed in this region, and may not be accessible from other regions. - - -== Step 2: Subscribe to the Kill Bill AMI - -To start the installation process, point your browser to the Kill Bill AMI at -+++ - -AWS Marketplace - -+++. - -You should see the following image at the top of your screen: - -image::../assets/aws/single-ami-subscribe.png[align=center] - -Click *Continue to Subscribe*. The next page will give the AWS Terms and Conditions. Accept the terms if asked. You will then see a new message confirming that you have subscribed. Next, click *Continue to Configuration*. - -== Step 3: Set Up EC2 Configuration - -The next page will give several configuration options. - -image::../assets/aws/single-ami-configuration.png[align=center] - -Be sure to select the correct region for your account. Accept the other defaults, and click *Continue to Launch*. - -The next page will give you several options for the launch method. Choose *Launch through EC2*. - -image::../assets/aws/single-ami-launch.png[align=center] - -All other options will disappear. Click *Launch*. - -== Step 4: Create a Key Pair - -The next page is headed *Launch an Instance*. Scroll down to the middle of this page, to the box titled *Key Pair (login)* Here you are asked to choose or create a *key pair*. - -image::../assets/aws/single-tier-keypair.png[align=center] - -We will create a new key pair. Click *Create Key Pair* to display a pane to be used for the creation. Give the key pair a simple, easy to remember name such as `My-Key-Pair`. Do not change the other options on this pane. Then click *Download Key Pair*. *Important:* You *must* save the private key that will be generated in this step. If you lose this key, you will *not* be able to login to your instance. In addition, you must set the protection for this file so it is readable by the owner only. - -== Step 5: Configure Network Settings - -Before launching the instance, configure the network settings: - -* Select the VPC where you want to deploy the EC2 instance. -* Choose a *public subnet* within that VPC. -* Ensure *Auto-assign public IP* is *enabled*. - -This allows the instance to receive a public IP address and be accessible from the internet. If Auto-assign public IP is disabled or a private subnet is selected, you may not be able to access the instance without additional networking configuration. - -== Step 6: Launch Your Instance - -When the key pair is generated, click *Launch Instances*. You should see the screen below: - -image::../assets/aws/single-tier-launching.png[align=center] - -Your instance is finally launching! To follow what is happening on the EC2 Dashboard, scroll all the way down to the bottom, and click *View all instances* at the bottom right. This will take you to the *Instances* screen which is part of the EC2 Dashboard. - -image::../assets/aws/single-ami-instances.png[align=center] - - -In a short time, the *Instance State* for your instance should indicate *Running*. Select the checkbox to the left of your instance ID. An information pane should open below with details about your instance. - -== Step 7: Testing - -You can now try to login to Kaui from your browser using the URL `\https://INSTANCE_IP:443`, where INSTANCE_IP is the IPV4 address for your instance, given on your dashboard as *Public IPV4 Address*. If all goes well, this should display the Kaui login screen. The browser may complain that your connection is not secure, but it should offer you a way to bypass the problem. - -For an introduction to Kaui, see our https://docs.killbill.io/latest/userguide_kaui.html[Kaui Guide]. The default credentials are: `admin` / `{EC2 instance ID}`. The first few requests might be a bit slow as Kill Bill initializes itself. - -In addition, you can visit the Kill Bill server using the URL `\https://INSTANCE_IP:8443`. This provides access to certain detailed reports that may be needed for maintenance, including metrics, event logs, and the Swagger API pages. - -