Cisco Cloud APIC for AWS Installation Guide, Release 5.2(x)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Cloud APIC for AWS Installation Guide, Release 5.2(x)

Chapter Title

AWS Resources and Naming Conventions

Results

Updated:
January 20, 2021

Chapter: AWS Resources and Naming Conventions

AWS Resources and Naming Conventions

AWS Resources and Naming Conventions

Following is a list of AWS resources created by the Cloud APIC when it is installed, and the naming conventions used in the Cloud APIC. Use the information in this list to better understand these AWS resources and to avoid using similar names.

Item

Number of Items Used

Naming Convention for Item

S3 buckets

  • One global (used to store the CFT templates)

  • One per region (used to store the CloudTrail logs)

Cloud APIC S3 buckets begin with the prefix capic. Avoid using buckets that begin with this prefix.

Tags

Minimum of two, maximum of eight

Following are the tag keys used:

  • AciDnTag

  • AciOwnerTag

  • Name (tag value contains object relative name, or RN)

  • AciStaleTag (present only if a resource is considered stale by Cloud APIC)

  • AciResolvedObjDnTag (only for VPC – it carries the Distinguished Name, or DN, for the resolved object)

  • AciPeerDnTag (only for VPC peering – it carries the DN for the peer VPC)

Avoid creating tags starting with Aci or Capic.

CloudTrails

One per region

Trail names begin with the prefix capic. Avoid creating trails that begin with this prefix.

CloudWatch events

Three per region

Rules begin with the prefix capic. Avoid creating rules that begin with this prefix.

Simple Queue Service (SQS) queues

One per region

Queue names begin with the prefix capic. Avoid creating queues that begin with this prefix.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco