Administer and operate

TLDR: Granica is self-managed software that runs in your public cloud account so there is minimal ongoing management required.

Learn about Granica

• Granica overview
• Granica architecture

Learn about Granica Crunch

• Crunch overview
• How crunching works
• Start a Crunch pilot

Set up monitoring

To give you visibility into your Granica deployment, take advantage of available usage monitoring and audit logging features.

• Enable CloudWatch monitoring
• View status using the Granica dashboard

At this point, you've completed the minimum setup to have a functional Granica deployment. In a production environment, you should also perform or familiarize yourself with the ongoing operational activities that follow.

Ongoing operational activities

The following operations should be performed periodically as needed.

Modify the AZs where Granica is deployed

Granica is deployed as an EKS cluster running in several AZs for high availability. The deployment includes an EKS control plane deployed across a minimum of two AZs, and a data plane deployed in those same two AZs as well as in any additionally specified AZs.

To modify the data plane AZs:

1. SSH into the Granica Admin Server, e.g. with ./setup.sh –login
2. Edit the AZs using the subnet_az_ids list in the ~/projectn.tfvars file

vpc_id="vpc-0622e93d1883b3ed4"
subnet_az_ids=["use1-az1", "use1-az2", "use1-az4"]
public_subnet_ids=["subnet-09cae95dc605232f1", "subnet-01de7fcf4f796e9ca", "subnet-0110ded09f2a321b1"]
private_subnet_ids=["subnet-0b20c643416f40f20", "subnet-044c3e25e1efa11fa","subnet-0ac756d6b5d1168b4"]

3. Edit the associated public and private subnets for your specified AZs
4. Run granica deploy –var-file=projectn.tfvars — this will clean up resources from removed AZs and add required resources in new AZs
5. No changes to client apps are required to use the dynamically created read endpoints in the new AZ(s)

Update your Granica deployment

Granica issues two kinds of software updates, both of which occur non-disruptively:

1. Algorithmic updates do not require any changes to the infrastructure and are pushed automatically from Granica headquarters
2. Infrastructure/feature updates are not pushed automatically and instead require you to run the granica update command from the Granica Admin Server

Recover from a disaster

Follow the procedures in our disaster recovery guide to get back up and running quickly.