Enterprise install
Quilt is a Data Hub for AWS. A Quilt instance is a private portal that runs in your virtual private cloud (VPC).
We encourage users to contact us before deploying Quilt. We will make sure that you have the latest version of Quilt, and walk you through the CloudFormation deployment.
We recommend that all users do one or more of the following:
Each instance consists of a password-protected web catalog on your domain, backend services, a secure server to manage user identities, and a Python API.
Could not load image
Architecture Diagram
- ECS services (e.g., Catalog, Identity Server) run in two availability zones with separate private subnets.
- Amazon RDS (Postgres) stores stack configuration settings only. It is deployed in a multi-AZ configuration for high availability.
- Security groups and NACLs restrict access to the greatest degree possible, by only allowing necessary traffic.
The Quilt CloudFormation template will automatically configure appropriate instance sizes for RDS, ECS (Fargate), Lambda and Elasticsearch Service. Some users may choose to adjust the size and configuration of their Elasticsearch cluster. All other services should use the default settings.
By default, Quilt configures an Elasticsearch cluster with 3 master nodes and 2 data nodes. Please contact the Quilt support team before adjusting the size and configuration of your cluster to avoid disruption.
The infrastructure costs of running a Quilt stack vary with usage. Baseline infrastructure costs start at $620 and go up from there. See below for a breakdown of baseline costs for
us-east-1 at 744 hours per month.Service | Cost |
|---|---|
Elasticsearch Service | $516.83 |
RDS | $75.56 |
ECS (Fargate) | $26.64 |
Lambda | Variable |
CloudTrail | Variable |
Athena | Variable |
Total | $619.03 + Variable Costs |
To check the status of your Quilt stack after bring-up or update, check the stack health in the CloudFormation console.
If you notice slow or incomplete search results, check the status of the Quilt Elasticsearch cluster. To find the Quilt search cluster from CloudFormation, click on the Quilt stack, then "Resources." Click on the "Search" resource.
If your cluster status is not "Green" (healthy), please contact Quilt support. Causes of unhealthy search clusters include:
- Running out of storage space
- High index rates (e.g., caused by adding or updating very large numbers of files in S3)
This deployment does not require an increase in limits for your AWS Account.
In addition to containers running in Fargate, Quilt includes a set of AWS Lambda functions. These lambda functions are not scanned by AWS Marketplace. The code for the lambda functions is open-source and has been verified through an independent security audit.
You will need the following:
- 1.An AWS account
- 2.IAM Permissions to create the CloudFormation stack (or Add products in Service Catalog).
Ensure that your service role is up-to-date with the example before every stack update so as to prevent installation failures.
- 1.The ability to create DNS entries, such as CNAME records, for your company's domain.
- 2.An SSL certificate in the same region as your Quilt instance to secure the domain where your users will access your Quilt instance. For example, to make your Quilt catalog available at
https://quilt.mycompany.com, you require a certificate for either*.mycompany.comor for the following 3 domains:quilt.mycompany.com,quilt-registry.mycompany.comandquilt-s3-proxy.mycompany.comin the AWS Certificate Manager. You may either create a new certificate, or import an existing certificate. The ARN for this certificate or set of certificates is required for use as theCertificateArnELBCloudFormation parameter. - 3.For maximum security, Quilt requires a region that supports AWS Fargate. As of this writing, all U.S. regions support Fargate.
- 4.An S3 Bucket for your team data. This may be a new or existing bucket. The bucket should not have any notifications attached to it (S3 Console > Bucket > Properties > Events). Quilt will need to install its own notifications. Installing Quilt will modify the following Bucket characteristics:
- Permissions > CORS configuration (will be modified for secure web access)
- Properties > Object-level logging (will be enabled)
- Properties > Events (will add one notification)
Buckets in Quilt may choose to enable versioning or disable versioning. It is strongly recommended that you keep versioning either on or off during the entire lifetime of the bucket. Toggling versioning on and off incurs edge cases that may cause bugs with any state that Quilt stores in ElasticSearch due to inconsistent semantics of
ObjectRemoved:DeleteMarkerCreated.- 1.A subdomain that is as yet not mapped in DNS where users will access Quilt on the web. For example
quilt.mycompany.com. - 2.
- 3.A license key or an active subscription to Quilt Business on AWS Marketplace. Click
Continue to Subscribeon the Quilt Business Listing to subscribe then return to this page for installation instructions. The CloudFormation template and instructions on AWS Marketplace are infrequently updated and may be missing critical bugfixes.
You can install Quilt via AWS Marketplace. As indicated above, we recommend that you contact us first.
- 1.Email [email protected] with your AWS account ID to request access to Quilt through the AWS Service Catalog and to obtain a license key.
- 2.Click the service catalog link that you received from Quilt. Arrive at the Service Catalog. Click IMPORT, lower right.
- 3.Navigate to Admin > Portfolios list > Imported Portfolios. Click Quilt Enterprise.
- 4.On the Portfolio details page, click ADD USER, GROUP OR ROLE. Add any users, including yourself, whom you would like to be able to install Quilt.
- 5.Click Products list, upper left. Click the menu to the left of Quilt CloudFormation Template. Click Launch product. (In the future, use the same menu to upgrade Quilt when a new version is released.)
- 6.Continue to the CloudFormation section. Note: the following screenshots may differ slightly fromm what you see in Service Catalog.
- 1.Specify stack details in the form of a stack name and CloudFormation parameters. Refer to the descriptions displayed above each text box for further details. Service Catalog users require a license key. See Before you install Quilt for how to obtain a license key.If you wish to use a service role, specify it as follows:
- 2.Service Catalog users, skip this step. Under Stack creation options, enable termination protection.This protects the stack from accidental deletion. Click Next.
- 3.Service Catalog users, skip this step. Check the box asking you to acknowledge that CloudFormation may create IAM roles, then click Create.
- 4.CloudFormation takes about 30 minutes to create the resources for your stack. You may monitor progress under Events. Once the stack is complete, you will see
CREATE_COMPLETEas the Status for your CloudFormation stack. - 5.To finish the installation, you will want to view the stack Outputs.In a separate browser window, open the DNS settings for your domain. Create the following
CNAMErecords. Replace italics with the corresponding stack Outputs.CNAMEValueQuiltWebHost KeyLoadBalancerDNSNameRegistryHostName KeyLoadBalancerDNSNameS3ProxyHost KeyLoadBalancerDNSName - 6.Quilt is now up and running. You can click on the QuiltWebHost value in Outputs and log in with your administrator password to invite users.
Major releases will be posted to AWS Marketplace. Minor releases will be announced via email and Slack. Join the Quilt mailing list or Slack Channel for updates.
To update your Quilt stack, apply the latest CloudFormation template in the CloudFormation console as follows.
- 1.Navigate to AWS Console > CloudFormation > Stacks
- 2.Select your Quilt stack
- 3.Click Update (upper right)
- 4.Choose Replace current template
- 5.Enter the Amazon S3 URL for your template
- 6.Click Next (several times) and proceed to apply the update
Your previous settings should carry over.
All customer data and metadata in Quilt is stored in S3. It may also be cached in Elasticsearch Service (show in red in the diagram below). No other services in the Quilt stack store customer data.
We recommend using S3 encryption and Elasticsearch Service encryption at rest to provide maximum protection.
User email addresses are stored by the Identity Service in RDS Postgres (part of the Quilt stack). User email addresses are also sent through an encrypted channel to the customer support messaging system (Intercom).
The default Quilt settings are adequate for most use cases. The following section covers advanced customization options.
The Quilt admin must log in and set the default role in order for new users to be able to sign up.
You can enable users on your Google domain to sign in to Quilt. Refer to Google's instructions on OAuth2 user agents and create authorization credentials to identify your Quilt stack to Google's OAuth 2.0 server.
In the template menu (CloudFormation or Service Catalog), select Google under User authentication to Quilt. Enter the domain or domains of your Google apps account under SingleSignOnDomains. Enter the Client ID of the OAuth 2.0 credentials you created into the field labeled GoogleClientId
- 1.Go to Azure Portal > Active Directory > App Registrations
- 2.Click New Registration
- 3.Name the app, select the Supported account types
- 4.Set a Redirect URI from a "Single-page application" to
https://<QuiltWebHost>/oauth-callback - 5.Once the application has been created you will need both its Application (client) ID and Directory (tenant) ID
- 6.Your
AzureBaseUrlwill be of the formhttps://ENDPOINT/TENANT_ID. In most casesENDPOINTis simplylogin.microsoftonline.com. Reference Microsoft identity platform and OpenID Connect protocol and National clouds for further details. - 7.Go to App registrations > Your Quilt app > Authentication > Implicit grants and hybrid flows, and check the box to issue ID tokens
- 8.
Note: You will need Okta administrator privileges to add a new Application.
- 1.Go to Okta > Admin > Applications > Applications
- 1.Click
Create App Integration. A new modal window opens. - 2.Assign
Sign-in methodradio button toOIDC - OpenID Connect. - 3.Assign
Application typeradio button toWeb Application.
- 1.Click the
Nextbutton. - 2.Rename the default
App integration nametoQuiltor something distinctive for your organization to identify it. - 3.
- 4.Configure the new web app integration as follows: 8.1. For
Grant typecheck the following:Authorization Code,Refresh Token, andImplicit (hybrid). 8.2. To theSign-in redirect URIsadd<YourQuiltWebHost>URL. Do not allow wildcard * in login URI redirect. This will be something like the following:https://quilt.<MY_COMPANY>.com/
8.3. Optionally add to the
Sign-out redirect URIs (if desired by your organization). 8.4. For the Assignments > Controlled Access selection, choose the option desired by your organization. 9. Once you click the Save button you will have a new application integration to review. 9.1. If it's undefined, update the Initiate login URI to you <YourQuiltWebHost> URL. 9.2. Copy the Client ID to a safe place 10. Go to Okta > Security > API > Authorization servers 10.1. You should see a default entry with the Audience value set to api://default, and an Issuer URI that looks like the following: https://<MY_COMPANY>.okta.com/oauth2/default See Okta authorization servers for more. 11. Proceed to Enabling SSO- 1.Go to Administration : Applications > Custom Connectors
- 2.Click
New Connector- 1.Name the connector Quilt Connector or something similar
- 2.Set
Sign on methodtoOpenID Connect - 3.Set
Login URLtohttps://<QuiltWebHost>/oauth-callback - 4.Save
- 3.Go back to Applications > Custom Connectors
- 4.Click
Add App to Connector - 5.Save the app (be sure to save it for the Organization)
- 6.Go to Applications > Applications > Your new app > SSO
- 1.Click SSO. Copy the Client ID and Issuer URL V2 to a safe place.
- 7.Add Your new app to the users who need to access Quilt
- 8.
Now you can connect Quilt to your SSO provider. In the Quilt template (AWS Console > CloudFormation > Quilt stack > Update > Use current template > Next > Specify stack details), set the following parameters:
- AuthType: Enabled
- AuthClientId: Client ID
- AuthBaseUrl: Issuer URL V2
These instructions document how to set up an existing role for use with Quilt. If the role you want to use doesn't exist yet, create it now. For guidance creating IAM roles, see: IAM best practices, and the Principle of Least Privilege
Go to your Quilt stack in CloudFormation. Go to
Outputs, then find RegistryRoleARN and copy its value. It should look something like this: arn:aws:iam::000000000000:role/stackname-ecsTaskExecutionRole.Go to the IAM console and navigate to
Roles. Select the role you want to use. Go to the Trust Relationships tab for the role, and select Edit Trust Relationship. The statement might look something like this:{
"Version": "2012-10-17",
"Statement": [
"... one or more statements"
]
}
Add an object to the beginning of the Statement array with the following contents:
{
"Effect": "Allow",
"Principal": {
"AWS": "$YOUR_REGISTRY_ROLE_ARN"
},
"Action": "sts:AssumeRole"
},
Note the comma after the object. Your trust relationship should now look something like this:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "$YOUR_REGISTRY_ROLE_ARN"
},
"Action": "sts:AssumeRole"
},
"... whatever was here before"
]
}
You can now configure a Quilt Role with this role (using the Catalog's admin panel, or
quilt3.admin.create_role).In order for Quilt to index buckets with SSE-KMS, you must add certain principals to the corresponding key policy. Go to CloudFormation > Your Quilt Stack > Resources and look for IAM roles with the following logical IDs:
AmazonECSTaskExecutionRolePkgEventsRolePkgSelectLambdaRoleSearchHandlerRoleT4BucketReadRoleT4BucketWriteRole
Note the ARN for each of the above logical IDs and add an Allow statement similar to the following to the KMS key policy:
{
"Effect": "Allow",
"Principal": {
"AWS": [
"<RoleARN-1>",
...
"<RoleARN-N>"
]
},
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey"
],
"Resource": "*"
}
All data and metadata in Quilt is stored in S3. S3 data is automatically backed up (replicated across multiple available zones). To protect against accidental deletion or overwriting of data, we strongly recommend enabling object versioning for all S3 buckets connected to Quilt.
No data will be lost if a Quilt stack goes down. The Quilt search indexes will be automatically rebuilt when buckets are added to a new stack.
To protect against data loss in the event of a region failure, enable S3 Bucket Replication on all S3 buckets.
The time to restore varies with storage needs, but a <2-hour recovery time objective (RTO) and <15 minute recovery point objective (RPO) are generally possible.
To restore Quilt in your backup region:
- 1.Create a new Quilt stack from the same CloudFormation template in the backup region.
- 2.Connect the replica buckets (in the backup region) to your Quilt stack. In the Quilt catalog, select "Users and Buckets"->"Buckets" and enter the bucket information.
Support is available to all Quilt customers by:
- online chat (in the Quilt catalog)
Quilt guarantees response to support issues according to the following SLAs for Quilt Business and Quilt Enterprise customers.
Text | Initial Response | Temporary Resolution |
|---|---|---|
Priority 1 | 1 business day | 3 business days |
Priority 2 | 2 business days | 5 business days |
Priority 3 | 3 business days | N/A |
Text | Initial Response | Temporary Resolution |
|---|---|---|
Priority 1 | 4 business hours | 1 business day |
Priority 2 | 1 business day | 2 business days |
Priority 3 | 1 business days | N/A |
- Business Day means Monday through Friday (PST), excluding holidays observed by Quilt Data.
- Business Hours means 8:00 a.m. to 7:00 p.m. (PST) on Business Days.
- Priority 1 means a critical problem with the Software in which the Software inoperable;
- Priority 2 means a problem with the Software in which the Software is severely limited or degraded, major functions are not performing properly, and the situation is causing a significant impact to Customer’s operations or productivity;
- Priority 3 means a minor or cosmetic problem with the Software in which any of the following occur: the problem is an irritant, affects nonessential functions, or has minimal impact to business operations; the problem is localized or has isolated impact; the problem is an operational nuisance; the problem results in documentation errors; or the problem is any other problem that is not a Priority 1 or a Priority 2, but is otherwise a failure of the Software to conform to the Documentation or Specifications;
- Temporary Resolution means a temporary fix or patch that has been implemented and incorporated into the Software by Quilt Data to restore Software functionality.
Last modified 12d ago