/
Kubernetes - S3 Storage

Kubernetes - S3 Storage

Scope AR requires storage for CMS content and Worklink Create project files. It is highly recommended that your organization has access to AWS S3. You will need two S3 buckets provisioned. Please ensure that the buckets are named with helpful identifiers such as companyA-cms-storage and companyA-wlc2-storage.

Bucket Policy

If utilizing IAM authentication, ensure that the s3:GetObject, s3:PutObject, and s3:ListBucket permissions are granted to both the CMS and WorkLink Create EKS Role ARNs, as defined in section 2.2 of this document.

If you are not using IAM authentication, grant the same permissions to the IAM user whose access and secret keys are specified as secrets (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) in the deployment configuration.

CORS Policy

The CORS bucket policy must also allow your organization’s CMS and Worklink Create domains to be an allowed origin. The CORS policy will need to be configured on both S3 buckets. Below is an example:

[     {         "AllowedHeaders": [             "*"         ],         "AllowedMethods": [             "GET"         ],         "AllowedOrigins": [             "cms.example.com", "create.example.com"         ],         "ExposeHeaders": [],         "MaxAgeSeconds": 3000     } ]

 

 

Related content