docs: update AWS KMS guide for op-alt-da v0.12.0

[jcstein]

Summary

Updates the AWS KMS guide for op-alt-da to reflect changes in v0.12.0:

• Remove cel-key workflow - no longer needed for key import in v0.12.0
• Remove deprecated config fields: alias_prefix, auto_create, import_key_name, import_key_hex
• Add new workflow: create KMS key directly via AWS CLI with ECC_SECG_P256K1 spec
• Update default_key_name to use full alias path format (e.g., alias/op-alt-da/celestia_key)
• Use "POST and get error" approach to discover Celestia address (simpler than manual derivation)
• Fix curl commands to suppress binary output warnings (-s -o /dev/null)
• Add IAM policy example and production setup instructions

Test plan

• Follow the localstack setup steps
• Verify KMS key creation works
• Verify da-server starts with new config format
• Confirm error message shows Celestia address on first POST
• Fund and retry POST to verify blob submission

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refines the AWS KMS integration guide for op-alt-da to align with the v0.12.0 release. The changes focus on simplifying the key management lifecycle by removing manual cel-key operations and deprecated configuration parameters. It introduces a more direct method for creating KMS keys and aliases via the AWS CLI, enhances the user experience for discovering Celestia addresses, and provides comprehensive instructions for production deployments, including necessary IAM policies.

Highlights

• Key Management Simplification: Removed the cel-key utility workflow, simplifying key management by eliminating the need for manual key export and import.
• Configuration Streamlining: Deprecated several celestia.awskms configuration fields, including alias_prefix, auto_create, import_key_name, and import_key_hex, streamlining the configuration.
• Direct KMS Key Creation: Introduced a new workflow for creating KMS keys directly via AWS CLI, specifying ECC_SECG_P256K1 for key spec and SIGN_VERIFY for key usage.
• Updated Key Naming Convention: Updated the default_key_name configuration to require the full alias path (e.g., alias/op-alt-da/celestia_key).
• Simplified Address Discovery: Implemented a 'POST and get error' approach for discovering the Celestia address, simplifying the initial setup process.
• Improved Curl Commands: Modified curl commands to suppress binary output warnings using -s -o /dev/null for cleaner output.
• Enhanced Production Setup: Expanded the production setup instructions with an example IAM policy and updated config.toml guidance for AWS KMS.
• Version Alignment: Updated the guide to reflect compatibility with op-alt-da version v0.12.0.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request provides a significant update to the AWS KMS guide for op-alt-da, aligning it with the changes in v0.12.0. The new workflow is much clearer and simpler, especially the method for discovering the Celestia address. The removal of deprecated fields and the addition of production setup instructions, including an IAM policy example, are excellent improvements.

I've added a few minor suggestions to improve the clarity and correctness of the code examples in the documentation. These are mostly related to removing unnecessary trailing backslashes in shell commands and clarifying a point about AWS KMS alias naming conventions.

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2398/