AWS Licensed Template

After loading the template the Parameter screen will be shown.

1. Stack name : Enter the name for the stack (e.g. my-gb-stack) .

2. CreateS3Bucket : Select whether a new bucket should be created or an existing bucket will be used. S3BucketName further down the parameters list dictates the name of the bucket that will be created or used.

3. EnableCloudFront : Enables AWS CloudFront CDN distribution for HTTPS access and global content delivery.

4. EnableSSH : enable SSH access to the EC2 instance the cluster uses.

5. GraphDatabaseEndpoint : Enter the Neptune cluster endpoint (without https:// prefix). Example: your-neptune-cluster.cluster-abcd1234.us-east-1.neptune.amazonaws.com:8182 . This will be used by the Graph Writer so data created by transfomer executions is written automatically to Neptune.

6. GraphDatabaseType : Choose your Neptune database query language, SPARQL or Neptune-Gremlin. This will configure the transformers and writer to create and write data for Semantic Graph (RDF) or Labelled Property Graph (Neptune-Gremlin) N.B. Testing Models will be available for both graph types but transformer executions can only be performed for the selected graph type.

7. InstanceType : The EC2 instance type for the ECS container instances. Container resources are automatically scaled based on instance type. Availble options are T3.xlarge and T3.2xlarge. T3.xlarge is suitable for smaller development data transformation use cases. T3.2xlarge is appropriate for larger production workloads.

8. KeyName : Select an existing EC2 Key Pair for SSH access (only required if EnableSSH is true).

1. PrivateSubnetAvailabilityZone : (Only Required if using existing VPC) The availability zone of your private subnet e.g. us-east-1c . This must match the AZ of the subnet in PrivateSubnetId. For new VPC creation, this parameter is ignored and auto-detected.

2. PrivateSubnetId : (Only Required if using existing VPC) Select ONE PRIVATE subnet ID for the cluster instances. This subnet must have a route to a NAT Gateway for outbound internet access. Note: Only the first subnet will be used if multiple are provided.

3. ProjectName : A project name to be used for naming resources.

4. PublicSubnetIds : (Required if using existing VPC) Select at least two PUBLIC subnet IDs for the load balancer. RECOMMENDATION: For optimal performance and cost, ensure at least one public subnet is in the same availability zone as your private subnet.

5. S3BucketName : (Optional) Custom S3 bucket name for GraphBuild data storage. If left empty, defaults to 'graph-build-ACCOUNT_ID'. Must be globally unique and follow S3 naming conventions. If CreateS3Bucket has been selected as true previously this is the name of the bucket that will be created.

6. SSHLocation : The IP address range that can be used to SSH to the EC2 instances. WARNING: Default '0.0.0.0/0' allows SSH from anywhere on the internet. For production, restrict to your IP address (e.g., '203.0.113.0/32').

7. StudioLicense : License key for the GraphBuild Studio (required for studio-node).

8. TransformerLicense : License key for the graph transformers and writer.

1. VpcCreationChoice : Select whether to create a new VPC or use an existing one. If your instance of Neptune already exists you will need to use the existing VPC that Neptune is in.

2. VpcId : (Required if using existing VPC) Select an existing VPC to deploy the cluster into e.g. vpc-5ba89652 (should be the VPC Neptune is in) .

After filling in the relevant parameters click 'Next' in the bottom right hand corner.

On the next page all that is required is to fill in the 2 check boxes at the bottom of the page and click 'Next' in the bottom right hand corner.

On the final page click 'Submit' in the bottom right hand corner.

After the stack creation has completed the relevant details needed to work with the stack are in the Outputs tab.