With Amazon OpenSearch Service, you can search, analyze, visualize, and secure up to petabytes of text and unstructured data. Pay only for what you use; there is no minimum fee or usage requirement. You are charged based on three dimensions: instance hours, which are the number of hours that an instance is available to you for use; the amount of storage you need; and data transferred in and out of OpenSearch Service. Storage pricing depends on the storage tier and type of instance that you choose.

Free Tier

You can get started for free on OpenSearch Service with AWS Free Tier. For customers in the AWS Free Tier, OpenSearch Service provides free usage of up to 750 hours per month of a t2.small.search or t3.small.search instance, which are entry-level instances typically used for test workloads, and 10 GB per month of optional Amazon Elastic Block Store (EBS) storage. If you exceed the Free Tier usage limits, you will be charged the OpenSearch Service rates for the additional resources you use. See offer terms for more details.

On-Demand Instance pricing

Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS is subject to Japanese Consumption Tax. Learn more.

Reserved Instance pricing

With Amazon OpenSearch Service Reserved Instances, you can reserve instances for a one- or three-year term and realize significant savings on usage costs compared to On-Demand instances. Functionally, On-Demand and Reserved Instances are identical. From a billing perspective, however, Reserved Instances can provide significant cost savings.

Reserved Instances have three payment options:

  • No Upfront Reserved Instances (NURI) – NURIs offer significant savings compared to On-Demand Instance pricing. You pay nothing upfront, but you commit to pay for the Reserved Instances over the course of a one- or three-year term. One-year NURIs offer a 31% discount and three-year NURIs offer a 48% discount. For T3.medium, one-year NURIs offer a 18% discount and three-year NURIs offer a 28% discount.
  • Partial Upfront Reserved Instances (PURI) – PURIs offer higher savings than NURIs. This option requires you to pay a portion of the total cost upfront and pay the remainder of the cost on an hourly basis over the course of the term. One-year PURIs offer a 33% discount and three-year PURIs offer a 50% discount. For T3.medium, one-year PURIs offer a 20% discount and three-year NURIs offer a 30% discount.
  • All Upfront Reserved Instances (AURI) – AURIs offer the highest savings of all of the Reserved Instance payment options. You pay for the entire reservation with one upfront payment and pay nothing on an hourly basis. One-year AURIs offer a 35% discount and three-year AURIs offer a 52% discount. For T3.medium, one-year AURIs offer a 22% discount and three-year NURIs offer a 32% discount.
  • Reserved Instance pricing is specific to each region and depends on the payment option and term that you select. When you purchase a Reserved Instance, you will be charged the associated upfront fees (if applicable) and hourly fees (if applicable), even if you are not currently running Amazon OpenSearch Service. To purchase Reserved Instances, visit the Reserved Instance tab in our Console.

 

* This is the average monthly payment over the course of the Reserved Instance term. For each month, the actual monthly payment will equal the actual number of hours in that month multiplied by the hourly usage rate or number of seconds in that month multiplied by the hourly usage rate divided by 3600, depending on the RDS for SQL Server instance type you run. The hourly usage rate is equivalent to the total average monthly payments over the term of the Reserved Instance divided by the total number of hours (based on a 365 day year) over the term of the Reserved Instance.

** Effective hourly pricing helps you calculate the amount of money a Reserved Instance will save you over On-Demand pricing. When you purchase a Reserved Instance, you are billed for every hour during the entire Reserved Instance term you select, regardless of whether the instance is running. The effective hourly price shows the amortized hourly instance cost. This takes the total cost of the Reserved Instance over the entire term, including any upfront payment, and spreads it out over each hour of the Reserved Instance term.

Amazon OpenSearch Serverless

With Amazon OpenSearch Serverless, you only pay for the resources consumed by the workload. OpenSearch Serverless charges for compute and storage separately. The compute capacity is measured in OpenSearch Compute Units (OCUs). The number of OCUs corresponds directly to the CPU, memory, Amazon EBS storage, and I/O resources required to index data or run queries. One OCU comprises 6 GB of RAM, corresponding vCPU, GP3 storage (used to provide fast access to the most frequently accessed data), and data transfer to Amazon Simple Storage Service (S3).

You will see one entry for compute in OCU-hours with two labels: one for data indexing and the other for search. OCUs are billed on an hourly basis on a collection with per-second granularity. Data stored on Amazon S3 will be billed by gigabyte-months. You will be billed at least for a minimum of 2 OCUs (1 OCU [0.5 x 2] indexing includes primary and standby, and 1 OCU [0.5 x 2] search includes one replica for HA) for the first collection in an account. However, the minimum varies based on your data size and collections type in use.

