Frequently asked questions about Glean’s AWS deployment options, infrastructure requirements, and feature support
Is AWS region _____ supported?
What access to the AWS account is required from Glean?
Why does Glean request the customer to create an admin role?
Will NAF and WAF be managed by Glean?
Which WAF are you using?
Does WAF log to CloudWatch?
Do you apply data protection filters on CloudWatch logs?
What's the path of incoming webhooks?
Can we attach custom security groups to one of the managed services?
Does Glean provide any Intrusion Detection capabilities on AWS?
What are the network requirements?
What OS are the EC2 instances running on and where do the AMIs come from?
Will the OS's be patched by Glean or is that a customer responsibility?
How do we appropriately size our Glean instance?
Can you provide estimates for costs and resource usage?
What GPU instance types are typically needed?
How do we minimize egress cost?
Which database are you using?
How often are SQL backups taken?
Do buckets have Inventory enabled?
Are S3 buckets accessible publicly or from Glean Central?
Is S3 configured for cross-region replication?
What is the purpose of the private lambdas separate from the EKS cluster?
Are the lambdas configured to be publicly accessible?
Do you add layers to lambdas, and if so, are they accessible from outside the organization?
Do you use lambda function URLs?
How does Glean handle Disaster Recovery?
Does Glean on AWS support vanity URLs?
Does Glean on AWS have feature parity with other Glean deployment methods?