we try to implement a backup solution with Google BackUp and DR, this service deploy in our vpc an appliance instance(n2-standard-16) with 4TB ok disk, i' don't have found any information about the price of this instance in GCP backup and DR pricing model.
Did you know if this instance is payed normally or this are a "special" price model?
Regards
Related
I came across the following question during my AWS practice and I have a different opinion and want to post it here for more discussion as it addresses a very common need, thanks.
http://jayendrapatil.com/aws-rds-replication-multi-az-read-replica/?unapproved=227863&moderation-hash=c9a071a3758c183b1cf03e51c44d2373#comment-227863
Your company has HQ in Tokyo and branch offices all over the world and is using logistics software with a multi-regional deployment on AWS in Japan, Europe and US. The logistic software has a 3-tier architecture and currently uses MySQL 5.6 for data persistence. Each region has deployed its own database. In the HQ region you run an hourly batch process reading data from every region to compute cross-regional reports that are sent by email to all offices this batch process must be completed as fast as possible to quickly optimize logistics. How do you build the database architecture in order to meet the requirements?
A. For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ region
B. For each regional deployment, use MySQL on EC2 with a master in the region and send hourly EBS snapshots to the HQ region
C. For each regional deployment, use RDS MySQL with a master in the region and send hourly RDS snapshots to the HQ region
D. For each regional deployment, use MySQL on EC2 with a master in the region and use S3 to copy data files hourly to the HQ region
E. Use Direct Connect to connect all regional MySQL deployments to the HQ region and reduce network latency for the batch process
I lean to E, the reason is:
Direct Connect provides bandwidth that bypasses the ISP and more privately, faster (if needed).
The question doesn't factor cost here.
The initial setup time could be longer comparing to other options, however, initial setup time cost should not be the point here, what is asking here is “this batch process must be completed as fast as possible to quickly optimize logistics.”, so it is not about the initial setup, it is about how to implement the right solution to deliver the “as fast as possible” service AFTER the setup
And hence I believe E is the best option for the need.
I am open to discussion, please, if my understanding is wrong. Thank you.
E is not applicable. You cannot use Direct Connect to connect 2 VPCs. Direct Connect is used to connect VPC and your premise. Question asks about multi-regional AWS infrastructure without mentioning anything about HQ not being hosted on AWS.
The easiest solution is A in my opinion.
I have taken a AWS Lightsail Unix Instance for one of my pilot project, I wanted to explore AWS ecosystem and thought this would be a easy playground to start with. The plan I opted was a USD 5 per month, which gives 1 GB Memory, 1 Core Processor, 40 GB SSD Disk and 2 TB Transfer.
After subscribing I created a LAMP instance and a Plesk Instance, assigned static IPs to both instances and setup connections from my PC to transfer files using PuTTY; also setup access to Plesk and phpMyAdmin to start work.
In the first month itself, I am seeing a huge bill of USD 985 for using AWS RDS, details in bill are as below:
Amazon Relational Database Service for MySQL Community Edition
$1.080 per RDS db.r4.xlarge Multi-AZ instance hour (or partial hour) running MySQL
My question is - When I created LAMP, does it create a AWS RDB service automatically, I have hardly used MySql for anything. It seems AWS Lightsail is throwing hidden charges without notifying customers about actuals.
No, creating a LAMP stack on Lightsail does not create an RDS instance on your behalf. With the LAMP stack on Lightsail, the MySQL database is installed on that instance alongside PHP and Apache - there is no charge beyond the $5.00 / month (in your case) as long as you don't go over the data transfer limit.
I can't say why you're getting charged for RDS, but it's not because you fired up Lightsail instances.
Thank you folks!
I tried to go through several docs AWS provides on pricing. There is no indication that AWS RDB services automatically starts on LAMP installation. I wanted to take second opinion before raising a complaint with them. I have opened a case, and they have confirmed to revert the charges, however there is no clarity how AWS RDS service has started. At present I have removed all DB snapshots and backups.
What is the rest API to get the AWS spot instances Pricing? Please provide some examples.
Thanks
Siva
The spot price can vary continually. To discover the actual spot price charged for instance you are running, use the Spot Instance Data Feed - Amazon Elastic Compute Cloud:
To help you understand the charges for your Spot Instances, Amazon EC2 provides a data feed that describes your Spot Instance usage and pricing. This data feed is sent to an Amazon S3 bucket that you specify when you subscribe to the data feed.
To obtain general historical information about spot pricing, use Spot Instance Pricing History - Amazon Elastic Compute Cloud.
My doubt is how the Amazon RDS instance is billed. I read somewhere that it is a component based billing based on the CPU/hour, number of input/output requests, etc.,
How are the I/O requests interpreted? I have a model in which I am trying to reduce the number of input queries that go into the cloud. Will it reduce my yearly cost to a good extent?
Full pricing information is available on the Amazon RDS Pricing page. It involves:
An hourly charge for the RDS instance
A charge for data storage based on amount of storage (including backup storage beyond the provisioned storage size)
A Data Transfer for traffic flowing out of AWS to the Internet
A minor charge for traffic flowing between Availability Zones
There are no charges relating to database requests. In fact, these requests are directly between client apps and the database and are not visible to AWS.
Update: Amazon Aurora also charges an "I/O request" charge. See comments below.
I´m quite new with Amazon Web Services. Some months ago, I created a m3.medium instance on demand. According to AWS EC2 prices, this instance is 0.077$/hour. This means 55,44$/month (november). However, I got a billing of 74.76$ (91.12$ with taxes).
I guess I have some service that I´m missing and maybe they are charging me:
In example, I have an Elastic Load Balancer. Am I getting charged for that? Actually, I have realized I had two ELB. It looks like I created it another one for testing purposes and I forgot it there.
I also have an Elastic Block Store (EBS) with 8GB of size. Am I getting charged for that? Do I really need it?
When I check my billing status, I don´t see any reference to these both two services. So, I guess they are included in the EC2 billing, right?
I don´t know where I got the idea that when you start an EC2 instances, an ELB and EBS was included with no additional charges.
As you can see, I´m quite lost with these services.
Billing information is available from the account menu (in the top-right, next to the Region menu). It will display a simple breakdown of charges by service:
More detailed billing information is available by clicking the "Bill Details" link (in the top-right). It will show a breakdown of charges by service for any selected month:
EBS charges are included under "Elastic Compute Cloud":
To answer your questions:
Elastic Load Balancer pricing
Elastic Block Store (EBS) pricing: This is the disk storage for Amazon EC2. You will be charged for any volumes from the time they are created until they are deleted.
There is also a Free Usage Tier that includes 30GB of EBS storage each month in your first year (amongst other services). If you use services within this free tier, there will be no charge.