Frequently Asked Questions (FAQ)

100MB

Currently, there is no data storage limit for Optical subscriptions.

Currently, there is no data transfer limit for any of the hosting optical subscriptions.

Yes, the data at rest and at transit are encrypted and complies with IM8 DP-2 & DP-3.
Additionally, REST API calls to Optical Content Studios must use the HTTPS protocol. This means that data is encrypted using TLS.

Optical has implemented several measures to ensure high availability and disaster recovery:

• Data Center Redundancy: Optical takes full advantage of Availability Zones provided natively by AWS cloud provider, allowing sites to handle traffic from 3 data centers (1a, 1b, 1c) in Singapore. The Availability Zones (1a, 1b, 1c) setup is sufficient to fulfill traditional disaster recovery requirements by deploying sites across different data centers. Therefore, no additional contingency site is needed for data center downtime concerns.

• Cloud Provider Redundancy: If tenants have concerns about cloud provider downtime, Optical cannot provide multi-cloud services in the near future due to the effort required to setup and maintain another cloud provider. However, tenants can consider the Optical CMS-only setup where they self-host their public web application.

• Regional Redundancy: Optical cannot provide multi-region services due to Singapore data residency requirements. However, tenants can consider the Optical CMS-only setup where they self-host their public web application if they require multi-region deployment.

In the context of VA and PT for the agency website, it is the scope of the Agency and the Agency can utilise GVT(T)20006 for VA and PT.

Yes, there will be a repository for each extension. An example is shown below.

Agency
|- Optical Public Web
|- Extensions
  |- Extension A
  |- Extension BCopy to clipboardErrorCopied

Yes, Agencies/Tenant developers are free to create their data model that suits their business use case.

This is a feature that has to be developed by the tenant developer. Tenant developers can contact the Optical team for more information about how to handle cache invalidation on our CDN if required

Please refer to Optical-Flex.

For example, if a web developer works with multiple agencies and believes a particular extension could benefit others, they may choose to contribute it to the Optical community. However, agencies are free to keep their extensions private for use within their own websites. The Optical team does not require that all extensions be shared.

Currently, Optical does not have an email campaign feature.

CMS Backend: Optical backend CMS follows semantic versioning.

Example: A.1.0

• 0 = minor version or patch
• 1 = major version
• A = major release

Upgrade Policy:

• All minor versions will be automatically pushed
• Major versions and major releases are pull upgrades, meaning tenant developers must follow the EOL (End of Life) policy of the major versions and manually pull from the available releases

Frontend (Public-web): For tenants on Full Flex hosting model and CMS Only model, tenant developers manage the versioning and upgrade of the public-web.

1. Fix a schedule for UAT.
2. Create a merge request into your own repo’s main branch.
3. Get the designated Tech Lead to review code and merge to main branch.
4. Mirroring kicks in and codes gets mirrored to SGTS Gitlab main branch.
5. Deployment pipeline run starts.
6. Build → packages → security tests are run → reports → pushes the image to ECR → deploys to STG
7. Reports will have security findings → Development team to remediate → while agency performs UAT.
8. Tenant developer fixes the security findings or raises security risk acceptance.
9. Repeat steps 3 to 7, until there are no security findings.
10. Deploys to staging
11. Functional UAT is performed.
12. Gets approval from Agency for Production deployment.
13. Agency approves then Production resources are deployed.