Questions tagged with Reserved Instances

Hello, I have a on-demand c6g.xlarge EC2 instance running. Now I have decided to purchase a Standard RI or an EC2 Instance Savings Plan. But before buying that, I would like few things. 1) Which of them allows to change OS in future. 2) Does either of them allows to change instance from c6g to c7g or from c6g to c6a? 3) If I buy a c6g.xlarge standard RI for one year today, and want to resize it to 2xlarge after say 6 months, (as per aws docs, I can do this by buying another c6g.xlarge, say I buy it for 3 years) what will be the validity of the newly generated c6g.2xlarge RI, 6 months or another three years from the day of latter purchase? 4) What will happen in case of EC2 saving plan for the same scenario as Que. 3? Thankslg...

I purchased a convertible RI r6a.32xlarge. What do I need to purchase or do to upgrade it to r6a.48xlarge? According to the documentation, I need to pay a normalization factor of 128 to equal the NF for the r6a.48xlarge (384). Do I just purchase the r6a.48xlarge instance and upgrade like that? Or r6a.16xlarge and then merge it with my instance? Documentation is uclear.lg...

When reserved instances are purchased from EC2 > Reserved Instances, then I would guess that gamelift fleets can not use these instances? Is there a way to reserve instances to be used for gamelift fleets? My gamelift fleet has predictable usage and I would like to reserve instances for next 12 months and save costs. Thanks!lg...

Hello there, I bought a reserved instance on February 9, 2023, 07:09 (UTC+6:30) and I can see expiry date as February 9, 2024, however the status is still Payment pending. and it is not active. Can someone please suggest or help? My Reserved Instance ID is 5414220a-dbf3-4242-8508-4b518da7f4d8 Thank You, Yan Painglg...

Hi, We incur 80% monthly cost for EC2 and RDS services used in our account. We have procured multiple Savings and RI plan on our account too for optimizing the spend. We have configured resource tags (eg: Environment: Prod, Non-Prod; Country: Country1, Country2, etc) on all our EC2 and RDS instances & same are configured in Cost allocation tags. In the Cost explorer section, we can see the detailed breakup of cost using 'Services' as filter criteria, but when we try to use these Tags to track spending by each resource tag, it does not work and shows most of the amount as 'No-tag' category. Fyi: We have multiple NURI and No-Upfront Savings plan in our account. What steps can we follow to track the spending distributed across these custom tags?lg...

I get the following error when trying to purchase a reserved instance. Error: Your current quota does not allow you to purchase the required number of reserved instances (Status Code: 400; Error Code: ReservedInstancesLimitExceeded; Request ID: 32762496-dfdf-447a-aff2-87cea127a11e) This isn't a very helpful error report because I only have one other instance, and my reserved instance limit is at 20, and I currently have no reserved instances. So what do I do to fix this?lg...

I have a Reserved instances rds m3.medium that is reserverd along 08 of March 2023, but AWS retired this instances. I would like to cancel this RI. By e-mail Announcement of AWS quote: *"*How will my reserved instance(s) impacted?* If you have Reserved Instances on M1, M2, M3, R3, or T1, you will be able to cancel them after you create new Reserved Instances for the same value or higher with M5, R5, or T3 respectively."* Do I would like to know how to cancel this RI?lg...

What if I have 1 RDS instance A that runs 24 hours a day and I also have 2 instances (B and C) that run concurrently between 7AM and 7PM (they are stopped at night). If I purchase 2 Reserved Instances would that be enough to cover the full usage of my 3 instances A, B and C? I know that if B and C ran consecutively it would be, but what hapens when they run concurently? Their usage adds up to 24 hour per day, but is that how the RI can be applied? I am assuming all the instances are in the same region and are the same instance type and size.lg...

Hi, We have a long-running RDS DB, and we would like to pay upfront for it, we want to know what is the best instance type to use. Is there a tool like AWS compute optimizer for RDS? If not, how do you determine what is the best-fit instance type?lg...

Hi, as per the announcement that these instance types are being deprecated, it is not clear what happens to remaining days already purchased for reserved instances of this older types. I have a db.r3.large instance, and a fully paid for Reserved Instance for that which has 462 days still remaining on it. The announcement email I received simply says "If you have Reserved Instances on M1, M2, M3, R3, or T1, you will be able to cancel them after you create new Reserved Instances for the same value or higher with M5, R5, or T3 respectively." However, what does that mean with respect to the loss of all of those already pre-paid for days on the existing Reserved Instance? Does canceling the Reserved Instance issue me a refund or credit towards the new Reserved Instance?lg...

