Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
AWS Documentation
Create an AWS Account
Contribute to this guide - Amazon EKS
Summary for existing contributorsSetup a local editing environmentUse the github.dev web-based editorEdit a single pageView and set the ID for a pageCreate a new pageInsert an imageCheck style with ValeBuild a local previewAsciiDoc Cheat Sheet

Contribute to this guide

PDF

Anyone can contribute to the best practices guide. The EKS Best Practices Guide is written in the AsciiDoc format on GitHub.

Summary for existing contributors

  • Open the bpg-docs.code-workspace with VS Code to automatically install the AsciiDoc extension.

  • The source files for the AWS Docs website are stored in latest/bpg

  • The syntax is highly similar to markdown.

  • The docs platform only deploys latest/bpg/images. Each of the guide sections has a symbolic link back to this directory. For example, latest/bpg/networking/images points to latest/bpg/images.

Setup a local editing environment

If you plan to edit the guide frequently, setup a local editing environment.

Fork and clone the repo

You need to be familiar with git, github, and text editors. For information on getting started with git and github, see Getting started with your GitHub account in the GitHub docs.

  1. View the EKS Best Practices Guide on GitHub.

  2. Create a fork of the project repo. Learn how to fork a repository in the GitHub docs.

  3. Clone your fork of the project repo. Learn how to clone your forked repository.

Open the VS Code Workspace

AWS recommends using Visual Studio Code from Microsoft to edit the guide. For more information about VS Code, see Download Visual Studio Code and Get started with Visual Studio Code in the Visual Studio Code Documentation.

  1. Open VS Code.

  2. Open the bpg-docs.code-workspace file from the cloned repo.

  3. If this is your first time opening this workspace, accept the prompt to install the AsciiDoc extension. This extension checks the syntax of AsciiDoc files and generates a live preview.

  4. Browse to the latest/bpg directory. This directory holds the source files that deploy to the AWS documentation site. The source files are organized by guide section, such as "security" or "networking".

Edit a file

  1. Open a file in the editor.

    • View the AsciiDoc Syntax to learn how to create headings, links, and lists.

    • You can use Markdown syntax to format text, create lists, and headings. You cannot use Markdown syntax to create links.

  2. Open a live preview of the page.

    • First, press ctrl-k or cmd-k (depending on keyboard). Second, press v. This opens a preview in split view.

AWS suggests using feature branches to organize your changes. Learn how to create branches with git.

Submit a Pull Request

You can create a pull request from the GitHub website or the GitHub cli.

Learn how to create a pull request from a fork by using the GitHub Website.

Learn how to create a pull request by using the GitHub cli.

Use the github.dev web-based editor

The github.dev web-based editor is based on VS Code. This is a great way to edit multiple files and preview content without any setup.

It has support for the AsciiDoc extension. You can do git operations by using the GUI. The web-based editor does not have a shell or terminal for running commands.

You must have a GitHub account. You will be prompted to login if required.

🚀 Launch the GitHub web-based editor.

Edit a single page

You can rapidly update individual pages by using GitHub. Each page contains an "📝 Edit this page on GitHub" link at the bottom.

  1. Navigate to the page in this guide you want to edit

  2. Click the "Edit this page on GitHub" link at the bottom

  3. Click the edit pencil icon on the top right of the GitHub file viewer, or press e

  4. Edit the file

  5. Submit your changes using the "Commit changes…​" button. This button creates a GitHub pull request. The guide maintainers will review this pull request. A reviewer will approve the pull request, or request changes.

View and set the ID for a page

This page explains how to view and set page ID.

The page ID is a unique string that identifies each page on the documentation site. You can view the page ID in the address bar of your browser when you’re on a specific page. The page ID is used for the URL, the filename, and to create cross-reference links.

For example, if you’re viewing this page, the URL in your browser’s address bar will look similar to:

https://docs.aws.amazon.com/view-set-page-id.html

The last part of the URL (view-set-page-id) is the page ID.