Additionally, OpenSearch Serverless also offers a dev-test option, where you can launch a collection without redundant standby nodes. This deployment mode further cuts the cost in half, with 0.5 OCU for indexing and 0.5 OCU for search. All the data is stored in Amazon S3 in both modes offering the complete data durability. However, the minimum varies based on your data size and collections type in use.

All subsequent collections using the same encryption key can share those OCUs. Additional OCUs will be added based on compute instances and data needed to support your collections. You can configure a maximum number of OCUs per account to control costs.

A vector search collection cannot share OCUs with search and time series collections, even if the vector search collection uses the same KMS key as the search or time series collections. A new set of OCUs will be created for your first vector search collection. The OCUs of vector search collections are shared among the same KMS key vector collections.

Amazon OpenSearch Ingestion

With Amazon OpenSearch Ingestion, you only pay for the resources consumed by your workload. OpenSearch Ingestion charges for only the compute needed to ingest, transform, and route data in an OpenSearch Ingestion pipeline. The compute capacity is measured in OpenSearch Compute Units (OCUs). The number of OCUs corresponds directly to the CPU and memory required to ingest data or perform transformation on the data. One OCU comprises 8 GB of RAM and 2vCPU. You will see one entry for compute in OCU-hours with the label for data ingestion. OCUs are billed on an hourly basis with per-minute granularity. You can configure a minimum and maximum number of OCUs per pipeline to control cost. Furthermore, OpenSearch Ingestion allows you to completely pause a pipeline when not in use and no OCUs are consumed when a pipeline is paused.

Amazon OpenSearch Service Direct Query

With Amazon OpenSearch Service Direct Query, you only pay for the resources consumed by your workload. OpenSearch Service Direct Query charges for only the compute needed to query your external data as well as maintain optional indexes in OpenSearch Service. The compute capacity is measured in OpenSearch Compute Units (OCUs). The number of OCUs corresponds directly to the vCPU and memory required to query or maintain indexes based on the data. One OCU comprises 2vCPU and 8 GiB of RAM. You will see one entry for compute in OCU-hours with the label for direct query. OCUs are billed on an hourly basis with per-minute granularity. To limit costs, you can set a maximum number of OCU-hours that can be used within a billing period. If no queries or indexing activities are active, no OCUs are consumed.

Additional costs

You are billed separately for the AWS services you use with OpenSearch Service, such as Amazon S3 and AWS Glue Data Catalog

  • You are billed by Amazon S3 when your workloads read, store, and transfer data. See Amazon S3 pricing for more information.
  • Glue Data Catalog is used by OpenSearch Service to manage tables you are charged standard Glue Data Catalog rates. For details, visit the AWS Glue pricing page.

Amazon EBS volume pricing (applies if you choose EBS volumes)

Amazon OpenSearch Service allows you to choose the type of Amazon EBS volume. If you choose Provisioned IOPS (SSD) storage, you will be charged for the storage as well as the throughput you provision. However, you will not be charged for the I/Os you consume.

UltraWarm and cold storage pricing

UltraWarm is an Amazon OpenSearch Service tier allowing you to economically retain large amounts of data while keeping the same interactive analysis experience. Learn more »

Cold storage is the lowest-cost storage tier for Amazon OpenSearch Service, which lets you detach and store infrequently accessed data in Amazon S3 and pay for compute only when you need it. Learn more »

Note: Managed storage pricing is applicable to UltraWarm data, cold storage data and OR1 remote store data.

Standard AWS data transfer charges

You need to pay standard AWS data transfer charges for the data transferred in and out of Amazon OpenSearch Service. You will not be charged for the data transfer between nodes within your Amazon OpenSearch Service domain.

Free automated snapshot storage

Amazon OpenSearch Service offers added data durability through automated and manual cluster snapshots. The service provides storage space for automated snapshots free of charge for each Amazon OpenSearch Service domain, and retains these snapshots for a period of 14 days. Manual snapshots are stored in Amazon S3 and incur standard Amazon S3 usage charges. Data transfer for using the snapshots is free of charge.

Pricing examples

Pricing example 1

