For customers who have recently purchased RIs that go beyond the EOSM date of the concerned generation, it is recommended to upgrade to the v5 generation between the date of EOS and the date of EOSM. This upgrade does not incur any extra cost, limited to the period of the initial order (after the date of EOSM, only the new reservation will be taken into account). An action is required for this upgrade: executing a stop/start in order to integrate the parameters of the new generation (going from v2, v3, or v4 to v5).
Articles in this section
- 1. [EOS/EOSM of processor gens] What is the impact on my existing resources?
- 2. [EOS/EOSM of processor gens] What about any new Reserved Instances (RIs)?
- 3. [EOS/EOSM of processor gens] The key dates of EOS and EOSM
- 4. [EOS/EOSM of processor gens] What are the processor generations?
- 5. [EOS/EOSM of processor gens] Are the AWS types such as t2.small concerned?
- 6. [EOS/EOSM of processor gens] Why are the End-of-Life (EOL) dates not specified yet?
- 7. [EOS/EOSM of processor gens] If I haven't upgraded to a higher generation at the date of EOSM, will my virtual machine be stopped suddenly?
- 8. [EOS/EOSM of processor gens] Will I continue to be billed after the date of EOS?
- 9. [EOS/EOSM of processor gens] I consume tinav2.c2r4p2 instances. Until when will it be possible to order Reserved Instances?
- 10. [EOS/EOSM of processor gens] I ordered 3 Reserved Instances of type tinav2.c2r4p2 from January 1, 2022 to December 31, 2023 (2-year commitment). Am I impacted and what will happen?
Comments
0 comments
Please sign in to leave a comment.