Brightspot CMS Developer Guide

AWS Secret Service

The AWS Secret Service provides an integration with the AWS Secrets Manager service for securely storing secrets.

First, ensure that the com.psddev:aws-secret dependency is included in your project’s build.gradle file.

Configuration of the AWS Secret Service is done via environment variables, typically in your Tomcat context.xml file. The key and respective values are described in the table below:

Key Value
brightspot/cms/defaultSecretService The name of the default secret service. This is used in other keys below and is designated as {name}.
(Optional) A prefix value to apply to all key names in AWS Secret Manager. This could be useful if you want to namespace all keys coming from Brightspot with some prefix value to more easily identify them.

The AWS Secrets Service uses the Default AWS Credentials Provider Chain to obtain AWS credentials for the AWS Secret Manager API. This system looks for credentials in a chain of locations including environment variables, system properties, and local credential files. AWS credentials must be provided in one of these locations for the AWS Secrets Service to function.

Previous Topic
Database Secret Service
Next Topic
Building a custom secret service
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Landing pages
Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform, including integrations requiring developer support to use.

Field types
Content modeling
Rich-text elements