Let’s say you are new to Amazon OpenSearch Service and are creating a domain in the US-East (N. Virginia) region. You are testing the service with three t3.small.search instances and 15 GB storage in each instance. You are using Amazon EBS General Purpose SSD (gp2) volumes as your preferred storage option. Amazon OpenSearch Service provides free usage of up to 750 hours per month of a t2.small.search or t3.small.search instance, with 10 GB of EBS storage. Considering a month’s usage, the three instances on your domain would run for 730 hours each, totaling 2,190 hours of usage. Minus 750 hours of free usage, you will be charged for 1,440 instance hours, which amounts to $51.84 for the month (see calculations in the table below). Similarly, for EBS, your three instances put together will have 45 GB of EBS storage. Minus 10 GB of free storage, you will be charged for 35 GB, which amounts to $4.725 for the month. Your total cost for the month is $56.67.

Please see below for a breakdown of the monthly costs (USD) you are likely to incur when free tier is still applicable. 

Cost Type Pricing  Usage Free Tier Billed Usage Cost  per month
Instance Usage t3.small.search = $0.036 per hour 3 instances * 730 hours in a month = 2,190 hours 750 hours 2,190 hours – 750 hours =. 1,440 hours 1,440 * $0.036 = $51.84
Storage Cost EBS General Purpose SSD (gp2)  = $0.135 per GB per month 15 GB * 3 instances = 45 GB per month 10 GB 45 GB – 10 GB = 35 GB 35 * $0.135 = $4.725
Total Cost $56.57

Pricing example 2

Let’s say you are creating a new production-grade domain with three Availability Zones in the US East (N. Virginia) region with the following configuration: three data nodes of type r6g.xlarge.search with 500 GB EBS storage (General Purpose SSD) each, three cluster manager nodes of type c6g.large.search, and two UltraWarm nodes of type ultrawarm1.medium.search with 1.5 TB storage each. In one month, the eight instances on your domain (three data nodes, three cluster manager nodes, and two UltraWarm nodes) will run for 730 hours each, totaling 5,840 instance hours. Based on the price of these individual instance types, your total cost for instance hours is $1,328.60. Your total storage cost for the month includes the cost of EBS storage for the three data nodes and the cost of storage for the UltraWarm nodes. With 500 GB EBS storage on each of the three instances, you will be charged for 1,500 GB at $0.135 per GB per month, which amounts to an EBS storage cost of $202.50 for the month. For storage for the two UltraWarm nodes, you will be charged for 3 TB (1.5 TB per instance), which amounts to $73.728 (at $0.024 per GB per month). 

Please see below for a breakdown of the monthly costs (USD) you are likely to incur.

Cost Type Pricing  Usage Cost  per month
Instance Usage r6g.xlarge.search = $0.335 per hour 3 instances (data nodes) * 730 hours in a month = 2,190 hours 2,190 hours * $0.335 = $733.65
c6g.large.search = $0.113 per hour 3 instances (cluster manager nodes) * 730 hours in a month = 2,190 hours 2,190 hours * $0.113 = $247.47
ultrawarm1.medium.search = $0.238 per hour 2 instances * 730 hours= 1,460 hours 1,460 hours * $0.238 = $347.48
Storage Cost EBS General Purpose SSD (gp2) = $0.135 per GB per month 500 GB per node * 3 instances (data nodes) = 1,500 GB per month 1,500 GB * $0.135 = $202.5
UltraWarm Managed Storage Cost = $0.024 per GB per month 1.5 TB * 2 instances = 3 TB per month 3072 GB * $0.024 = $73.728
Total Cost $1,604.83

OpenSearch includes certain Apache-licensed Elasticsearch code from Elasticsearch B.V. and other source code. Elasticsearch B.V. is not the source of that other source code. ELASTICSEARCH is a registered trademark of Elasticsearch B.V.

Pricing example 3

Amazon OpenSearch Service does not charge for Multi-AZ with Standby.

Scenario 1: Customer has a well configured domain with 3 cluster manager nodes, 6 data nodes and 3 copies of data. They will not see any impact of moving their domain to Multi-AZ with Standby. The before and after cost is the same.

Item Configuration Count Rate Total
Cluster Manager Nodes m5.large.search 3

$0.14

$306.72
Data Nodes m5.large.search 6

$0.14

$613.44
EBS Storage GP2 512 GB

$0.14

$414.72

Total
    1,334.880

Scenario 2: Customer has a domain that is undersized (more than 60% CPU or RAM utilisation) cluster manager. The customer will need to update their cluster manager node instance type before enabling Multi-AZ with Standby. In this case, for 10-20 data nodes, they need to use an instance type of c5.xlarge.search or above. Due to the change in cluster manager node size the customer will see some increase in cost as Multi-AZ with Standby enforces these best practices.

