Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud Cost Intelligence content development - Draft #19536

Draft
wants to merge 6 commits into
base: develop
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 54 additions & 0 deletions src/content/docs/cci/getting-started/overview.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
---
title: 'Cloud Cost Intelligence: Take control of your cloud spending'
metaDescription: Gain comprehensive visibility and control over AWS cloud costs with CCI, enhancing your FinOps strategy for holistic cost management.
freshnessValidatedDate: never
---
Cloud Cost Intelligence (CCI) is designed to provide comprehensive visibility and management of AWS cloud costs. Positioned within the growing Financial Operations (FinOps) space, CCI aims to bridge the gap between cost visibility and infrastructure observability, offering you a holistic view of your cloud expenditures.

Check notice on line 6 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L6

[Microsoft.Passive] 'is designed' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is designed' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 6, "column": 31}}}, "severity": "INFO"}

Check notice on line 6 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L6

[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 6, "column": 46}}}, "severity": "INFO"}

Imagine a startup that's expanding its use of AWS services. Tracking and managing these cloud expenses can get overwhelming. CCI helps by showing exactly where money is being spent, so the startup can find areas for cost savings. By aligning cloud spending with usage, startups can better manage their budget while still supporting growth. This ensures that every dollar spent is contributing effectively to the company’s success.

Check notice on line 8 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L8

[Microsoft.Passive] 'being spent' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'being spent' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 8, "column": 170}}}, "severity": "INFO"}

## Key benefits
Here’s how CCI can benefit you:

### Comprehensive cost visibility
- **Breakdown by category:** View cloud costs segmented by product, service, team, and region, enabling detailed analysis and understanding of expenditure.
- **Trend analysis:** CCI provides insights into month-on-month cost trends, average costs, and top cost drivers, helping you identify patterns and potential areas for cost optimization.
- **Anomaly detection:** The platform highlights cost spikes and anomalies, allowing you to quickly identify and address unexpected expenses.

Check notice on line 16 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L16

