Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Commit a55adc0

Browse files
authored
localstack release 4.1 (#1628)
1 parent 34e1f50 commit a55adc0

File tree

5 files changed

+37
-2
lines changed

5 files changed

+37
-2
lines changed

config.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ enable = true
205205

206206
[params.localstack]
207207
# LocalStack specific configuration values
208-
latest_version = "4.0.0"
208+
latest_version = "4.1.0"
209209

210210
[params.localstack.cli_links]
211211
# Configure the different download links for the cli-binary-download shortcode

content/en/references/configuration.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ This section covers configuration options that are specific to certain AWS servi
9595
| Variable | Example Values | Description |
9696
| - | - | - |
9797
| `BEDROCK_PREWARM` | `0` (default) \| `1` | Pre-warm the Bedrock engine directly on LocalStack startup instead of on demand. |
98-
| `DEFAULT_BEDROCK_MODEL` | `smollm2` (default) | The model to use to handle text model invocations in Bedrock. Any text-based model available for Ollama is usable. |
98+
| `DEFAULT_BEDROCK_MODEL` | `smollm2:360m` (default) | The model to use to handle text model invocations in Bedrock. Any text-based model available for Ollama is usable. |
9999

100100
### BigData (EMR, Athena, Glue)
101101

@@ -257,6 +257,12 @@ Please consult the [migration guide]({{< ref "user-guide/aws/lambda#migrating-to
257257
| - | - | - |
258258
| `REDIS_CONTAINER_MODE` | `1`\|`0` (default) | Start MemoryDB cluster nodes in separate containers instead of in the LocalStack container |
259259

260+
# MSAF
261+
262+
| Variable | Example Values | Description |
263+
| - | - | - |
264+
| `PROVIDER_OVERRIDE_KINESISANALYTICSV2` | `legacy` | Use the older mock Kinesis Analytics provider. |
265+
260266
### MWAA
261267

262268
| Variable | Example Values | Description |

content/en/user-guide/aws/bedrock/index.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,19 @@ $ awslocal bedrock create-model-invocation-job \
127127

128128
The results will be at the S3 URL `s3://out-bucket/12345678/batch_input.jsonl.out`
129129

130+
## Available models
131+
132+
LocalStack's Bedrock emulation supports models from the [Ollama Models library](https://ollama.com/search).
133+
134+
To use a model, retrieve its ID from Ollama and set `DEFAULT_BEDROCK_MODEL` to that ID.
135+
LocalStack will pull the model from Ollama and use it for emulation.
136+
137+
For example, to use the Mistral model, set the environment variable while starting LocalStack:
138+
139+
{{< command >}}
140+
$ DEFAULT_BEDROCK_MODEL=mistral localstack start
141+
{{< / command >}}
142+
130143
## Troubleshooting
131144

132145
Users of Docker Desktop on macOS might run into the issue of Bedrock becoming unresponsive after some usage.

content/en/user-guide/aws/redshift/index.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,3 +143,19 @@ $ awslocal glue get-table \
143143
--database-name $GLUE_DATABASE_NAME \
144144
--name "${REDSHIFT_DATABASE_NAME}_${REDSHIFT_SCHEMA_NAME}_${REDSHIFT_TABLE_NAME}"
145145
{{< / command >}}
146+
147+
## Resource Browser
148+
149+
The LocalStack Web Application provides a Resource Browser for managing RedShift clusters.
150+
You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the **Resources** section, and then clicking on **RedShift** under the **Analytics** section.
151+
152+
<img src="redshift-resource-browser.png" alt="RedShift Resource Browser" title="RedShift Resource Browser" width="900" />
153+
<br>
154+
<br>
155+
156+
The Resource Browser allows you to perform the following actions:
157+
158+
* **Create Cluster**: Create a new RedShift cluster by specifying the cluster identifier, database name, master username, master password, and node type.
159+
* **View Cluster**: View the details of a RedShift cluster, including the cluster identifier, database name, master username, master password, node type, and endpoint.
160+
* **Edit Cluster**: Edit an existing RedShift cluster by clicking the cluster name and clicking the **EDIT CLUSTER** button.
161+
* **Remove Cluster**: Remove an existing Redshift cluster by selecting it from the table and clicking the **ACTIONS** followed by **Remove Selected** button.
574 KB
Loading

0 commit comments

Comments
 (0)