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.

Sign up for GitHub

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

Update README.md #4231

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #4231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions src/docs/ocean/tips-and-best-practices/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@ The Ocean internal architecture utilizes the Elastigroup engine, a core componen
</details><br>

<details>
<summary markdown="span">Utilize Reserved Instances (For AWS users)</summary>
<summary markdown="span">Utilize Commitments (For AWS users)</summary>

## Utilize Reserved Instances (For AWS users)
## Utilize Commitments (For AWS users)

If you have [reserved instances](elastigroup/features/core-features/spot-reserved-on-demand-instances) (RIs) and they are available, Ocean will utilize them by default before purchasing spot instances, (i.e., the API attribute `utilizeReservedInstances` is set to True by default upon Ocean creation). If you would like to change this, set this attribute to False using this [API](https://docs.spot.io/api/#operation/OceanAWSClusterCreate). In addition, if you would like to take advantage of [AWS Savings Plans](https://aws.amazon.com/savingsplans/pricing/), you can opt in using the API.
If you have [reserved instances](elastigroup/features/core-features/spot-reserved-on-demand-instances) (RIs) and they are available, Ocean will utilize them by default before purchasing spot instances, (i.e., the API attribute `utilizeReservedInstances` is set to True by default upon Ocean creation). If you would like to change this, set this attribute to False using this [API](https://docs.spot.io/api/#operation/OceanAWSClusterCreate). In addition, if you would like to take advantage of [AWS Savings Plans](https://aws.amazon.com/savingsplans/pricing/), you can opt in using the API attribute `utilizeCommitments` which is set to False by default.

If you are using RI sharing across multiple AWS accounts, you can take advantage of the Cross RI Utilization feature to further optimize your RI usage. This feature will consider RI contracts and consumption across all relevant accounts. This is useful when a single account cannot consume the full RI capacity. Additional accounts can then use the excess capacity up to the maximum capacity of the RI. To activate this feature, do the following:
If you are using RI/SP sharing across multiple AWS accounts, you can take advantage of the Cross RI/SP Utilization feature to further optimize your RI/SP usage. This feature will consider RI/SP contracts and consumption across all relevant accounts. This is useful when a single account cannot consume the full RI capacity. Additional accounts can then use the excess capacity up to the maximum capacity of the RI. To activate this feature, do the following:

1. [Connect](https://docs.spot.io/connect-your-cloud-provider/aws-account) all the accounts with RI contracts to the Spot platform. (This can also be done using a read-only policy.)
1. [Connect](https://docs.spot.io/connect-your-cloud-provider/aws-account) all the accounts with RI/SP contracts to the Spot platform. It is important to connect every member account to the Spot Console so we have visibility into how and which RIs and SPs are being utilized (This can also be done using a read-only policy).
2. Reach out to Spot Support and request enablement of Cross RI Utilization for your Spot organization.

</details><br>
Expand Down
Loading