Brad Poulton 2 лет назад
Родитель
Сommit
e3bf871a0e
1 измененных файлов с 8 добавлено и 2 удалено
  1. 8 2
      AWS Notes.md

+ 8 - 2
AWS Notes.md

@@ -263,15 +263,21 @@ To reserve an instance, you have to be confident that (a) you're going to need t
 1) Verify via the Monitoring Dashboard (https://moose-splunk.pvt.xdr.accenturefederalcyber.com/en-US/app/search/freds_monitoring_dashboard) that there are no concerns over utilization, especially with respect to CPU and Memory.
 2) Verify the same via the AWS Console.
 3) Carefully record the instance types that are going to be reserved.
-4) Verify that all the instance have the Platform listed as "Red Hat (Inferred)"
+4) Verify that all the instance have the Platform listed as "Red Hat (Inferred)" / "Red Hat Enterprise Linux"
 5) Go to reserved instances:
-  a) Change platform to "Red Hat Enterprise Linux"
+  a) Change platform to "Red Hat Enterprise Linux" (Watch out for GitHub/VMRay instance!)
+  - Tenancy = default
+  - Offering class = Standard (Convertable instances can only be changed within the same class)
   b) Change instance type to the desired type
   c) Change term to 1 year
   d) Change Payment Option to "No Upfront"
 6) Click "Search". You should see the standard and convertible options.
 7) Be sure to update the terraform and Document reservations via tags in the `terragrunt.hcl` of the module in the `xdr-terraform-live` repository.
 
+Assignment of reservations to instances get assigned at billing time. The AWS Console does not show us which reservations are assigned to which instances. To find that out, you will need to look at the bill.  
+
+For customers that renew, the cost savings is lost if they only pay for 9 months. Reserve for as close to 1 year as possible. 
+
 # Rotating Keys
 
 Keys should be rotated regularly (TODO: What does SSP say?).