AWS guidance documentation change
Summary
Minor grammatical corrections, phrasing improvements, and typo fixes throughout the FAQ document
Security assessment
Changes are purely editorial: fixing typos ('loose'→'lose'), grammar ('other then'→'other than'), and phrasing clarity. No security vulnerabilities, configurations, or features are mentioned or modified.
Diff
diff --git a/guidance/latest/cloud-intelligence-dashboards/faq.md b/guidance/latest/cloud-intelligence-dashboards/faq.md index 38787700a..f32ff81c4 100644 --- a//guidance/latest/cloud-intelligence-dashboards/faq.md +++ b//guidance/latest/cloud-intelligence-dashboards/faq.md @@ -21 +21 @@ Follow [Feedback & Support](./feedback-support.html) guide -Full list can be found [here](./dashboards.html). +The full list can be found [here](./dashboards.html). @@ -33 +33 @@ CUR documentation can be found [here](https://docs.aws.amazon.com/pdfs/cur/lates -On average, CURs are updated up to 3 times daily, but that will fluctuate depending on the size of the file/amount of user usage and many other factors. you can monitor your CUR S3 bucket to see the date/time the new month’s file is deposited. Within the CUR itself you can see the corresponding usage dates/times to infer which usage is reflected within that file. +On average, CURs are updated up to 3 times daily, but that will fluctuate depending on the size of the file/amount of user usage and many other factors. You can monitor your CUR S3 bucket to see the date/time the new month’s file is deposited. Within the CUR itself you can see the corresponding usage dates/times to infer which usage is reflected within that file. @@ -37 +37 @@ On average, CURs are updated up to 3 times daily, but that will fluctuate depend -For CUR2 we do not support exports other then deployed by cid Data Exports Stack. For Legacy CUR we do not recommend using an existing CUR unless it is for an installation within a Management (Payer) Account AND the existing Legacy CUR strictly conforms to the CID requirements: +For CUR2 we do not support exports other than those deployed by the CID Data Exports Stack. For Legacy CUR we do not recommend using an existing CUR unless it is for an installation within a Management (Payer) Account AND the existing Legacy CUR strictly conforms to the CID requirements: @@ -66 +66 @@ CID uses S3 replication for CUR aggregation. The data is not stored in the sourc -By default CUDOS has 7 months of data, If you need to pull more data, you can follow below steps as long as you have that additional data in CUR. +By default CUDOS has 7 months of data. If you need to pull more data, you can follow below steps as long as you have that additional data in CUR. @@ -87 +87 @@ Note: Some visuals are additionally limited by filters. Feel free to adjust them -### In which regions can the Cloud Intelligence Dashboards be deployed in? +### In which regions can the Cloud Intelligence Dashboards be deployed? @@ -89 +89 @@ Note: Some visuals are additionally limited by filters. Feel free to adjust them -CID requires Quick Sight, Athena and Glue. Cost Usage Reports (CUR) Bucket has to be in the same region as those services. CUR bucket can be replicated to the region that supports CIDs via S3 bucket replication. When using the cid-cmd, you can define the Region to deploy the dashboard in as a parameter e.g. _cid-cmd --region_name eu-west-2 deploy_. +CID requires Quick Sight, Athena and Glue. The Cost Usage Reports (CUR) bucket has to be in the same region as those services. CUR bucket can be replicated to the region that supports CIDs via S3 bucket replication. When using the cid-cmd, you can define the Region to deploy the dashboard in as a parameter e.g. _cid-cmd --region_name eu-west-2 deploy_. @@ -177 +177 @@ You can share dashboards and visuals with specific users or groups in your accou -### How is the Unit Cost is being calculated? +### How is the Unit Cost calculated? @@ -197 +197 @@ On KPI dashboard, under Set KPI Goals tab. Choose a specific KPI and adjust the -### How I can consolidate data from multiple AWS Organizations +### How can I consolidate data from multiple AWS Organizations @@ -203 +203 @@ You can add data collection from multiple AWS Organizations to be visualized in - 2. In each Management Account account (Payer) you need to install CID-CUR-Source as described in [step 2 here](./deployment-in-global-regions.html). + 2. In each Management Account (Payer) you need to install CID-CUR-Source as described in [step 2 here](./deployment-in-global-regions.html). @@ -212 +212 @@ You can expect the CUR to appear 24h after the backfill request completed. - 1. Follow Data Collection instructions to install permissions each Management Account account (Payer) as described in [here](./data-collection-deployment.html). + 1. Follow Data Collection instructions to install permissions in each Management Account (Payer) as described in [here](./data-collection-deployment.html). @@ -221 +221 @@ You can expect the CUR to appear 24h after the backfill request completed. -For Data Collection the backfill is not possible. You can check dashboards in after 24h or trigger refresh of all related datasets manually. +For Data Collection the backfill is not possible. You can check dashboards after 24h or trigger refresh of all related datasets manually. @@ -287 +287 @@ You can deploy CID in an account where Lake Formation activated. Under Technical -Some CID views dependent on having or historically having an RDS database instance and an ElastiCache instance run in your organization. +Some CID views are dependent on having or historically having an RDS database instance and an ElastiCache instance run in your organization. @@ -289 +289 @@ Some CID views dependent on having or historically having an RDS database instan -The CloudFormation deployment do not have this dependency. +The CloudFormation deployment does not have this dependency. @@ -364 +364 @@ Estimate the cost for your solution using [AWS Pricing Calculator](https://calcu -It depends on the the frequency of scans, number of regions and accounts and a volume of the workloads. Generally for customers with a monthly bill 1M$ the cost of data collection is less then $50/month for default scan frequency. +It depends on the frequency of scans, number of regions and accounts and a volume of the workloads. Generally for customers with a monthly bill 1M$ the cost of data collection is less than $50/month for default scan frequency. @@ -384 +384 @@ Translating the Dashboard into another language poses a significant challenge. W -### I am planning a migration of AWS Accounts to a different AWS Organization. What changes I need to make in CloudFormation stack in destination account? +### I am planning a migration of AWS Accounts to a different AWS Organization. What changes do I need to make in the CloudFormation stack in the destination account? @@ -390 +390 @@ Maintain current configuration until billing cycle completion to ensure accurate -It is important to request a backfill of your CUR before transferring AWS Accounts. Once an account leaves an AWS Organization you loose the ability to backfill CUR data. +It is important to request a backfill of your CUR before transferring AWS Accounts. Once an account leaves an AWS Organization you lose the ability to backfill CUR data. @@ -463 +463 @@ If you need to regularly export this data, you can deploy this as a Lambda to ru -### I have an archive of Cost and Usage Report (CUR). How I integrate to CID after migration? +### I have an archive of Cost and Usage Report (CUR). How do I integrate with CID after migration? @@ -480 +480 @@ It is recommended to setup CUR replication before migration. You can reuse histo -If you respect the above requirements, on an single tenant account or an organization (**FromOrg**), you are able to copy the CUR to another CID deployment, in another organization (**ToOrg**). +If you respect the above requirements, on a single tenant account or an organization (**FromOrg**), you are able to copy the CUR to another CID deployment, in another organization (**ToOrg**). @@ -482 +482 @@ If you respect the above requirements, on an single tenant account or an organiz -For the import process to work, the imported data should comply with a strict S3 mapping structure. S3 mapping is based on the CUR name and bucket prefix. In order to migrate existing reports, S3 mappings should be compliant. This will require to rename before transfer the data to the cid bucket of the destination organization. +For the import process to work, the imported data should comply with a strict S3 mapping structure. S3 mapping is based on the CUR name and bucket prefix. In order to migrate existing reports, S3 mappings should be compliant. This will require renaming the data before transfer to the cid bucket of the destination organization. @@ -599 +599 @@ This statement is to be added to an existing kms key policy and not to replace i -CUR bucket replication is the preferred method because it is tested and documented. Technically you can use cross-account methods but it is untested. It is true that CUR bucket replication will create more cost as the you will have to store the CUR twice, although you could think of it as a backup in case something happens to the payer accounts. We recommend CUR bucket replication also because the Athena tables are created/updated via a Glue crawler where you get all CUR schema changes handled. Glue crawlers don’t support cross account set up. It also gets significantly more complicated if KMS encryption is used. +CUR bucket replication is the preferred method because it is tested and documented. Technically you can use cross-account methods but it is untested. It is true that CUR bucket replication will create more cost as you will have to store the CUR twice, although you could think of it as a backup in case something happens to the payer accounts. We recommend CUR bucket replication also because the Athena tables are created/updated via a Glue crawler where you get all CUR schema changes handled. Glue crawlers don’t support cross account set up. It also gets significantly more complicated if KMS encryption is used. @@ -605 +605 @@ CUR bucket replication is the preferred method because it is tested and document -We recommend installation from scratch in case if you fully lost the access to your Quick Sight account. But you may want to backup data, collected by CID as well as your custom dashboards. +We recommend installation from scratch in case you fully lost access to your Quick Sight account. But you may want to backup data, collected by CID as well as your custom dashboards. @@ -656 +656 @@ There are two main reasons for this: - 1. As there are lambda function deployed in the account these could benefit from Compute Savings plans. This means that there could be higher savings missed in other accounts because they are used on the lambdas first: + 1. As there are Lambda functions deployed in the account these could benefit from Compute Savings plans. This means that there could be higher savings missed in other accounts because they are used on the lambdas first: @@ -663 +663 @@ There are two main reasons for this: -### My Athena database has tables in called year and payer +### My Athena database has tables called year and payer @@ -690 +690 @@ To fix please follow the steps below: -### What’s new in CUDOS v5 compare to previous version? +### What’s new in CUDOS v5 compared to the previous version? @@ -752 +752 @@ If you would like to delete previous version of CUDOS you can run `cid-cmd delet - 4. **Reduced amount of Athena data scans** : Having all CUDOS v5 datasets in SPICE reduces amount of data scanned by Athena compare to previous version. + 4. **Reduced amount of Athena data scans** : Having all CUDOS v5 datasets in SPICE reduces the amount of data scanned by Athena compared to the previous version.