# 12-Nov-2026 — copy S3 across regions with per-bucket credentials and seed a default banner [#231](https://github.com/Ramblers-GB/ngx-ramblers/issues/231)

## [build 1082](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/43395923344) — [commit 89caeb1](https://github.com/Ramblers-GB/ngx-ramblers/commit/89caeb1b43bb651034bb2c6d18aeb1654d22c245)

_____

## What's new

- Copy standard assets and group logos by reading from the source bucket and writing to the destination, following each bucket's region, so files in the Ireland staging bucket copy into a new London bucket.
- Copying standard assets and a full S3 duplicate uses the AWS credentials that own each bucket, so a London group bucket can be filled from the Ireland staging assets bucket without a shared admin key.
- New sites get a unique bucket name that includes `eu-west-2`, and Environment Setup / site registration use that name and region when creating AWS resources.
- Environment management has a Default logo banner step that creates a banner when none exist, and adds a banner picture to an existing banner that is missing one. The step is safe to re-run.
- The copy-assets, sample pages and notification steps say that they fill what is missing and leave existing records in place.
- Resuming provision for a site that already has a Mongo user sets Atlas back to the password already stored for that environment, then waits for login.
- Estate deploy passes the environment's Fly VM memory into `flyctl deploy`.