How can i scale up my azure reserved virtual machine? - azure-virtual-machine

How can i scale up my azure reserved VM ? I am in a situation where I bought reserved instance per year for B2ms machine but after eight months I want to increase it to B4ms. How will payment look like in that situation. When number of vm is the same, but we need to scale it up ?

You could open up a support ticket to the Subscription and Billing team and request that you change the scope of the reserved instance. From there you could opt to have a larger tier and you would then be required to pay the difference between what you have already paid and what the new tier at that price would cost for the remaining of the contract.
You can just refer to this official guide to raise a support ticket.

Related

How to setup Commitment use discounts on google?

I create a blog on GCP using ghost cms with a bitnami server. I recently found commitment discounts.
I know bitanmi provides a commitment discount on that. But my website is 15 months old maybe for that reason a commitment discount is not added to my bills and my bill amount is very high forme. So that's the reason I try to set up my own commitment discount for my blog.
I config my blog comes to the default configuration. My machine type is g1-small and uses 10 GB storage.
Fill in the information on the commitment page. Them click to purchase button, I face an error.
Creating commitment "commitment-1" failed. Error: invalid value for type Long
Guide me on how to solve it.
Unfortunately you won't be able to use Committed Discounts.
You've mention that you are using g1-small
My machine type is g1-small and uses 10 GB storage
In the Restrictions part you will find:
Committed use discounts do not apply to preemptible VM instances, N1 shared-core machine types, or extended memory.
g1-small is a shared-core machine type. You can confirm it in this docs or in the GCP UI like below (view from Compute Engine)
In Commitment types you can find information on what resources can be committed. On the bottom of this part you also can find information that g1-small cannot be committed.
You can't purchase commitments for f1-micro, or g1-small machine types or for the sole-tenant premium charge.
Regarding storage, only Local SSD disk can be committed and those are 375 GB as per About local SSDs documentation.
Each local SSD is 375 GB in size, but you can attach a maximum of 24 local SSD partitions for 9 TB per instance.
To sum up
With your current setup you are not able to use Committed Discounts. You would need to use different machine type.

my instance is getting billed even after buying a reserved instance (AWS)

Thanks for looking into this
I have purchased 2 reserved instance on AWS t3a.xlarge + windows and t3a.xlarge + windows + ms SQL for one year with no upfront as the payment method and region as Mumbai(ap-south)
Post the purchase I have launched the 2 instances in the same region with the same configuration AS I checked a day later I was getting billed for those new servers-where the reserved instance was not used.
How should I proceed here?? and where did I made the mistake
thanks in advance
Best way to look at this is through the AWS Cost Management service (Billing). In there you'll find the utilization dashboard and the coverage dashboard of your Reserved instances. That should give you a good idea why the RIs weren't applied.
Because there is a lot of missing information from your question, I'd suggest to check the following:
Regional vs AZ RIs - make sure that you didn't purchase RIs for a specific AZ and then deployed in in a different one (even if the region is the same)
See your hourly usage patterns. It's not attached to an instance, and calculated on a hourly basis.
Check carefully that the RIs you purchased are aligned with exactly what you deployed as you talked about a Windows machine which has several different offerings.
Good luck!

Are the limits for Google Cloud's Always Free on a per-project or per-account basis?

Currently, Google Cloud Platform offers "1 non-preemptible f1-micro VM instance per month" amongst other things, for free, as part of its Always Free tier.
However, I can't determine if the limits assigned to the free tier, like the single f1-micro instance, are per-account (ie, for a single Google email address), or per-project.
Basically: if I make another GCP project under the same account, can I run another f1-micro for free, or will the second one cost me?
The always free tier depends on the billing account
This means that this limits are shared by the different projects you have under the same billing account.
So what you were asking of having an additional VM on another project will not be free, however you can create another account and have this additional VM on this account and that one will be free.
Per the documentation available at enter link description here ,
Your Always Free f1-micro instance limit is by time, not by instance.
Each month, eligible use of all of your f1-micro instances is free
until you have used a number of hours equal to the total hours in the
current month. Usage calculations are combined across the supported
regions.
So to answer your question, you will get charged based on the amount of time you use the instance(s)
Always Free resources are calculated per billing account. (not the email itself).
So you don't have to create a new email to have an additional VM, just add a new billing account and link it to a different project, then you can have another free VM on that project.
I will try it this month, i am setting up two VM in two different projects linked to two different billing accounts all under single email, i will let you know if it worked.

Committed use discounts: How to apply to a VM

I purchased a VM with a committed use discount from GCP and it's active but now I would think that this VM would be added to my VM instances list but it's not.
My two old VM's are still running but I don't see my VM that should be connected to my committed use discount purchase.
Does anybody know how to proceed to setup a VM with my purchase?
Thanks,
Claudio
Committed use discounts are automatically applied to the project they were purchased under, and are only applied to the number of cores that were specified when the commitment was purchased.
So for example, if the commitment was made for 4 cores for 24 hours and 8 were used, the discount will be applied to the 4 cores.
It is also specific to a region. If you purchase a committed usage discount for us-east1 it won't apply to a VM in us-central1 for instance.
You can find more detailed information and some examples on this article here .

My basic (free) account on AWS S3 is going to expire either it move to other plan or stay on basic (free)

I have S3 basic (free) account which i have been using for last one year. In coming month it is going to be expired , my question what is its expecting behavior after expired whether it stayed in basic and charge me what i use or forced me to move other plans like developer , business. If it moved to developer account then should i have to pay $49 dollars or not.
There is no such thing as a "free" AWS account.
There is, however, something called the Free Usage Tier, which provides limited quantities of certain services at no charge during the first 12 months of the account.
For example, the Free Usage Tier includes 750 hours per month of a t2.micro instance running Windows and another one running Linux. If you stay within that level of usage, there will be no charge. A control panel is available within the AWS management console to view consumption of the Free Usage Tier.
At the end of the initial 12 months, the Free Usage Tier no longer applies and the account will be charged for these services based upon actual usage.
This is completely separate to AWS Support, which has pricing tiers that you mentioned:
Basic (no extra charge)
Developer (a monthly flat fee)
Business
Enterprise
You are under no compulsion to subscribe to AWS Support. You can continue on Basic Support at no extra charge. However, if you are using AWS for production workloads, it would be advisable to subscribe to AWS Support so that you can ask questions about the service.
Bottom line: There is no need to change anything. However, you will be charged the list price for any services you consume after your 12-month period.