• /
  • EnglishEspañolFrançais日本語한국어Português
  • Inicia sesiónComenzar ahora

Prerequisites for CCI

preview

We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview program pursuant to our pre-release policies.

Prepare your AWS environment for Cloud Cost Intelligence (CCI) integration by following these prerequisites, including setting up consolidated billing, enabling cost and usage reports, configuring IAM roles and policies for secure access, and activating necessary AWS regions. Ensure your setup supports effective cost analysis and management within the New Relic platform.

Prerequisites

Prerequisites for real-time cost estimation

To enable real-time estimated cost viewing in CCI, ensure you meet the specific prerequisites associated with your instrumentation method:

MethodDescriptionWhen to choosePrerequisites
Infrastructure agent and integrationsUses the New Relic Infrastructure Agent for detailed monitoring.Select for deep visibility/control, ideal for standalone EC2, EKS/EC2, or ECS/EC2 setups.
  • If you have standalone EC2, install the New Relic infrastructure agent.
  • If you have EKS/EC2, install the Kubernetes integration.
  • If you have ECS/EC2, install the ECS integration. This method is not supported for AWS Fargate.
Cloud integration (metrics)Utilizes AWS CloudWatch metrics for near real-time monitoring.Opt when real-time data is essential. Suitable for dynamic environments needing up-to-date insights.Set up Amazon CloudWatch Metric Streams.
Cloud integration (polling) - legacyCollects data by polling AWS services at intervals.Suitable for environments tolerating less frequent updates. Legacy option used when metrics-based approach is less feasible.Set up AWS polling integrations.

Prerequisites for Kubernetes cost allocation

  • Install the Kubernetes integration. AWS Fargate integration is not supported for this feature.
  • Beyond the standard Kubernetes labels (app.kubernetes.io/name, app.kubernetes.io/instance, app.kubernetes.io/component, and app.kubernetes.io/part-of), consider adding two custom labels such as environment and team to indicate the deployment environment and the responsible team. Also, consider adding two custom resource tags such as project and costCenter. These labels and resource tags will help you better segment and analyze your Kubernetes cost allocation data.

Recommendations

  • Configure cost allocation tags in your AWS account. Tagging facilitates detailed and meaningful cost categorization. Ensure that at least two custom resource tags are consistently applied across your AWS resources for effective cost filtering and grouping.
  • Use an S3 bucket located in the us-east-2 region for optimal performance and cost efficiency.

Access control advisory

All users with access to the designated New Relic account/organization can view your AWS cloud cost data within Cloud Cost Intelligence. We encourage you to carefully select the appropriate New Relic account/organization that aligns with your internal access control policies to ensure secure and compliant handling of cloud cost data.

Importante

S3 bucket access

New Relic only requires read access to your S3 bucket, and this access is limited to a single IAM role from the New Relic side. Ensure that this access level is maintained to protect your data while facilitating necessary operations.

Copyright © 2025 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.