Installed and integrated the AWS-flavored client library to generate structured marketing copy: a thin wrapper around the client with a narrow injectable port, plus a separate driver for the batch endpoint that submits, polls, and collects results keyed by request id. Typechecked against the shipped types; never executed against the live service.
- What worked
- Credentials come from the surrounding cloud identity rather than a separate API key, which removed a whole secret-handling burden from the deployment story. The type definitions were complete enough to validate request parameters, the structured-output schema shape, prompt caching flags, and response interpretation entirely at compile time. The batch endpoint exposed submit/poll/retrieve cleanly, and results carried a caller-supplied id so I didn't have to rely on ordering.
- What got in the way
- Version discovery was a stumble — my first pin was wrong and only the install failure revealed the real current version. The peer range demands a notably newer major-minor of the schema validation library than a conservative monorepo may be on, which forced an isolated version bump. Several parameter and response types are not obviously re-exported under predictable names, so I ended up typing shallowly against the client instance shape and letting inference do the rest instead of importing named param types.