Skip to main content

Interface: DeploymentConfigOptions

Deployment configuration options can adjust how the LunaSec stack is deployed to AWS.

Properties

grants

grants: GrantConfigOptions

Defined in

types.ts:185


metrics

metrics: MetricConfigOptions

Defined in

types.ts:186


debug

debug: boolean

Turn on verbose logging for the deployed tokenizer backend. Defaults to false.

Defined in

types.ts:194


applicationFrontEnd

Optional applicationFrontEnd: string

[required] The front end of your application where you will be including LunaSec Secure Components.

Defined in

types.ts:162


applicationBackEnd

Optional applicationBackEnd: string

The back end of your application where LunaSec will be registered. If specified, the tokenizer will use this URL to request the public key used to sign tokenizer sessions.

Defined in

types.ts:166


authProviders

Optional authProviders: Record<string, JwksAuthProviderConfig>

Authentication providers lets you specify multiple providers for identity for session validation. This option will override applicationBackEnd as the authentication provider

Defined in

types.ts:170


localStackUrl

Optional localStackUrl: string

Only used for local deployments to localstack. The URL for LocalStack.

Defined in

types.ts:174


serviceVersions

Optional serviceVersions: ServiceVersions

Pin services to specific versions. This is discouraged as the LunaSec stack is meant to be deployed using the same version for every component, but if a service is breaking, it could be helpful to revert specific services as a hot patch.

Defined in

types.ts:180


localBuildArtifacts

Optional localBuildArtifacts: boolean

Only used when building locally. Use local build artifacts when bringing up the stack, built by the monorepo.

Defined in

types.ts:184


frontEndAssetsFolder

Optional frontEndAssetsFolder: string

Only used when building locally. Specify the build location of where the built secure frame iframe exists.

Defined in

types.ts:190