Static Publisher 1.0.26 – Deployment identities for multi-account publishing

Changes

Static Publisher 1.0.26 adds explicit AWS shared-config profile selection for deployment targets, making it possible to publish multiple WordPress sites from one coordinator while using separate AWS accounts and roles.

What’s new

• Added an optional AWS profile setting to the base deployment target.
• Added independent AWS profile selection to subscription-backed deployment profiles.
• Named profiles can be used for local S3 uploads and CloudFront invalidations without storing AWS access keys in WordPress.
• Temporary credentials attached to an individual queued job continue to take precedence over configured profile names.
• Added strict profile-name validation across WordPress, Publisher Core, and the exporter.
• Documented the separation between coordinator-side AWS profiles and CDK-allowlisted Lambda deployment roles.
• Added support for target-specific cross-account roles and external IDs.

Updated components

• Publisher Core 1.1.11
• Publisher Admin 1.0.13
• Static Publisher Exporter 1.1.81 or newer

Upgrade notes

Install the compatible exporter on the coordinator and restart the external queue runner.

For delegated cross-account deployment, update the Lambda worker stack with the target account’s S3-only deployment role and external ID, then reinstall the generated remote-workers.json.

The AWS profile configured in WordPress must exist for the operating-system user running the exporter. WordPress stores only the profile name, never its credentials.

Exporter 1.1.82 is recommended once available because it also contains the latest cross-account S3 streaming, relative URL rewriting, and rendered runtime-DOM fixes.