Table 2A Pre-Multi-AZ with Standby cluster with undersized cluster manager
Item Configuration Count Rate Total
Cluster Manager Nodes

m5.large.search

3

$0.14

$306.72
Data Nodes r5.large.search 18

$0.37

$4,821.12

EBS Storage GP2 1500 GB

$0.14

$3,645

Total
    $ 8,772.840
Table 2B Post-Multi-AZ with Standby cluster with correct cluster manager selection
Item Configuration Count Rate Total
Cluster Manager Nodes

c5.xlarge.search

3

$0.25

$542.16
Data Nodes r5.xlarge.search 18

$0.37

$4,821.12

EBS Storage GP2 1500 GB

$0.14

$3,645

Total
    $ 9,008.280

Scenario 3: Customer has a domain that follows old best practices and guidelines, thus has 2-copies of data (1 primary and 1 replica) and storage utilization is above 70%. Enabling Multi-AZ with Standby requires at least 3 or multiple of 3 copies of data. To accommodate the additional copy of data the customer would need an additional 40% of storage while still keeping 20% of free disk space. This means an additional 9 data nodes.

Table 3A Pre-Multi-AZ with Standby customer cluster had less than 20% free disk space and 2-copies of data
Item Configuration Count Rate Total
Cluster Manager Nodes

m5.large.search

3

$0.14

$306.72
Data Nodes r5.xlarge.search 18

$0.37

$4,821.12

EBS Storage GP2 1500 GB

$0.14

$3,645

Total
    $ 8,772.840
Table 3B Post-Multi-AZ with Standby customer would add 9 additional data nodes to accommodate the 3rd copy of data
Item Configuration Count Rate Total
Cluster Manager Nodes

c5.xlarge.search

3

$0.25

$542.16
Data Nodes r5.xlarge.search 27*

$0.37

7,231.68

EBS Storage GP2 1500 GB

$0.14

$5,467.50

Total
    $ 13,241.340

*In case the customer uses only 50-60% of the total storage, they would not need to add additional storage for the third copy and hence may not incur additional cost.

From the above examples, customers who follow best practices do not incur additional cost of enabling Multi-AZ with Standby on their domain.

Pricing Example 4

Let’s say you are creating a new production-grade domain with three Availability Zones in the US East (N. Virginia) region with the following configuration: three data nodes of type or1.xlarge.search with 500 GB EBS storage (General Purpose SSD) each, three cluster manager nodes of type c6g.large.search, and three Ultrawarm nodes of type ultrawarm1.medium.search with 1.5 TB storage each. In one month, the nine instances on your domain (three data nodes, three cluster manager nodes, and three Ultrawarm nodes) will run for 720 hours each, totaling 5780 instance hours. Based on the price of these individual instance types, your total cost for instance hours is $1661.04. Your total storage cost for the month includes the cost of EBS storage for the three data nodes, local storage and the cost of storage for managed storage which is $292.728. With 500 GB EBS storage on each of the three instances, you will be charged for 1,500 GB at $0.122 per GB per month, which amounts to an EBS storage cost of $183.0 for the month. As data is written synchronously to Amazon S3 In the remote store, you will be charged for 1,500 GB at $0.024 per GB per month, which amounts to $36.0 For storage for the three Ultrawarm nodes, you will be charged for 3 TB (1.5 TB per instance), which amounts to $73.728 (at $0.024 per GB per month). 

Please see below for a breakdown of the monthly costs (USD) you are likely to incur.

Cost Type Pricing Usage Cost per month

Instance Usage

 

or1.xlarge.search = $0.418 per hour 3 instances (data nodes) * 720 hours in a month = 2160 hours 2,160 hours * $0.418 = $902.88
c6g.large.search = $0.113 per hour 3 instances (cluster manager nodes) * 720 hours in a month = 2,190 hours 2,160 hours * $0.113 = $244.08
ultrawarm1.medium.search = $0.238 per hour

3 instances * 720 hours= 2160 hours

2160 hours * $0.238 = $514.08
Storage Cost EBS General Purpose SSD (gp2) = $0.135 per GB per month

500 GB per node * 3 instances (data nodes) = 1,500 GB per month

1,500 GB * $0.122 = $183.00
OR1 Managed Storage Cost = $0.024 per GB per month 500 GB per node * 3 instances (data nodes) = 1,500 GB per month 1,500 GB * $0.024 =$36.00
Ultrawarm Managed Storage Cost = $0.024 per GB per month 1.5 TB * 2 instances = 3 TB per month 3072 GB * $0.024 = $73.728
Total Cost $1,953.732

