Skip to content

Conversation

stathis-cmnd
Copy link
Contributor

Description

Detailed docs on how to create a AWS KMS key for the BYOK integration.
Add downloadable files.

Links to this docs will be used in the console integration for downloading scripts and providing customers with technical documentation

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)

PR Checklist

  • My changes are for an upcoming minor release and are in the /docs directory (version 8.8).
  • My changes are for an already released minor and are in a /versioned_docs directory.

@CLAassistant
Copy link

CLAassistant commented Oct 9, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

github-actions bot commented Oct 9, 2025

👋 🤖 🤔 Hello, @stathis-cmnd! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.7/.

  • docs/components/saas/byok/create-byok-aws-kms-key.md
  • docs/components/saas/byok/downloads/aws-kms-key-policy.json
  • docs/components/saas/byok/downloads/create-byok-kms-key-multi-region.sh
  • docs/components/saas/byok/downloads/create-byok-kms-key-single-region.sh

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

* Outputs the key ARN for you to provide to Camunda.

**Instructions:**
1. Download the script: [create-byok-kms-key-single-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-single-region.sh).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [create-byok-kms-key-single-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-single-region.sh). Please use relative URLs.

* Outputs both key ARNs for you to provide to Camunda.

**Instructions:**
1. Download the script: [create-byok-kms-key-multi-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-multi-region.sh).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [create-byok-kms-key-multi-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-multi-region.sh). Please use relative URLs.

> before creating the second key.

**Script Reference:**
For creating AWS KMS single-region key Download and run [create-byok-kms-key-single-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-single-region.sh)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [create-byok-kms-key-single-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-single-region.sh). Please use relative URLs.


**Script Reference:**
For creating AWS KMS single-region key Download and run [create-byok-kms-key-single-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-single-region.sh)
For creating AWS KMS multi-region keys Download and run [create-byok-kms-key-multi-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-multi-region.sh)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [create-byok-kms-key-multi-region.sh](https://docs.camunda.io/docs/next/components/saas/byok/downloads/create-byok-kms-key-multi-region.sh). Please use relative URLs.


6. **Edit Key Policy**
* On the review screen, find the **Key policy** section and click **Switch to policy view**.
* Add to or replace with the [key policy](https://docs.camunda.io/docs/next/components/saas/byok/downloads/aws-kms-key-policy.json) we provide to you
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [key policy](https://docs.camunda.io/docs/next/components/saas/byok/downloads/aws-kms-key-policy.json). Please use relative URLs.

@stathis-cmnd
Copy link
Contributor Author

@christinaausley this is a detailed guide on how to create the KMS keys. Links to this doc will be used to support the console operations i.e. links from the console around BYOK should lead in this doc. In addition we can use it as direct reference and link it to https://github.com/camunda/camunda-docs/pull/6634/files#diff-190963c5b7bc0e62f2648f199626a6d28c8b70684b8e50825efce41f5c1f752fR43 Instead of adding the instructions there

The PR also includes the downloaded files the customers can download through the console.

Could you please give your feedback if you agree with this doc and if it needs formation changes? Thank you

cc @Sijoma


6. **Edit Key Policy**
- On the review screen, find the **Key policy** section and click **Switch to policy view**.
- Add to or replace with the [key policy](https://docs.camunda.io/docs/next/components/saas/byok/downloads/aws-kms-key-policy.json) we provide to you
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[all.markdownLinksDontExitToProduction] Improper link format: [key policy](https://docs.camunda.io/docs/next/components/saas/byok/downloads/aws-kms-key-policy.json). Please use relative URLs.

stathis-cmnd and others added 8 commits October 9, 2025 18:24
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- Charges for KMS Key storage will appear on your AWS bill
- Charges for KMS API calls will appear on Camunda's AWS bill
- **For single region the KMS key must be created in the eu-west-1 (Ireland) region**
- **For dual-region backup, the primary key must be in eu-west-1 (Ireland) and the replica/secondary key in a eu-west-2 (London)** No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[prettier] reported by reviewdog 🐶

Suggested change
- **For dual-region backup, the primary key must be in eu-west-1 (Ireland) and the replica/secondary key in a eu-west-2 (London)**
- **For dual-region backup, the primary key must be in eu-west-1 (Ireland) and the replica/secondary key in a eu-west-2 (London)**

@christinaausley
Copy link
Contributor

christinaausley commented Oct 9, 2025

@stathis-cmnd I noticed that this new create-byok-aws-kms-key.md page overlaps quite a bit with the existing aws-external-encryption-setup.md.

Since both guides walk the user through creating and configuring AWS KMS keys for BYOK, it might make sense to merge them into a single, structured flow (e.g., in docs/components/saas/byok/aws-kms-setup.md) to reduce duplication and clarify the end-to-end process:

  • Cluster creation and external encryption setup
  • KMS key creation (CLI or manual)
  • Key policy configuration
  • Key association with the cluster
  • Verification and monitoring

This would give users one place to follow the full workflow and make maintenance easier over time.
WDYT? I am happy to do this if agreed on.

@stathis-cmnd
Copy link
Contributor Author

stathis-cmnd commented Oct 10, 2025

@christinaausley yes that is actually the case. We had in another repo the guides and instructions provided/written by Philipp from AWS. I changed them a bit to be compatible with our use case. So the idea is to merge them in one doc and single source of truth. If you can to the merging that would be great. Thank you

@christinaausley
Copy link
Contributor

christinaausley commented Oct 13, 2025

@mesellings As far as the downloads here, how do you want cases like these handled in the docs? Kept in the docs, and just link to the repo location, or in a separate repo entirely? Alternatively we can incorporate them as details elements, as done with https://github.com/camunda/camunda-docs/pull/6634/files currently.

@christinaausley
Copy link
Contributor

Closing as this was incorporated with https://github.com/camunda/camunda-docs/pull/6634/files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants