Configuring YOUnite Services in an AWS Implementation

It is recommended to have an Elastic IP associated with the instance, otherwise a significant amount of configuration work will need to be repeated each time the instance is restarted.

Locate an existing Elastic IP associated with the account within EC2 → Network & Security → Elastic IPs

If there are no non-Associated Elastic IPs available for the accound then select Allocate Elastic IP Address, select Amazon’s pool of IPV4 Adresses, then select Allocate

Once the Elastic IP address is created, assign a name to it.

Prior to creating a Security Group, identify the VPC that you will use. You have the option to use the default VPC associated with your account, or you can choose to create a separate VPC to isolate YOUnite’s traffic. Navigate to EC2 → Security Groups → Create Security Group

Define the Security Group Name and Description for the Security Group and note the VPC to apply this Security Group to the Instance when it is launched.

Select Add Rule and add the following Inbound Rules:

Also, include the following Inbound Rules if running the “Biz Demo” and you want to access the databases from outside AWS (with DBeaver):

When all rules have been added, click Create Security Group

Use an existing key pair or navigate to EC2 → Key Pairs and select Create Key Pair

A myKeyPair.pem file will be created which will be required to ssh into the AWS instance to be created.

On the EC2 main page select Launch Instance.

Make the following selections on the Launch and Instance page:

Associating an Elastic IP to the instance is required so that a static IP address is maintained whenever the instance is restarted.

Create a YOUnite hostname such as aws.mycompany.org, in your local host file (/etc/hosts) with the corresponding Elastic IP.

For example, assuming your Elastic IP address is 52.1.51.239, here is a sample:

Login to the instance using the .pem file and the YOUnite hostname name added earlier to the local /etc/hosts file.

Use the user name: ec2-user

Remember to run:

Example login:

Open the /etc/hosts file and append the YOUnite Hostname to the end of the localhost entry:

Edited host entry:

Test:

Run aws configure entering the ECR Access keys mentioned in the Prerequisites section and AWS region for the instance.

Add the following and save:

Apply the change to the running instance:

Perform the following two edits and restart docker:

Add the following and save:

And edit the following line and save:

Restart Docker:

Define the following environment variable in each within each shell running YOUnite services:

This line may also be added to the .bashrc file.

Start the Basic Stack:

Once start.sh completes, you can optionally start the BizDemo:

To avoid AWS charges when the instances are not in use, be sure to stop the instance whenever you are finished running YOUnite.

Since an Elastic IP is configured, the instances can be restarted at any time using Instance State → Start Instance

If you want to user Postman, create a new "aws" environment and set the token_href and href variables using your YOUnite hostname

If configuring the Biz Demo, connect to the four databases with DBeaver using the following information.

See Biz Demo for further reference.

Docker Desktop and DockStation only run locally on the system so to manage the instance, you must login to the instance and use Docker and Docker Compose command line tools.