Skip to content

Commit 4a1227f

Browse files
chore: version packages [skip ci]
1 parent cfe6cb0 commit 4a1227f

4 files changed

Lines changed: 10 additions & 9 deletions

File tree

.changeset/fix-bb-agent-multi-region-s3storage.md

Lines changed: 0 additions & 7 deletions
This file was deleted.

package-lock.json

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

packages/bb-agent/CHANGELOG.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,13 @@
11
# @aws-blocks/bb-agent
22

3+
## 0.3.1
4+
5+
### Patch Changes
6+
7+
- cfe6cb0: fix(bb-agent): use the Lambda execution region for S3Storage (#120)
8+
9+
The deployed Agent constructed Strands' `S3Storage` without a `region`, so it defaulted to `us-east-1` and hard-pinned the snapshot S3 client there. Because the session bucket is created in the deploy region, any deployment outside `us-east-1` failed snapshot reads/writes with a cross-region 301 `PermanentRedirect`. `S3Storage` is now constructed with `region: process.env.AWS_REGION` — which the Lambda runtime always sets to the function's region — so snapshots resolve against the correct regional endpoint. `region` and `s3Client` are mutually exclusive in `S3StorageConfig`, so only `region` is passed.
10+
311
## 0.3.0
412

513
### Minor Changes

packages/bb-agent/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@aws-blocks/bb-agent",
3-
"version": "0.3.0",
3+
"version": "0.3.1",
44
"author": "Amazon Web Services",
55
"license": "Apache-2.0",
66
"type": "module",

0 commit comments

Comments
 (0)