AWS Managed Prefix List Standard

Scope: OIT
Type: Standard
Version: 2025

Goal

This document defines the standard naming convention and recommended tags for AWS Managed Prefix Lists

Ownership

This standard is owned by the Cloud Center of Excellence. Direct questions to the sponsor of the CCoE, Sarkis Daglian email redacted

Scope

This standard applies to all newly created, oit-maintained prefix lists.

Timeline & Enforcement

All newly-created prefix lists must be named and tagged in accordance with the standard by the end of 2025.

Terminology

Requirements

Prefix List Naming

Prefix lists should be named with the following format: uci-<descriptive-name>[-pl]

Prefix list names should use kabab case, all lowercase with words seperated by hyphens, not spaces or underscores.

The uci- prefix is used to distinguish UCI-owned prefix lists from AWS-maintained prefix lists, which appear in the same contexts.

The descriptive name should describe the networks included in the prefix list.

The optional -pl suffix can be used when the prefix list is likely to be seen next to other AWS resources, and so needs to be distinguished from those resources.

Prefix List Tagging

As non-cost-incurring, widely shared resources, prefix lists are excepted from the AWS Tagging Standards.

The following are the recommended tags to include on prefix lists in their stead.

Key Value
uci:ProtectionLevel P1, P2, P3, P4
uci:ResponsibleTeam See below for recommended values
Description A short description of the networks within the prefix list

To keep references to specific teams consistent, the following are the recommended values for the uci:ResponsibleTeam tag.

Responsible Team Tag Value
Enterprise Unix Services EUS
Windows Services Group WSG
Middleware Application Infrastructure MAI
Identity Access Management IAM