Elasticsearch Reserved Instance Payment Pending

Risk level: High (not acceptable risk)

Rule ID: ES-019

Identify any pending Amazon Elasticsearch (ES) Reserved Instances available in your AWS account and solve these incomplete ES reservations by requesting AWS Support to retry the necessary payments, as outlined in the remediation/resolution section of the conformity rule. A pending AWS Elasticsearch Reserved Instance is an incomplete reservation that receives the "payment-pending" status during the purchasing process due to issues with the payment method used by the AWS customer.

This rule can help you work with the AWS Well-Architected Framework

This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS

Cost
optimisation

Using Reserved Instances to cut down on computing costs is one of the best cost optimization strategies when working with AWS Elasticsearch service. To fully receive the discount benefit, make sure that all your Elasticsearch reservation purchases have been fully processed (i.e. the purchase has been approved and the payment has been confirmed).

Audit

To identify any pending AWS Elasticsearch RI purchases available within your AWS account, perform the following:

Using AWS Console

01 Sign in to AWS Management Console.

02 Navigate to Elasticsearch (ES) dashboard at https://console.aws.amazon.com/es/.

03 In the left navigation panel, select Reserved Instances.

04 Choose the Reserved Instance (RI) that you want to examine and check the value listed within the Status column. If the reservation current status is set to payment-pending, the payment processing for the selected Amazon Elasticsearch Reserved Instance was not fully processed, therefore you need to retry your reservation pending payment by contacting AWS Support Center (see Remediation/Resolution section for more information).

05 Repeat step no. 4 to verify the purchase status for other AWS Elasticsearch Reserved Instances provisioned in the current region.

06 Change the AWS region from the navigation bar and repeat the process for other regions.

Using AWS CLI

01 Run describe-reserved-elasticsearch-instances command (OSX/Linux/UNIX) using custom query filters to list the IDs of all Elasticsearch Reserved Instances available in the selected AWS region:

aws es describe-reserved-elasticsearch-instances
	--region us-east-1
	--output table
	--query 'ReservedElasticsearchInstances[*].ReservedElasticsearchInstanceId'

02 The command output should return a table with the requested RI IDs:

----------------------------------------
|   ReservedElasticsearchInstanceIds   |
+--------------------------------------+
| aaaabbbb-1234-aaaa-bbbb-1234aaaabbbb |
| abcdabcd-1234-abcd-1234-abcdabcdabcd |
+--------------------------------------+

03 Run describe-reserved-elasticsearch-instances command (OSX/Linux/UNIX) using the ID of the Elasticsearch Reserved Instance (RI) that you want to examine as identifier and custom query filters to describe the purchase status for the selected RI:

aws es describe-reserved-elasticsearch-instances
	--region us-east-1
	--reserved-elasticsearch-instance-id aaaabbbb-1234-aaaa-bbbb-1234aaaabbbb
	--query 'ReservedElasticsearchInstances[*].State'

04 The command output should return the purchase payment status for the selected AWS ES reservation:

[
    "payment-pending"
]

If the status value returned by the describe-reserved-elasticsearch-instances command output is "payment-pending", as shown in the output example above, the purchase payment for the selected Amazon Elasticsearch Reserved Instance was not fully processed, therefore you need to retry your RI pending payment by contacting AWS Support Center using the console available at https://console.aws.amazon.com/support/.

05 Repeat step no. 3 and 4 to check the purchase status for other AWS Elasticsearch RIs available in the selected region.

06 Change the AWS region by updating the --region command parameter value and repeat steps no. 1 – 5 to perform the audit process for other regions.

Remediation / Resolution

Because Partial Upfront and All Upfront Reserved Instance types require an upfront payment, if the issuing bank of your payment method does not approve the upfront payment, your Elasticsearch reservation purchase is not fully processed and Amazon set its status automatically to "payment-pending", hence these purchase cannot be confirmed. To solve any incomplete Amazon Elasticsearch reservations, you need to retry the RI payments by contacting Amazon Web Services. To create the required support case using the AWS Support Center console, perform the following:

Note: Requesting Amazon to retry pending Elasticsearch Reserved Instance payments using AWS Billing and Cost Management console or AWS API via Command Line Interface (CLI) is not currently supported.

Using AWS Console

01 Sign in to AWS Management Console.

02 Navigate to AWS Support Center page at https://console.aws.amazon.com/support/.

03 On Support Center page, select My support cases tab to access your support cases.

04 On My support cases panel, click Create case to open the support case form.

05 On the Create Case page, perform the following actions:

Under Regarding, select Account and Billing Support option.
Choose Billing from the Service dropdown list to send your request to AWS Billing and Cost Management service.
Select Reserved Instances from the Category dropdown list.
Inside the Subject box, enter a subject for your request such as "Retry Amazon Elasticsearch Reserved Instance pending payment(s)".
In the Description textbox, enter a short description for your request so that AWS support team can evaluate your request.
Under Contact method, select a preferred contact method that AWS support team can use to respond to your request. If your need is urgent, choose Phone to request a direct phone call.
Click Submit to send the payment retry request for your Elasticsearch Reserved Instance(s) to Amazon Web Services. A customer support representative should contact you shortly.

References

AWS Command Line Interface (CLI) Documentation
es
describe-reserved-elasticsearch-instances

Publication date Oct 29, 2018

Unlock the Remediation Steps

Gain free unlimited access
to our full Knowledge Base

Over 750 rules & best practices
for and

You are auditing:

Elasticsearch Reserved Instance Payment Pending

Risk level: High

Audit

Using AWS Console

Using AWS CLI

Remediation / Resolution

Using AWS Console

References

Related Elasticsearch rules