[new-relic.Adverbs] Consider removing 'quickly'.
Raw output
{"message": "[new-relic.Adverbs] Consider removing 'quickly'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 16, "column": 93}}}, "severity": "INFO"}

### Kubernetes cost allocation
CCI offers visibility into Kubernetes-related costs, including pods and ingress/egress expenses, which is crucial for teams managing complex Kubernetes environments.

### Real-time cost estimation
- **Immediate cost updates:** Unlike traditional tools that have a latency of up to two days, CCI provides near real-time cost updates, reflecting changes within minutes of resource provisioning.
- **Estimation accuracy:** The platform uses telemetry data and historical cost patterns to estimate costs, offering users timely insights into their cloud spending.
<Callout variant="important">
**Disclaimer**<p/>
Real-time cost estimates for the past 48 hours are based on telemetry and historical data, not on actual incurred costs. These estimates offer provisional insights until AWS’s official Cost and Usage Reports (CUR) are available, and are for informational purposes only. These figures may not exactly match the final incurred costs reflected in your official billing statements.

Check notice on line 26 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L26

[Microsoft.Passive] 'are based' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are based' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 26, "column": 52}}}, "severity": "INFO"}
</Callout>

## How CCI retrieves AWS S3 data
CCI automatically accesses your AWS Cost and Usage Reports (CUR), which are stored in your designated S3 bucket. This process begins with your authorization and the provision of access permissions.

Check notice on line 30 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L30

[Microsoft.Passive] 'are stored' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are stored' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 30, "column": 73}}}, "severity": "INFO"}

Once access is established, CCI continuously pulls the latest CUR files from your S3 bucket. This automated and seamless data retrieval ensures that you have the most current financial information available.

Check notice on line 32 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L32

[Microsoft.Passive] 'is established' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is established' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 32, "column": 13}}}, "severity": "INFO"}

<Callout variant="important">
**Data Privacy Notice**<p/>
Customers should ensure that Cost and Usage Reports (CUR) do not contain personal data when used with Cloud Cost Intelligence (CCI). Currently, the CUR does not support data deletion from the New Relic product, so it is crucial to exclude any personal information at the data source.

Check failure on line 36 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L36

[Microsoft.Contractions] Use 'don't' instead of 'do not'.
Raw output
{"message": "[Microsoft.Contractions] Use 'don't' instead of 'do not'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 36, "column": 59}}}, "severity": "ERROR"}

Check failure on line 36 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L36

[Microsoft.Contractions] Use 'doesn't' instead of 'does not'.
Raw output
{"message": "[Microsoft.Contractions] Use 'doesn't' instead of 'does not'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 36, "column": 153}}}, "severity": "ERROR"}

Check failure on line 36 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L36

[Microsoft.Contractions] Use 'it's' instead of 'it is'.
Raw output
{"message": "[Microsoft.Contractions] Use 'it's' instead of 'it is'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 36, "column": 215}}}, "severity": "ERROR"}
</Callout>

### Data analysis and reporting
After retrieving the CUR data, CCI processes and analyzes this information to present actionable insights in its dashboards. You can visualize the financial implications of your cloud usage with clarity, identifying cost drivers and potential areas for optimization.

## Future enhancements
While the initial release focuses on visibility, future iterations of CCI will include advanced features such as cost optimization recommendations. These enhancements will leverage accumulated data and insights to provide actionable suggestions for reducing cloud expenditures.

Check notice on line 43 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L43

[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 43, "column": 215}}}, "severity": "INFO"}

## Differentiation
CCI stands out in the FinOps market through its unique combination of real-time cost estimation and integration with telemetry data. This approach not only provides immediate insights but also aligns cost data with operational metrics, offering a more comprehensive view of cloud resource utilization.

Check notice on line 46 in src/content/docs/cci/getting-started/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/overview.mdx#L46

[new-relic.ComplexWords] Consider using 'use' instead of 'utilization'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'use' instead of 'utilization'.", "location": {"path": "src/content/docs/cci/getting-started/overview.mdx", "range": {"start": {"line": 46, "column": 290}}}, "severity": "INFO"}

## Conclusion
Cloud Cost Intelligence (CCI) is a powerful tool for organizations looking to gain control over cloud expenditures. By providing detailed visibility, real-time updates, and future optimization capabilities, CCI empowers you to make informed decisions and optimize your cloud investments effectively.

## What's next
- [Prerequisites for CCI](/docs/cci/getting-started/prerequisites)
- [Set up CCI](/docs/cci/getting-started/setup)
- [Troubleshoot setup issues]()
208 changes: 208 additions & 0 deletions src/content/docs/cci/getting-started/prerequisites.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,208 @@
---
title: Prerequisites for CCI
metaDescription: Set up AWS for CCI with consolidated billing, CUR, IAM roles, and region activation to optimize cost analysis in New Relic.
freshnessValidatedDate: never
---

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.

Check notice on line 7 in src/content/docs/cci/getting-started/prerequisites.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/prerequisites.mdx#L7

[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).
Raw output
{"message": "[Microsoft.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "src/content/docs/cci/getting-started/prerequisites.mdx", "range": {"start": {"line": 7, "column": 1}}}, "severity": "INFO"}

Before you integrate CCI with your AWS environment:

- Ensure [consolidated billing is set up for AWS Organizations](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html). This consolidates billing across all accounts in your organization for unified cost management.

Check notice on line 11 in src/content/docs/cci/getting-started/prerequisites.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/prerequisites.mdx#L11

[Microsoft.Passive] 'is set' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is set' looks like passive voice.", "location": {"path": "src/content/docs/cci/getting-started/prerequisites.mdx", "range": {"start": {"line": 11, "column": 32}}}, "severity": "INFO"}
- [Enable Cost and Usage Reports (CUR) in your AWS Management account](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-reports-costusage.html) (also referred to as the Payer account) with the following settings:

<table>
<thead>
<tr>
<th width={250}>
<DNT>
**Setting**
</DNT>
</th>

<th>
<DNT>
**Value**
</DNT>
</th>
<th>
<DNT>
**Description**
</DNT>
</th>
</tr>
</thead>

<tbody>
<tr>
<td>
S3 bucket name
</td>

<td>
`<your-company-name>-billing`
</td>

<td>
Specifies where the CUR data will be stored. The naming convention helps identify the bucket's purpose and ownership.
</td>
</tr>

<tr>
<td>
Export Type
</td>

<td>
Standard Data Export
</td>

<td>
Provides detailed information about usage and costs, suitable for most billing and cost analysis use cases.
</td>
</tr>

<tr>
<td>
Report Versioning
</td>

<td>
Create New Report Version
</td>

<td>
Each update to the CUR creates a new version. This retains historical reports, which are useful for auditing and tracking cost changes over time.
</td>
</tr>

<tr>
<td>
File Format
</td>

<td>
Parquet
</td>

<td>
A columnar storage file format that enhances query performance and reduces storage space, beneficial for processing large data volumes efficiently.
</td>
</tr>

<tr>
<td>
Include Resource IDs
</td>

<td>
ON
</td>

<td>
Enables detailed tracking of costs associated with individual AWS resources, aiding in fine-grained analysis and billing.
</td>
</tr>

<tr>
<td>
Data Refresh Settings
</td>

<td>
AUTOMATIC
</td>

<td>
Ensures that CUR data is kept up-to-date with the latest usage and cost information without manual intervention.
</td>
</tr>

<tr>
<td>
Split Cost Allocation Data
</td>

<td>
OFF
</td>

<td>
If not specifically needed, keeping this option off simplifies the data structure. It avoids separating data based on custom cost categories or splits. This might be left off unless detailed cost allocation splits are necessary for your analysis.
</td>
</tr>
</tbody>
</table>

- Configure [cost allocation tags](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html) in your AWS account. Tagging facilitates detailed and meaningful cost categorization.
- [Create a cross-account IAM policy granting read-only access to your CUR S3 bucket](https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/policies/details/arn%3Aaws%3Aiam%3A%3A017663287629%3Apolicy%2Fcco-finops-user-policy?section=permissions). Here’s a policy template for reference:
```json
{
"Version": "2012-10-17",
"Statement":
[
{
"Action":
[
"s3:Get*",
"s3:List*"
],
"Effect": "Allow",
"Resource":
[
"arn:aws:s3:::nr-finops-team/*",
"arn:aws:s3:::nr-finops-team"
],
"Sid": "AccessMasterPayerBillingBucket"
},
{
"Effect": "Allow",
"Action":
[
"pricing:DescribeServices",
"pricing:GetAttributeValues",
"pricing:GetProducts",
"pricing:GetPriceListFileUrl",
"pricing:ListPriceLists"
],
"Resource":
[
"*"
]
}
]
}
```
- [Create an IAM role and attach the above permission policy to it](https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/roles/details/cco-data-integrator-access?section=permissions).
- Add the New Relic global user (for example, `arn:aws:iam::707672555654:user/cco-s3-migration`) to the IAM role’s trust policy and provide role permissions. This is to allow the New Relic global user for CCI to assume the IAM role.

Check notice on line 177 in src/content/docs/cci/getting-started/prerequisites.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/prerequisites.mdx#L177

[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.", "location": {"path": "src/content/docs/cci/getting-started/prerequisites.mdx", "range": {"start": {"line": 177, "column": 133}}}, "severity": "INFO"}
```json
{
"Version": "2012-10-17",
"Statement":
[
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::707672555654:user/cco-s3-migration"
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"sts:ExternalId": "sgaxJF645eg5wOdTwh8M5EG6vLv5Ap5d"
}
}
}
]
}
```
<Callout variant="important">
If your resources are in AWS regions where Security Token Service (STS) is not active by default (for example, ap-east-1, eu-south-1), activate STS for those regions.

Check failure on line 199 in src/content/docs/cci/getting-started/prerequisites.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/prerequisites.mdx#L199

[Microsoft.Contractions] Use 'isn't' instead of 'is not'.
Raw output
{"message": "[Microsoft.Contractions] Use 'isn't' instead of 'is not'.", "location": {"path": "src/content/docs/cci/getting-started/prerequisites.mdx", "range": {"start": {"line": 199, "column": 77}}}, "severity": "ERROR"}
</Callout>


## 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.

Check notice on line 204 in src/content/docs/cci/getting-started/prerequisites.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/prerequisites.mdx#L204

[new-relic.Adverbs] Consider removing 'carefully'.
Raw output
{"message": "[new-relic.Adverbs] Consider removing 'carefully'.", "location": {"path": "src/content/docs/cci/getting-started/prerequisites.mdx", "range": {"start": {"line": 204, "column": 158}}}, "severity": "INFO"}

## What's next
- [Set up CCI](/docs/cci/getting-started/setup)
- [Troubleshoot setup issues]()
57 changes: 57 additions & 0 deletions src/content/docs/cci/getting-started/setup.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
title: Set up CCI
metaDescription: Set up Cloud Cost Intelligence with AWS. Configure IAM roles and data paths for detailed cost analysis and streamlined access in New Relic.
freshnessValidatedDate: never
---

Learn how to seamlessly set up Cloud Cost Intelligence (CCI) with AWS by configuring essential integration settings, including IAM roles and data export paths. This guide walks you through the required steps to enable detailed cost analysis and management within your New Relic platform, ensuring streamlined access to your AWS Cost and Usage Reports.

Follow these steps to configure CCI for integration with your AWS account:

<Steps>
<Step>
## Log in

Log in to New Relic.
</Step>

<Step>
## Start integrating

Click **Cloud Cost Intelligence** on the left panel, and then click **Add the integration**.
Alternatively, click **Integrations & Agents** on the left panel, look for Cloud Cost Intelligence amongst all capabilities, and then click **Cloud Cost Intelligence**.
</Step>

<Step>
## Meet prerequisites

Read the prerequisites. Ensure you meet them.
</Step>

<Step>
## Select account

Select the New Relic account that you want to use for the setup, and click **Continue**.

</Step>

<Step>
## Provide connection details

Check notice on line 39 in src/content/docs/cci/getting-started/setup.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/cci/getting-started/setup.mdx#L39

[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'Provide'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'Provide'.", "location": {"path": "src/content/docs/cci/getting-started/setup.mdx", "range": {"start": {"line": 39, "column": 8}}}, "severity": "INFO"}

Enter the following details required to fetch cost data from AWS:
- **Connection name:** Filled in by default. Edit if you want a custom name instead.
- **Data export name:** The name of the data export file. Used to construct the path to the corresponding CUR file. ​​For a report named cci-ingestion-test, the constructed path would be cost-and-usage-reports/cci-ingestion-test/data. This would be where CUR data is stored within the S3 bucket.
- **Cross-account IAM role ARN:** The Amazon Resource Name (ARN) for the IAM role that CCI will assume to access your S3 bucket. An ARN is a unique identifier for various AWS resources, including IAM roles. It follows a standard format that includes the service, region, account ID, and resource specifics—such as `arn:aws:iam::<account-id>:role/<role-name>`.

</Step>

<Step>
## Test connection

Finally, initiate a test to verify that the connection to your AWS environment is successful.

</Step>
</Steps>

## What's next
- [Troubleshoot setup issues]()
11 changes: 11 additions & 0 deletions src/nav/cci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
title: Cloud Cost Intelligence (CCI)
path: /docs/cci
pages:
- title: Getting started
pages:
- title: Overview of CCI
path: /docs/cci/getting-started/overview
- title: Prerequisites for CCI
path: /docs/cci/getting-started/prerequisites
- title: Set up CCI
path: /docs/cci/getting-started/setup
2 changes: 2 additions & 0 deletions src/nav/root.yml
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,8 @@ pages:
- title: Website performance monitoring
path: website-performance-monitoring
- title: Data insights
- title: Cloud Cost Intelligence
path: cci
- title: Alerts
path: alerts
- title: Change Tracking
Expand Down
Loading