Bump the go-dependencies group with 3 updates (#17)

Bumps the go-dependencies group with 3 updates: github.com/aws/aws-sdk-go-v2, github.com/aws/aws-sdk-go-v2/config and github.com/aws/aws-sdk-go-v2/service/secretsmanager.

Updates github.com/aws/aws-sdk-go-v2 from 1.32.4 to 1.43.3

Commits

e022bf5 Release 2026-07-31.2
37db31f Regenerated Clients
743701a Update API model
5555cc0 upgrade to smithy-go v1.27.6 (#3505)
b0c4f28 Release 2026-07-31
8c94f29 Regenerated Clients
d4d7af9 Update endpoints model
3dd4c38 Update API model
2f4fc72 Release 2026-07-30
8348643 Regenerated Clients
Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/config from 1.28.4 to 1.32.34

Commits

e022bf5 Release 2026-07-31.2
37db31f Regenerated Clients
743701a Update API model
5555cc0 upgrade to smithy-go v1.27.6 (#3505)
b0c4f28 Release 2026-07-31
8c94f29 Regenerated Clients
d4d7af9 Update endpoints model
3dd4c38 Update API model
2f4fc72 Release 2026-07-30
8348643 Regenerated Clients
Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/secretsmanager from 1.34.5 to 1.44.3

Commits

70e9f3d Release 2025-09-10
e620ecb Regenerated Clients
b412203 Update endpoints model
89f42ef Update API model
d71b109 Bump smithy go version to allow unused required parameter in endpoint rule se...
f68827f Release 2025-09-09
d1748bf Regenerated Clients
00307c0 Update endpoints model
424be93 Update API model
648027e Release 2025-09-08
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency’s major version (unless you unignore this specific dependency’s major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency’s minor version (unless you unignore this specific dependency’s minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

sunlight-secretmanager

sunlight-secretmanager is a command-line tool to manage a Sunlight CT Log’s private key material.

All CT logs have a private key which they use to create Signed Certificate Timestamps (SCTs) and Signed Tree Heads (STHs). Sunlight does not take this private key as input directly. Instead, its configuration requires two file paths:

A seed file containing at least 32 bytes of random data, from which the log’s ECDSA P-256 key will be derived; and
A PEM file containing the corresponding ECDSA P-256 public key.

The purpose of sunlight-secretmanager is to authenticate to AWS Secrets Manager, retrieve a stored seed, use that seed to derive the corresponding pubkey, and write both files to disk in a tmpfs. It knows what seed to retrieve and where to write the output files by parsing the same config file which configures the Sunlight log itself.

If it successfully retrieves a secret from AWS Secrets Manager but that secret is empty, it will generate a new seed and save it back to AWS before proceeding. This allows for seamless setup of new log shards simply by adding them to Terraform.

Usage

$ sunlight-secretmanager -config /path/to/sunlight/config.yml