Firing up new RHEL 9 EC2 ARM64 instance, and immediately trying to do a yum update and it can't. It appears the BaseOS is out of sync (older) with the updated Appstream repo. None of my 12 Reserved Instances, running RHEL9, can yum update either. If I disable BaseOS, it doesn't complain. I can't contact RHEL, since RedHAT says AWS handles RedHAT support. I've tried US-EAST-1, US-EAST-2, and US-WEST-2. The Appstream Repo, which provides all of the -devel rpms, has newer, updated rpms, which is complaining about older rpms in the BaseOS. As you can see it wants differing packages for -devel and base versions, which can't happen. Please fix. Thanks! Red Hat Enterprise Linux 9 for aarch64 - AppStream from RHUI (RPMs) 27 MB/s | 13 MB 00:00 Red Hat Enterprise Linux 9 for aarch64 - BaseOS from RHUI (RPMs) 40 MB/s | 6.0 MB 00:00 Red Hat Enterprise Linux 9 Client Configuration 18 kB/s | 1.8 kB 00:00 Error: Problem 1: package authselect-compat-1.2.5-1.el9.aarch64 requires authselect(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed - cannot install both authselect-1.2.5-2.el9_1.aarch64 and authselect-1.2.5-1.el9.aarch64 - cannot install the best update candidate for package authselect-compat-1.2.5-1.el9.aarch64 - cannot install the best update candidate for package authselect-1.2.5-1.el9.aarch64 Problem 2: package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed - cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-40.el9.aarch64 - cannot install the best update candidate for package glibc-devel-2.34-40.el9.aarch64 - cannot install the best update candidate for package glibc-2.34-40.el9.aarch64 Problem 3: package zlib-devel-1.2.11-34.el9.aarch64 requires zlib(aarch-64) = 1.2.11-34.el9, but none of the providers can be installed - cannot install both zlib-1.2.11-35.el9_1.aarch64 and zlib-1.2.11-34.el9.aarch64 - cannot install the best update candidate for package zlib-devel-1.2.11-34.el9.aarch64 - cannot install the best update candidate for package zlib-1.2.11-34.el9.aarch64 Problem 4: package libxcrypt-devel-4.4.18-3.el9.aarch64 requires glibc-devel(aarch-64) >= 2.27, but none of the providers can be installed - package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed - package glibc-devel-2.34-28.el9_0.aarch64 requires glibc = 2.34-28.el9_0, but none of the providers can be installed - package glibc-devel-2.34-28.el9_0.2.aarch64 requires glibc = 2.34-28.el9_0.2, but none of the providers can be installed - package glibc-2.34-40.el9.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-40.el9 if redhat-rpm-config), but none of the providers can be installed - package glibc-2.34-28.el9_0.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-28.el9_0 if redhat-rpm-config), but none of the providers can be installed - package glibc-2.34-28.el9_0.2.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-28.el9_0.2 if redhat-rpm-config), but none of the providers can be installed - cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-40.el9.aarch64 - cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-28.el9_0.aarch64 - cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-28.el9_0.2.aarch64 - cannot install the best update candidate for package redhat-rpm-config-196-1.el9.noarch - cannot install the best update candidate for package libxcrypt-devel-4.4.18-3.el9.aarch64 - cannot install the best update candidate for package glibc-gconv-extra-2.34-40.el9.aarch64 Problem 5: problem with installed package authselect-compat-1.2.5-1.el9.aarch64 - package authselect-compat-1.2.5-1.el9.aarch64 requires authselect(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed - package authselect-1.2.5-1.el9.aarch64 requires authselect-libs(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed - cannot install both authselect-libs-1.2.5-2.el9_1.aarch64 and authselect-libs-1.2.5-1.el9.aarch64 - cannot install the best update candidate for package authselect-libs-1.2.5-1.el9.aarch64 Problem 6: package gcc-11.3.1-2.1.el9.aarch64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed - package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed - package glibc-devel-2.34-28.el9_0.aarch64 requires glibc = 2.34-28.el9_0, but none of the providers can be installed - package glibc-devel-2.34-28.el9_0.2.aarch64 requires glibc = 2.34-28.el9_0.2, but none of the providers can be installed - package glibc-2.34-40.el9.aarch64 requires glibc-common = 2.34-40.el9, but none of the providers can be installed - package glibc-2.34-28.el9_0.aarch64 requires glibc-common = 2.34-28.el9_0, but none of the providers can be installed - package glibc-2.34-28.el9_0.2.aarch64 requires glibc-common = 2.34-28.el9_0.2, but none of the providers can be installed - cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-40.el9.aarch64 - cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-28.el9_0.aarch64 - cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-28.el9_0.2.aarch64 - cannot install the best update candidate for package glibc-common-2.34-40.el9.aarch64 - cannot install the best update candidate for package gcc-11.3.1-2.1.el9.aarch64 Problem 7: problem with installed package glibc-devel-2.34-40.el9.aarch64 - package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed - cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-40.el9.aarch64 - package glibc-langpack-en-2.34-40.el9_1.1.aarch64 requires glibc = 2.34-40.el9_1.1, but none of the providers can be installed - cannot install the best update candidate for package glibc-langpack-en-2.34-40.el9.aarch64 You can even take the AMI Image directly from RHEL, https://access.redhat.com/solutions/15356 and try and do a yum update, on install and get: [root@ip-172-30-3-97 ~]# yum update Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Red Hat Enterprise Linux 9 for aarch64 - AppStream from RHUI (RPMs) 65 MB/s | 13 MB 00:00 Red Hat Enterprise Linux 9 for aarch64 - BaseOS from RHUI (RPMs) 35 MB/s | 6.0 MB 00:00 Red Hat Enterprise Linux 9 Client Configuration 19 kB/s | 1.8 kB 00:00 Error: Problem 1: package authselect-compat-1.2.5-1.el9.aarch64 requires authselect(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed cannot install both authselect-1.2.5-2.el9_1.aarch64 and authselect-1.2.5-1.el9.aarch64 cannot install the best update candidate for package authselect-compat-1.2.3-7.el9.aarch64 cannot install the best update candidate for package authselect-1.2.3-7.el9.aarch64 Problem 2: problem with installed package authselect-compat-1.2.3-7.el9.aarch64 package authselect-compat-1.2.3-7.el9.aarch64 requires authselect(aarch-64) = 1.2.3-7.el9, but none of the providers can be installed package authselect-compat-1.2.5-1.el9.aarch64 requires authselect(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed package authselect-1.2.3-7.el9.aarch64 requires authselect-libs(aarch-64) = 1.2.3-7.el9, but none of the providers can be installed package authselect-1.2.5-1.el9.aarch64 requires authselect-libs(aarch-64) = 1.2.5-1.el9, but none of the providers can be installed cannot install both authselect-libs-1.2.5-2.el9_1.aarch64 and authselect-libs-1.2.3-7.el9.aarch64 cannot install both authselect-libs-1.2.5-2.el9_1.aarch64 and authselect-libs-1.2.5-1.el9.aarch64 cannot install the best update candidate for package authselect-libs-1.2.3-7.el9.aarch64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) If you add --allowerasing, and let it remove authselect-compat on this initial update, then do a: yum group install "development tools", and let it install all the -devel rpms, now you're in for a world of hurt. Any yum updates after that, and with repos out of sync, yum can't update: [root@ip-172-30-3-97 ~]# yum update Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Last metadata expiration check: 0:03:07 ago on Thu 26 Jan 2023 09:17:10 PM UTC. Error: Problem 1: package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-40.el9.aarch64 cannot install the best update candidate for package glibc-devel-2.34-40.el9.aarch64 cannot install the best update candidate for package glibc-2.34-40.el9.aarch64 Problem 2: package zlib-devel-1.2.11-34.el9.aarch64 requires zlib(aarch-64) = 1.2.11-34.el9, but none of the providers can be installed cannot install both zlib-1.2.11-35.el9_1.aarch64 and zlib-1.2.11-34.el9.aarch64 cannot install the best update candidate for package zlib-devel-1.2.11-34.el9.aarch64 cannot install the best update candidate for package zlib-1.2.11-34.el9.aarch64 Problem 3: package libxcrypt-devel-4.4.18-3.el9.aarch64 requires glibc-devel(aarch-64) >= 2.27, but none of the providers can be installed package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.aarch64 requires glibc = 2.34-28.el9_0, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.2.aarch64 requires glibc = 2.34-28.el9_0.2, but none of the providers can be installed package glibc-2.34-40.el9.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-40.el9 if redhat-rpm-config), but none of the providers can be installed package glibc-2.34-28.el9_0.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-28.el9_0 if redhat-rpm-config), but none of the providers can be installed package glibc-2.34-28.el9_0.2.aarch64 requires (glibc-gconv-extra(aarch-64) = 2.34-28.el9_0.2 if redhat-rpm-config), but none of the providers can be installed cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-40.el9.aarch64 cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-28.el9_0.aarch64 cannot install both glibc-gconv-extra-2.34-40.el9_1.1.aarch64 and glibc-gconv-extra-2.34-28.el9_0.2.aarch64 cannot install the best update candidate for package redhat-rpm-config-196-1.el9.noarch cannot install the best update candidate for package libxcrypt-devel-4.4.18-3.el9.aarch64 cannot install the best update candidate for package glibc-gconv-extra-2.34-40.el9.aarch64 Problem 4: package gcc-11.3.1-2.1.el9.aarch64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.aarch64 requires glibc = 2.34-28.el9_0, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.2.aarch64 requires glibc = 2.34-28.el9_0.2, but none of the providers can be installed package glibc-2.34-40.el9.aarch64 requires glibc-common = 2.34-40.el9, but none of the providers can be installed package glibc-2.34-28.el9_0.aarch64 requires glibc-common = 2.34-28.el9_0, but none of the providers can be installed package glibc-2.34-28.el9_0.2.aarch64 requires glibc-common = 2.34-28.el9_0.2, but none of the providers can be installed cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-40.el9.aarch64 cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-28.el9_0.aarch64 cannot install both glibc-common-2.34-40.el9_1.1.aarch64 and glibc-common-2.34-28.el9_0.2.aarch64 cannot install the best update candidate for package glibc-common-2.34-40.el9.aarch64 cannot install the best update candidate for package gcc-11.3.1-2.1.el9.aarch64 Problem 5: problem with installed package glibc-devel-2.34-40.el9.aarch64 package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-40.el9.aarch64 package glibc-langpack-en-2.34-40.el9_1.1.aarch64 requires glibc = 2.34-40.el9_1.1, but none of the providers can be installed cannot install the best update candidate for package glibc-langpack-en-2.34-40.el9.aarch64 Problem 6: package annobin-10.73-3.el9.aarch64 requires (gcc >= 11 with gcc < 12), but none of the providers can be installed package gcc-11.3.1-2.1.el9.aarch64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed package glibc-devel-2.34-40.el9.aarch64 requires glibc = 2.34-40.el9, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.aarch64 requires glibc = 2.34-28.el9_0, but none of the providers can be installed package glibc-devel-2.34-28.el9_0.2.aarch64 requires glibc = 2.34-28.el9_0.2, but none of the providers can be installed cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-40.el9.aarch64 cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-28.el9_0.aarch64 cannot install both glibc-2.34-40.el9_1.1.aarch64 and glibc-2.34-28.el9_0.2.aarch64 package gcc-11.2.1-9.4.el9.aarch64 requires cpp = 11.2.1-9.4.el9, but none of the providers can be installed package glibc-minimal-langpack-2.34-40.el9_1.1.aarch64 requires glibc = 2.34-40.el9_1.1, but none of the providers can be installed cannot install both cpp-11.2.1-9.4.el9.aarch64 and cpp-11.3.1-2.1.el9.aarch64 cannot install the best update candidate for package glibc-minimal-langpack-2.34-40.el9.aarch64 cannot install the best update candidate for package cpp-11.3.1-2.1.el9.aarch64 cannot install the best update candidate for package annobin-10.73-3.el9.aarch64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest'lg...

Hi, my website (kenniescompass.com) is down. And we got the following email from lightsail... We have detected a degradation of the underlying hardware hosting your instance: kenniescompass.com (us-east-1) in your AWS Account with ID: 722687524582. Due to this degradation, we will have to perform necessary maintenance to the underlying hardware. Your instance may already be unreachable. Maintenance activity will result in your Lightsail instance stopping after Wed, 18 Jan 2023 20:00:00 GMT. After your instance is stopped, you can restart it at any time. what does this mean? How do i fix it immediately to get my website back up and running?lg...