AWS environments are vast, and with their complexity comes the need for robust discovery tools that help organizations maintain visibility over their cloud assets. At RapDev, we’ve worked with clients across various industries who need to optimize how they track and manage AWS resources. Two major tools provided by ServiceNow for AWS discovery are the Service Graph Connector for AWS and Cloud Discovery. While both tools help organizations manage their AWS environments, they differ in features, setup, and cost. In this blog, we’ll break down the differences and help you determine which tool might fit your needs.

What is the Service Graph Connector for AWS?

The Service Graph Connector (SGC) for AWS is an integration that pulls detailed data from your AWS environment into your CMDB. This connector focuses on service relationships, showing how AWS resources like EC2, S3, and RDS interact. The SGC helps ensure your CMDB maintains accurate, real-time mappings of these services, essential for incident management and understanding infrastructure dependencies.

One significant advantage of the SGC is that it does not require a MID server. Instead, it leverages AWS Config to pull in data, streamlining the setup process for organizations that don’t want the overhead of managing additional infrastructure components. This makes it ideal for teams focused on ease of implementation and needing precise service maps in their CMDB.

What is AWS Cloud Discovery?

AWS Cloud Discovery is a broader tool focusing on identifying AWS resources across your environment. While part of ServiceNow’s Discovery suite, it specifically gathers data on AWS services like EC2 instances, Lambda functions, and security groups.

Cloud Discovery requires a MID server to communicate between ServiceNow and AWS. This setup scans your infrastructure, pulling AWS resources into the CMDB without emphasizing service mapping like the SGC. It provides a comprehensive inventory of your assets, making it useful for IT operations teams seeking broad visibility into their cloud assets.

Costs and Infrastructure Considerations

When deciding between Service Graph Connector for AWS and AWS Cloud Discovery, consider cost implications and infrastructure requirements.

• Service Graph Connector for AWS: SGC relies on AWS Config to track resource changes, which can become costly in large AWS environments due to charges based on the number of configuration items. However, the lack of a MID server simplifies setup and reduces overhead, particularly in smaller environments where AWS Config costs may be minimal.
• AWS Cloud Discovery: AWS Cloud Discovery requires MID servers, introducing infrastructure management tasks but avoiding additional cloud charges. For large-scale environments, the cost of managing MID servers may be lower than AWS Config expenses, especially when tracking many configuration items.

When to Use Service Graph Connector vs AWS Cloud Discovery

• Service Graph Connector: If you need real-time relationship mapping between AWS resources and want to avoid deploying MID servers, SGC is a strong choice. It’s ideal for organizations focused on service maps and incident management. However, the cost of AWS Config should be considered for large environments. AWS Systems Manager would be required for deep discovery on EC2 instances.
• AWS Cloud Discovery: For organizations seeking a broad inventory of AWS resources, Cloud Discovery is preferable. While it requires MID servers, it avoids AWS Config costs, making it financially viable for large environments. It’s suited for teams prioritizing asset tracking and configuration management over detailed service relationships.

How to Choose

Choosing between Service Graph Connector for AWS and AWS Cloud Discovery depends on your organization’s priorities. If you need detailed service relationships and can manage AWS Config costs, SGC offers valuable insights. If cost is a concern and you need a broad inventory, Cloud Discovery may be more cost-effective.

At RapDev, we’ve helped clients implement both tools to improve AWS visibility and management processes. Whether you're seeking detailed service maps or broad discovery capabilities, we can help you navigate AWS discovery and optimize your cloud infrastructure. Reach out if you need assistance selecting the right tool for your environment.