AWS Build Specification

The canonical AWS build specification for RIALTO lives in our Terraform repository.

This page is largely out of date, replaced by the aforementioned Terraform definitions.

Here are some notes that may help building out our Terraform work.

Region

us-west-2

VPCs

https://github.com/sul-dlss/rialto/wiki/Neptune-Lambda-Integration
rialto-core VPC

Security Groups

rialto-core VPC

CloudWatch

https://github.com/sul-dlss-labs/rialto-trigger-rebuild#add-schedule-event

API Gateway

https://github.com/sul-dlss/rialto/wiki/RIALTO-Combine-Core-Integration
each lambda has its own api gateway, and each gateway has a dedicated api key and usage plan for rialto-internal usage

Lambda

All lambdas use same RialtoLambda execution role
sparqlProxy lambda has one trigger: its API Gateway
derivatives lambda has one trigger: SNS
We use CircleCI/GitHub integration to automatically deploy lambdas to AWS.

EC2

one instance running ingest service
one instance running solr
both using same VPC and Security Group

ECS

• triggerRebuild is an ECS task run on a schedule by CloudWatch Events
• RIALTO Webapp is an ECS service
• RIALTO-entity-resolver is an ECS service fronting the data store

Neptune

1 cluster containing 1 instance of class db.r4.xlarge
running within same VPC and using same Security Group as above

SNS

Create one topic per environment (dev/stage/prod) which serves as the backbone/messaging bus for the components