Create big segment store integration
Create a persistent store integration.
If you are using server-side SDKs, segments synced from external tools and larger list-based segments require a persistent store within your infrastructure. LaunchDarkly keeps the persistent store up to date and consults it during flag evaluation.
You can use either Redis or DynamoDB as your persistent store. When you create a persistent store integration, the fields in the config object in the request vary depending on which persistent store you use.
If you are using Redis to create your persistent store integration, you will need to know:
- Your Redis host
- Your Redis port
- Your Redis username
- Your Redis password
- Whether or not LaunchDarkly should connect using TLS
If you are using DynamoDB to create your persistent store integration, you will need to know:
- Your DynamoDB table name. The table must have the following schema:
- Partition key:
namespace(string) - Sort key:
key(string)
- Partition key:
- Your DynamoDB Amazon Web Services (AWS) region.
- Your AWS role Amazon Resource Name (ARN). This is the role that LaunchDarkly will assume to manage your DynamoDB table.
- The External ID you specified when creating your Amazon Resource Name (ARN).
To learn more, read Segment configuration.
Authorizations
Path Parameters
The project key
The environment key
The integration key, either redis or dynamodb
Body
The global integration settings, as specified by the formVariables in the manifest.json for this integration.
"{\"required\": \"example value for required formVariables property for sample-integration\", \"optional\": \"example value for optional formVariables property for sample-integration\"}"
Whether the integration configuration is active. Default value is false.
false
Tags to associate with the integration
Name to identify the integration
"Sample integration"
Response
Big segment store response
The location and content type of related resources
The integration ID
"12ab3c4d5ef1a2345bcde67f"
The integration key
redis, dynamodb "redis"
The project key
"default"
The environment key
"development"
The delivery configuration for the given integration provider. Only included when requesting a single integration by ID. Refer to the formVariables field in the corresponding manifest.json for a full list of fields for each integration.
Whether the configuration is turned on
true
List of tags for this configuration
Name of the configuration
"Development environment configuration"
Version of the current configuration
1
Details on the connection status of the persistent store integration
Details on the allowed and denied actions for this configuration