Set the page ID

When creating a new page, you need to set the page ID in the source file. The page ID should be a concise, hyphenated string that describes the page content.

  1. Open the source file for your new page in a text editor.

  2. At the top of the file, add the following line. It should be above the first heading.

    [#my-new-page]

    Replace my-new-page with the page ID for your new page.

  3. Save the file.

Note

Page IDs must be unique across the entire documentation site. If you try to use an existing page ID, you’ll get a build error.

Create a new page

Learn how create a new page and update the guide table of contents.

Create page metadata

  1. Determine the page title, and page short title. The page short title is optional, but recommended if the page title is more than a few words.

  2. Determine the ID of the page. This must be unique within the EKS Best Practices Guide. The convention is to use all lowercase, and separate words with -.

  3. Create a new asciidoc file, in a folder if needed, and add the following text to the file:

    [."topic"] [#<page-id>] = <page-title> :info_titleabbrev: <page-short-title>

    For example,

    [."topic"] [#scalability] = EKS Scalability best practices :info_titleabbrev: Scalability

Add to table of contents

  1. Open the file for the parent page in the table of contents. For new top level guide sections, the parent file is book.adoc.

  2. At the bottom of the parent file, update and insert the following directive:

    include::<new-filename>[leveloffset=+1]

    For Example,

    include::dataplane.adoc[leveloffset=+1]

Insert an image

  1. Find the image prefix for the page you are editing. Review the :imagesdir: property in the heading of the file. For examples, `:imagesdir: images/reliability/

  2. Place your image in this path, such as latest/bpg/images/reliability

  3. Determine appropriate alt-text for you image. Write a short high-level description of the image. For example, "diagram of VPC with three availability zones" is appropriate alt-text.

  4. Update the following example with the alt-text and image filename. Insert at the desired location.

    image::<image-filename>[<image-alt-text>]

    For example,

    image::eks-data-plane-connectivity.jpeg[Network diagram]

Check style with Vale

  1. Install the Vale CLI.

  2. Run vale sync

  3. Install the Vale Extension from the Visual Studio Marketplace.

  4. Restart VS Code, and open an AsciiDoc file

  5. VS Code underlines problematic text. Learn how to work with Errors and Warnings in the VS Code docs.

Build a local preview

  1. Install the asciidoctor tool using brew on Linux or MacOS

  2. Open a terminal, and navigate to latest/bpg/

  3. Run asciidoctor book.adoc

    • Review any syntax warnings and errors

  4. Open the book.html output file.

    • On MacOS, you can run open book.html to open the preview in your default browser.

AsciiDoc Cheat Sheet

Basic Formatting

*bold text*
_italic text_
`monospace text`

Headers

= Document Title (Header 1)
== Header 2
=== Header 3
==== Header 4
===== Header 5
====== Header 6

Lists

Unordered Lists:

- Item 1
- Item 2
-- Subitem 2.1
-- Subitem 2.2
- Item 3

Ordered Lists:

. First item
. Second item
.. Subitem 2.1
.. Subitem 2.2
. Third item

Links

External link:  https://example.com[Link text]
Internal link: <<page-id>>
Internal link: xref:page-id[Link text]

Images

image::image-file.jpg[Alt text]

Code Blocks

 [source,python]
 ----
 def hello_world():
     print("Hello, World!")
 ----

Tables

Learn how to build a basic table. 

[cols="1,1"]
|===
|Cell in column 1, row 1
|Cell in column 2, row 1

|Cell in column 1, row 2
|Cell in column 2, row 2

|Cell in column 1, row 3
|Cell in column 2, row 3
|===

Admonitions

NOTE: This is a note admonition.

WARNING: This is a warning admonition.

TIP: This is a tip admonition.

IMPORTANT: This is an important admonition.

CAUTION: This is a caution admonition.

Preview:

Note

This is a note admonition.

Includes

 include::filename.adoc[]

Previous topic:

Host credentials

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.