Pricing Example 5

OpenSearch Service Direct Query - Querying

Let’s say you have an Amazon OpenSearch Service domain already setup in the US-East (N. Virginia) region and you created a new Direct Query data source using Amazon S3 to query to your VPC flow logs. You refer to your run book to kick off a series of queries which in its entirety use 2 OCU-hours to complete. You would be billed 2 OCUs * 0.24 OCU-hours * 24 hours/day = $11.52 / day to maintain your index for faster query performance.

Pricing Example 6

OpenSearch Service Direct Query - Acceleration

Let’s say you have an Amazon OpenSearch Service domain already setup in the US-East (N. Virginia) region and you have created a new Direct Query data source using Amazon S3 to query to your S3 Logs. You want to tune query performance so that your queries complete faster. You enable a materialized view on your S3 Logs table in AWS Glue Data Catalog when setting up the data source which runs every hour and uses 2 OCU-hours each time it runs. You would be billed 2 * 0.24 OCU-hours * 24 hours/day = $11.52 / day to maintain your index for faster query performance.

FAQs

On-Demand Instance pricing

Q: How will I be charged and billed for my use of Amazon OpenSearch Service?

You pay only for what you use, and there are no minimum or setup fees. You are billed based on:

  • Amazon OpenSearch Service instance hours – Based on the class (e.g. Standard Small, Large, Extra Large) of the Amazon OpenSearch Service instance consumed. Partial Amazon OpenSearch Service instance hours consumed are billed as full hours.
  • Storage (per GB per month) – Amazon EBS Storage capacity you have provisioned to your Amazon OpenSearch Service instance. If you scale your provisioned storage capacity within the month, your bill will be pro-rated.
  • Provisioned IOPS per month – Amazon EBS Provisioned IOPS rate, regardless of IOPS consumed (for Amazon OpenSearch Service Provisioned IOPS (SSD) Storage only).
  • Data transfer – Regular AWS data transfer charges apply.

Please refer to the Amazon OpenSearch Service pricing page for detailed pricing information.

Q: When does billing of my Amazon OpenSearch Service domain begin and end?

Billing commences for an Amazon OpenSearch Service instance as soon as the instance is available. Billing continues until the Amazon OpenSearch Service instance terminates, which would occur upon deletion or in the event of instance failure.

Q: What defines billable instance hours for Amazon OpenSearch Service?

Amazon OpenSearch Service instance hours are billed for each hour your instance is running in an available state. If you no longer wish to be charged for your Amazon OpenSearch Service instance, you must delete the domain to avoid being billed for additional instance hours. Partial Amazon OpenSearch Service instance hours consumed are billed as full hours.

Reserved Instance pricing

Q: What is a Reserved Instance (RI)?

Amazon OpenSearch Service Reserved Instances give you the option to reserve an instance for a one- or three-year term, and in turn receive significant savings compared to the On-Demand Instance pricing.

Q: How are Reserved Instances different from On-Demand Instances?

Functionally, Reserved Instances and On-Demand Instances are exactly the same. The only difference is how your instance(s) are billed. With Reserved Instances, you purchase a one- or three-year reservation and receive a lower effective hourly usage rate (compared to On-Demand Instances) for the duration of the term. Unless you purchase Reserved Instances in a Region, all instances in that Region are billed at On-Demand Instance hourly rates.

Q: What are the payment options for Reserved Instances?

Three options are available:

  • No Upfront Reserved Instances (NURI) – NURIs offer significant savings compared to On-Demand Instance prices. You pay nothing upfront, but commit to paying for the Reserved Instance over the course of the one- or three-year term.
  • Partial Upfront Reserved Instances (PURI) – PURIs offer higher savings than NURIs. You pay for a portion of the total cost upfront, and the remainder over the course of the term. This option balances payments between upfront and hourly.
  • All Upfront Reserved Instances (AURI) – AURIs offer the highest savings of all of the Reserved Instance payment options. You pay for the entire reservation with one upfront payment, and pay nothing on an hourly basis.

Q: How do I purchase Reserved Instances?

You purchase Reserved Instances in the "Reserved Instance" section of the AWS Management Console for Amazon OpenSearch Service. Alternatively, you can use the Amazon OpenSearch Service API or AWS Command Line Interface to list and purchase Reserved Instances.

