Skip to content

Commit

Permalink
localstack release 4.1 (#1628)
Browse files Browse the repository at this point in the history
  • Loading branch information
HarshCasper authored Jan 30, 2025
1 parent 34e1f50 commit a55adc0
Show file tree
Hide file tree
Showing 5 changed files with 37 additions and 2 deletions.
2 changes: 1 addition & 1 deletion config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ enable = true

[params.localstack]
# LocalStack specific configuration values
latest_version = "4.0.0"
latest_version = "4.1.0"

[params.localstack.cli_links]
# Configure the different download links for the cli-binary-download shortcode
Expand Down
8 changes: 7 additions & 1 deletion content/en/references/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ This section covers configuration options that are specific to certain AWS servi
| Variable | Example Values | Description |
| - | - | - |
| `BEDROCK_PREWARM` | `0` (default) \| `1` | Pre-warm the Bedrock engine directly on LocalStack startup instead of on demand. |
| `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. |
| `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. |

### BigData (EMR, Athena, Glue)

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

# MSAF

| Variable | Example Values | Description |
| - | - | - |
| `PROVIDER_OVERRIDE_KINESISANALYTICSV2` | `legacy` | Use the older mock Kinesis Analytics provider. |

### MWAA

| Variable | Example Values | Description |
Expand Down
13 changes: 13 additions & 0 deletions content/en/user-guide/aws/bedrock/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,19 @@ $ awslocal bedrock create-model-invocation-job \

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

## Available models

LocalStack's Bedrock emulation supports models from the [Ollama Models library](https://ollama.com/search).

To use a model, retrieve its ID from Ollama and set `DEFAULT_BEDROCK_MODEL` to that ID.
LocalStack will pull the model from Ollama and use it for emulation.

For example, to use the Mistral model, set the environment variable while starting LocalStack:

{{< command >}}
$ DEFAULT_BEDROCK_MODEL=mistral localstack start
{{< / command >}}

## Troubleshooting

Users of Docker Desktop on macOS might run into the issue of Bedrock becoming unresponsive after some usage.
Expand Down
16 changes: 16 additions & 0 deletions content/en/user-guide/aws/redshift/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,3 +143,19 @@ $ awslocal glue get-table \
--database-name $GLUE_DATABASE_NAME \
--name "${REDSHIFT_DATABASE_NAME}_${REDSHIFT_SCHEMA_NAME}_${REDSHIFT_TABLE_NAME}"
{{< / command >}}

## Resource Browser

The LocalStack Web Application provides a Resource Browser for managing RedShift clusters.
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.

<img src="redshift-resource-browser.png" alt="RedShift Resource Browser" title="RedShift Resource Browser" width="900" />
<br>
<br>

The Resource Browser allows you to perform the following actions:

* **Create Cluster**: Create a new RedShift cluster by specifying the cluster identifier, database name, master username, master password, and node type.
* **View Cluster**: View the details of a RedShift cluster, including the cluster identifier, database name, master username, master password, node type, and endpoint.
* **Edit Cluster**: Edit an existing RedShift cluster by clicking the cluster name and clicking the **EDIT CLUSTER** button.
* **Remove Cluster**: Remove an existing Redshift cluster by selecting it from the table and clicking the **ACTIONS** followed by **Remove Selected** button.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit a55adc0

Please sign in to comment.