Rule 2 - AWS CI-to-CI Relationships

Rule Synopsis

These are the rule/s that automatically determine and create the CI-to-CI relationships (dependencies) for each AWS Resource/CI Type.

Rule Details and Default

The default rule/s are described by the table below which show the default CI-to-CI Relationships per Resource/CI Type.

Resource/CI Types

Relationships

CloudWatch Alarm

  • N/A

DynamoDb Table

  • N/A

EC2 Instance

  • EC2 Instance Use End Point To EC2 Network Interface

  • EC2 Instance Instantiates Computer#1

EC2 Internet Gateway

  • EC2 Internet Gateway Use End Point To EC2 VPC

EC2 Network Interface

  • N/A

EC2 Subnet

  • EC2 Subnet Contains EC2 Instance

  • EC2 Subnet Contains EC2 Network Interface

  • EC2 Subnet Contained by EC2 VPC

EC2 VPC

  • EC2 VPC Contains EC2 Instance

  • EC2 VPC Contains EC2 Network Interface

KMS Alias

  • KMS Alias Uses KMS Key

KMS Key

  • N/A

Lambda Function

  • Lamda Function Sends Data to S3 Bucket#2

  • Lamda Function Sends Data to SNS Topic#2

Elastic Load Balancer

  • Load Balancer Contained by EC2 Subnet

  • Load Balancer Contained by EC2 Subnet

  • Load Balancer Contained by EC2 VPC

RDS DB Instance

  • RDS DB Instance Connected by EC2 Subnet

S3 Bucket

  • N/A

SNS Topic

  • SNS Topic Instantiates Lamda Function#2

SQS Queue

  • SQS Queue Instantiates Lamda Function#2

#1 Please read the Additional Information section for more information about this relationship.

#2 See Override Options section for more information about this relationship.

Override Options

Context

Customers may be seeking more CI-to-CI relationships (dependencies) than those shown above.

Options

  1. Customers can self-enable any additional CI-to-CI relationships (dependencies) identified with footnote #1.

  2. Even more relationships can be added by Syncfish (if the source system offers addtional ones).

Overriding via Connection Settings

Customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:

  1. For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.

  2. For the specific CI Sync Connection Setting/s related to the rule described on this page please read Extended CI Relationships (CI Dependencies) for AWS.

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Additional Information

Syncfish recommend the following FAQ article that explains the difference between Virtual Machine Instance objects/CIs and Virtual Machine objects/CIs.

The FAQ explains each object type, why the exist as separate objects, where they exist in the CMDB and how they relate to one another (i.e. the standard CI-to-CI Relationships or Dependencies created for these objects.

We suggest you read FAQ - Overview of Virtual Machine Instance objects and Virtual Machine objects and the associated CIs.

N/A

Support Model for Rule Overrides

Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?

Answer: Yes (via self-service in the CI Sync UI) for the additional relationships identified by the footnote #1 reference. For even more relationships, customers must request support from Syncfish (and have an active Syncfish Extended Implementation and Support Plan)

Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule

Answer: Either a Silver Plan or Gold Plan (for customers wanting Syncfish assistance to perform overrides of this rule beyond the additional relationships identified by the footnote #1 reference which are addressed via the self-service UI)