Once you purchase a Reserved Instance, you can use it just like an On-Demand Instance. As long as the purchased reservation is active, Amazon OpenSearch Service applies the reduced hourly rate to it.

Q: Are Reserved Instances specific to an Availability Zone?

Amazon OpenSearch Service Reserved Instances are purchased for a Region rather than for a specific Availability Zone. After you purchase a Reserved Instance for a Region, the discount applies to matching usage in any Availability Zone within that Region.

Q: How many Reserved Instances can I purchase?

You can procure up to 100 Reserved Instances in a single purchase. If you need more Reserved Instances, you need to place more purchase requests.

Q: Do Reserved Instances include a capacity reservation?

Amazon OpenSearch Service Reserved Instances are purchased for a Region rather than for a specific Availability Zone. Hence, they are not capacity reservations. Even if capacity is limited in one Availability Zone, Reserved Instances can still be purchased in the Region. The discount applies to matching usage in any Availability Zone within that Region.

Q: What if I have an existing On-Demand Instance that I’d like to convert to a Reserved Instance?

Simply purchase a Reserved Instance of the same type as the existing On-Demand Instance. If the Reserved Instance purchase succeeds, Amazon OpenSearch Service automatically applies the new hourly usage charge for the duration of your reservation.

Q: If I sign up for a Reserved Instance, when does the term begin? What happens to my Reserved Instance when the term ends?

Pricing changes and the reservation term associated with your Reserved Instance become active after your request is received and the payment authorization is processed. If the one-time payment (if applicable) or new hourly rate (if applicable) cannot be successfully authorized by the next billing period, the discounted price does not take effect and your term does not begin. You can follow the status of your reservation using the console, API, or CLI. For more details, refer our documentation.

When your Reserved Instance term expires, your Reserved Instance reverts to the appropriate On-Demand Instance hourly usage rate for your instance class and Region.

Q: How do I control which instances are billed at the Reserved Instance rate?

When computing your bill, our system automatically applies your reservation(s) such that all eligible instances are charged at the lower hourly Reserved Instance rate. Amazon OpenSearch Service does not distinguish between On-Demand and Reserved Instances while operating Amazon OpenSearch Service domains.

Q: If I scale my Reserved Instance up or down, what happens to my reservation?

Each Reserved Instance is associated with the instance type and Region that you picked for it. If you change the instance type in the Region where you have the Reserved Instance, you will not receive discounted pricing. You must ensure that your reservation matches the instance type you plan to use. For more details, please refer to Amazon OpenSearch Service Reserved Instance Documentation.

Q: Can I move a Reserved Instance from one Region or Availability Zone to another?

Each Reserved Instance is associated with a specific Region, which is fixed for the lifetime of the reservation and cannot be changed. Each Reserved Instance can, however, be used in any of the Availability Zones within the associated Region.

Q: Are Reserved Instances applicable if use multiple Availability Zones?

A Reserved Instance is for an AWS Region and can be used in any of the Availability Zones in that Region.

Q: Are Reserved Instances available for both cluster manager nodes and Data nodes?

Yes. Amazon OpenSearch Service does not differentiate between cluster manager and Data nodes when applying Reserved Instance discounts.

Q: Can I cancel a Reserved Instance?

No, you cannot cancel your Reserved Instances, and the one-time payment (if applicable) and discounted hourly usage rate (if applicable) are not refundable. Also, you cannot transfer the Reserved Instance to another account. You must pay for every hour during your Reserved Instance’s term, regardless of your usage.

Q: If I purchase a Reserved Instance from a payer (primary) account, is it accessible to all the member accounts?

Yes. Reserved Instance pricing and application follows the policies defined for consolidated billing on AWS. More details can be found here.

Q: If AWS reduces prices of On-Demand Instances for Amazon OpenSearch Service, will the amount I pay for my current Reserved Instances change?

No. The price you pay for already-purchased Reserved Instances does not change for the term of the reservation.

Q: Can I sell my Reserved Instances on the Reserved Instance Marketplace?

No. Reserved Instances purchased on Amazon OpenSearch Service cannot be sold on the Reserved Instance Marketplace.

Q: Are volume discounts available for Reserved Instance purchase?

No. We do not offer volume discounts for Amazon OpenSearch Service Reserved Instances.

Additional pricing resources

AWS Pricing Calculator

Easily calculate your monthly costs with AWS

Get pricing assistance

Contact AWS specialists to get a personalized quote

Learn how to get started with Amazon OpenSearch Service

Visit the getting started page