DOC-371: Add Docker flags environment variables for container-spawning services - #846
Open
HarshCasper wants to merge 1 commit into
Open
DOC-371: Add Docker flags environment variables for container-spawning services#846HarshCasper wants to merge 1 commit into
HarshCasper wants to merge 1 commit into
Conversation
HarshCasper
requested review from
quetzalliwrites and
remotesynth
as code owners
August 4, 2026 11:51
Deploying localstack-docs with
|
| Latest commit: |
7086edb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f4b4e55a.localstack-docs.pages.dev |
| Branch Preview URL: | https://docs-agent-doc-371.localstack-docs.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR documents 10 new
<SERVICE>_DOCKER_FLAGSenvironment variables that enable passing custom Docker flags to service containers spawned by LocalStack. These variables follow the same pattern as the existingLAMBDA_DOCKER_FLAGSandECS_DOCKER_FLAGSconfiguration options.Changes
Added documentation for the following environment variables in
src/content/docs/aws/customization/configuration-options.md:BEDROCK_DOCKER_FLAGS- Bedrock (Ollama) containersCODEBUILD_DOCKER_FLAGS- CodeBuild build containersDOCDB_DOCKER_FLAGS- DocumentDB (MongoDB) containersELASTICACHE_DOCKER_FLAGS- ElastiCache containersGLUE_DOCKER_FLAGS- Glue job containersKINESISANALYTICSV2_DOCKER_FLAGS- Kinesis Analytics v2 (Flink) containersKAFKA_DOCKER_FLAGS- Kafka/MSK containersMEMORYDB_DOCKER_FLAGS- MemoryDB containersMQ_DOCKER_FLAGS- Amazon MQ (RabbitMQ) broker containersRDS_DOCKER_FLAGS- RDS MySQL and MSSQL containersSAGEMAKER_DOCKER_FLAGS- SageMaker training and endpoint containersEach variable is documented in its respective service section with:
-v /certs:/certs(illustrating the primary use case of custom CA certificate mounting)LAMBDA_DOCKER_FLAGS."LAMBDA_DOCKER_FLAGSfor detailed usage restrictionsAdditionally, created three new service sections in alphabetical order:
Primary Use Case
The primary use case for these flags is injecting custom CA certificates into service containers, which is critical for customers operating in environments with custom certificate authorities.
Audit Trail
Sources Accessed
src/content/docs/aws/customization/configuration-options.mdagents.mdfor documentation standardsResearch Conducted
LAMBDA_DOCKER_FLAGS,ECS_DOCKER_FLAGS,BATCH_DOCKER_FLAGS, andMWAA_DOCKER_FLAGSare documented to maintain consistencyCoverage Verification
All 10 new environment variables from the upstream PR are documented:
Build Validation
npm run buildcompleted successfullyConfidence & Gaps Assessment
Confidence: High
Gaps: None identified
LAMBDA_DOCKER_FLAGSdocumentation for full specificationsRelated
Important
An AI agent generated this pull request. Review all changes before you merge.