Q. Which cloud environments are supported?
Q. Which Postgres versions are supported by Cloud Database?
Q. What's the difference between PostgreSQL and Postgres Plus Advanced Server?
Q. Which web browsers does the Postgres Plus Cloud Database console support?
Q. What options do I have for purchasing the Cloud Database?
Q. How do I purchase the pay-as-you-go Cloud Database?
Q. How do I purchase the yearly subscription for Cloud Database?
Q. Which Amazon deployment regions are supported?
A. The following regions are currently supported:
- United States East (Virginia)
- United States West (N. California)
- EU West (Ireland)
- Asia Pacific SouthEast (Singapore)
- Asia Pacific SouthEast (Australia)
- Asia Pacific NorthEast (Tokyo)
If you need support for another region, please contact us
Q. Can I use my existing on-premise database subscription to use Cloud Database?
Q. Can EnterpriseDB help me estimate the costs and pricing for my application?
The first method is to price the key cost parameters as they are detailed at: Cloud Database Pricing.
Note that these prices are for the US East (Northern Virginia) Region (for other regions visit the Postgres Plus Cloud Database Amazon Marketplace pages: http://aws.amazon.com/marketplace/pp/B00MI8NK4U and http://aws.amazon.com/marketplace/pp/B00MI8R5A0). For each parameter, guess-timate the quantities and multiply the price by the quantity. Then add your estimated costs for all parameters. This should give you a good approximation.
For example, for the 'Amazon EC2 On-Demand Instances' portion of your monthly Amazon bill, you will need to pick a Database Instance Class for each cluster you set up, and decide how many total servers (1 master plus n read replicas) will run in the cluster. Then, multiply the number of servers times the hourly rate for that instance class times the average number of hours in a month.
For example, the monthly charge for a Postgres Plus Cloud Database Advanced 3 server cluster composed of m1.small instances would be: 3 servers x 0.26 per hour x 729.6 average hours in a month = $569. Then, estimate the Amazon EC2 Data Transfer Rate, Elastic Block Storage, and S3 Store Fees -- and total everything up.
The second method is to use Amazon's cost estimator: http://calculator.s3.amazonaws.com/calc5.html. Keep in mind that this estimator does not include EnterpriseDB's fees built into the cost of the Amazon EC2 On-Demand Instances Running Amazon Linux as noted on our pricing page: Cloud Database Pricing
If your application is mission critical, large and/or complex, or your staff is limited in time or knowledge, EntepriseDB offers a Cloud Database Consulting engagement on a professional services basis. In this engagement, we work with your staff over a few days to evaluate and prototype migrating your database tier from an on-premise or existing hosted environment to a secure and elastic cloud deployment on Postgres Plus Cloud Database.
Finally, if you need DBA expertise, EnterpriseDB also offers the RemoteDBA service which allows you to immediately apply qualified staff-power where you need it for either short or long term engagements in a highly cost efficient manner tailored to your needs.
Please email our Sales department for details or call +1 781-357-3390 or 1-877-377-4352 (US Only).
Q. Who owns the data that I store at Amazon under Cloud Database?
Q. In the future, if your Cloud Database service is no longer available, what happens to my data?
Q. How do I get usage or billing information, change my payment method, or cancel my purchase?
Q. Can I register two different users to manage the same clusters?
Q. Is Cloud Database available for deployment on bare metal systems?
Q. Which private clouds are supported by the Cloud Database?
A. Amazon Virtual Private Clouds (VPCs) are supported by the Cloud Database. Physical private cloud support is not currently available.
Q. What if I have more questions about Cloud Database?
A. Contact the EnterpriseDB Sales team by email at: firstname.lastname@example.org, on the EnterpriseDB website at: http://www.enterprisedb.com/general-inquiry-form, or by phone at: +1 781-357-3390 or 1-877-377-4352 (US Only).
Q. Do I need to make changes to my database for better performance in your cloud database?
A.To assist organizations who are thinking of moving to the cloud and have concerns about the efficiency of their database systems, we offer our popular Architectural Health Check service. This analysis service identifies performance and best practices issues and makes actionable recommendations to optimize your database. Acting on these recommendations will make your database perform better on-premise, and be prepared to take full advantage of cloud computing.
Q. Does Cloud Database support PostGIS?
Q. Does Cloud Database create databases automatically?
A. Yes, the Cloud Database will create replicas within your database cluster automatically based on thresholds you set to handle increasing read loads (known as horizontal scaling, or scale out). When a Cloud Database cluster is first created it has a single master server plus the number of read replicas you specify. The master hosts a single Postgres cluster which can contain many databases.
Q. Do I have my own instance of the Cloud Database console or am I sharing it with others?
A. Each Postgres Plus Cloud Database console, one in each supported Amazon region, supports all customers in that region.
However, each customer's Cloud Database cluster is entirely private and is not shared with anyone else.
Q. What operating system is used for my instances?
Q. What type of network or shared file system is used for my instances?
A.The Amazon public cloud implementation is not based on a network or shared file system. It is based on LVM2 and ext3
Q. Can I create and run independent instances of PostgreSQL or Postgres Plus Advanced Server for different applications?
A. Yes. With Cloud Database, you can create and run independent instances of PostgreSQL or Postgres Plus Advanced Server for different applications.
Q. How is High Availability achieved in Cloud Database?
A. A JGroups cluster manager and node agent manage server health monitoring and automatic fail-over and are setup automatically for you when you create additional replicas. Pgpool is used to handle connection pooling allow more efficient use of client connections. Postgres' binary streaming replication is used to keep read replicas in sync with the master server ensuring READ loads are serviced. Auto-scaling maintains data availability under high or spiky loads by adding more replicas to the cluster as needed.
Q. What else is pgpool used for?
Q. How is high availability handled for the Cloud Database Manager itself on Amazon?
A. There are a couple of ways that a crash of the Cloud Database instance is handled. When you first create your Cloud Database instance in Amazon, you can choose to provide the instance with Termination Protection. This will automatically spin up another instance of the Cloud Database Console/Cluster Manager. Alternatively you can manually create another Cloud Database Console/Cluster Manager from the AWS console. In both cases: a) your database cluster(s) will continue running, and b) the new Console/Cluster Manager will find your running clusters and resume managing them.
Q. Do the instances in my cluster run in different availability zones for better high availability?
A. Yes, each instance runs in a different availability zone. You can check your Amazon console on AWS to determine in which availability zone each instance is running.
Q. Does Cloud Database make use of Amazon's Elastic IPs?
A. Yes, if the Master fails over to a new VM instance, the load balancing IP address will remain the same so that your applications requires no change in connection settings.
Q. Can I use Amazon's internal private IP instead of the public DNS to save on data transfer charges?
A. Within an Amazon region, if your Amazon hosted client or application server uses the public DNS, Amazon will smartly use the internal private IP, even across availability zones, saving you data transfer charges.
Q. Is pgpool required when using the Cloud Database?
A. Database access through the pgpool load balancing port is optional. However, if your cluster scales out additional replicas you will have to manually send application requests to the different servers. You can always connect directly to your database instances.
Q. How are SELECT statements with functions that modify data load balanced?
A. All INSERT-UPDATE-DELETE statements are sent to the master for processing. All SELECT statements get spread across the entire cluster. However, the load balancer does allow you to declare a list of functions, which, if they appear in any SELECT statement, cause that statement to executed on the master. This prevents any SELECT statements that modify data from being sent to a read replica. You can specify lists of functions using the parameters "black_function_list" and "white_function_list" in the configuration panel for a cluster.
Q. How much downtime occurs during fail-over?
A. If the master fails over there will be a short period of downtime for writes as a new master is created and attached to the old master's data, preventing any data loss. The time period is dependent on the size of the machine being created, its region, and performance of the Amazon infrastructure.
Q. How are replicas created in Cloud Database?
A. Replicas are kept up to date with the master server using Postgres' built-in streaming replication in Hot Standby mode.
Q. Is streaming replication synchronous?
A. No, it is asynchronous. Depending on configuration settings, load and other factors affecting performance, PostgreSQL's streaming replication is fast enough that each transaction can be replicated from the master database server to a replica server as quickly as the master database can perform a single transaction.
Q. How much data loss occurs in a fail-over situation?
A. If the master fails, all completed transactions are saved as the data is attached to a new master instance. If a replica fails, its replacement may be behind the master initially, but it will catch up as streaming replication resumes.
Q. Do the master, replicas, and console app use public or private IP addresses to communicate?
A. They use private IP addresses with certificate-based communication.
Can I manage the Postgres configuration parameters using Cloud Database?
A. Yes, by using the Configurations panel in the Cloud Database console Clusters tab. You can also create multiple parameter groups or configuration profiles that can be used for different clusters you set up.
Q. How do I configure access permissions (hba.conf) to the cluster?
A. Currently, these have to be managed manually on each server using ssh.
Q. Can I manage the pgpool configuration parameters using Cloud Database?
A. Yes, by using the Configurations pane on the Clusters tab in the Cloud Database console.
Q. How are backups made in Cloud Database?
A. Backups are made by creating an EBS backed snapshot during a timeslot you specify when you create a cluster (e.g., between 2:00 am and 4:00 am). You can also specify how many rolling daily backups to retain (e.g., the last 3 days). This is handled for you automatically.
Q. Does Cloud Database support point in time recovery (PITR)?
Q. What kind of scaling is available in Cloud Database?
A. You can automatically scale the storage capacity and connections according to thresholds pre-set by you. For example, if you set a 75% storage threshold, then when the threshold value is exceeded, the Postgres Plus Cloud Database will automatically allocate, deploy, and attach additional storage for you, and record the events in the Event viewer. Also, you can manually scale to larger or smaller machine sizes.
Q. Does auto-scaling scale down with a reduction in demand?
A. No, it must be handled manually.
Q. What is the performance difference between cloud computing and running directly on physical hardware?
A. There are too many variables and use cases to make a realistic comparison. Suffice to say that in Amazon's public service, virtual machines as large as 64 CPUs and 128 GB memory are available, which should be more than enough to satisfy most applications.
Q. What is the largest database I can use?
A. Cloud Database can support multi-terabyte databases.
Q. What kind of monitoring does Cloud Database provide?
A. Cloud Database provides charts displaying CPU Load and Storage Space metrics. It also has an Event viewer that shows when instances join or leave a cluster, error events, and other status indicators. Finally, you can use Postgres Enterprise Manager to monitor your instances in much greater detail along with alerting and other features such as capacity management.
Q. Can Postgres Enterprise Manager agents monitor Cloud Database instances?
A. Yes, PEM can monitor PostgreSQL and Postgres Plus Advanced Server instances on public and private clouds or regular bare metal installations in the data center performed by Cloud Database.
Q. Can I use my existing Postgres based tools with Postgres Plus Cloud Database instances?
Q. Where can I find documentation for Cloud Database?
A.You can download Cloud Database documentation here. The Cloud Database Console main dashboard also includes links to tutorials covering various tasks.
Q. How does Cloud Database help developers?
Q. How do I create my first cluster?
Q. My first instance is up and running, how do I connect my application or a client like pgAdmin?
Q. Can a Java application running in Tomcat on EC2 be connected to a Cloud Database cluster?
Q. How do I scale my cluster up adding another replica?
Q. How do I create a sandbox environment using a copy of production data?