amazon-rds

Configure GlassFish JDBC connection pool to handle Amazon RDS Multi-AZ failover

半世苍凉 提交于 2019-11-30 10:15:34
I have a Java EE application running in GlassFish on EC2, with a MySQL database on Amazon RDS. I am trying to configure the JDBC connection pool to in order to minimize downtime in case of database failover. My current configuration isn't working correctly during a Multi-AZ failover, as the standby database instance appears to be available in a couple of minutes (according to the AWS console) while my GlassFish instance remains stuck for a long time (about 15 minutes) before resuming work. The connection pool is configured like this: asadmin create-jdbc-connection-pool --restype javax.sql

What are the respective advantages/limitations of Amazon RDS vs. EC2 with MySQL? [closed]

岁酱吖の 提交于 2019-11-30 10:04:48
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . I realize a couple of basic differences between the two, i.e. EC2 is going to be cheaper RDS I wouldn't have to do maintenance Other than those two, are there any advantages to running my database from RDS as opposed to a separate EC2 server acting as a MySQL server. Assuming

Accessing AWS RDS using IAM Authentication and Spring JDBC (DataSource and JdbcTemplace)

两盒软妹~` 提交于 2019-11-30 09:57:20
I am not able to figure out how to implement this. Any help and/or pointers will be greatly appreciated. Currently, my Java/Spring application backend is deployed on EC2 and accessing MySQL on RDS successfully using the regular Spring JDBC setup. That is, storing database info in application.properties and configuring DataSource and JdbcTemplate in @Configuration class. Everything works fine. Now, I need to access MySQL on RDS securely . RDS instance has IAM Authentication enabled. I have also successfully created IAM role and applied inline policy . Then, following the AWS RDS documentation

Can RDS snapshots be transferred across AWS accounts?

坚强是说给别人听的谎言 提交于 2019-11-30 08:24:08
问题 In the time since this question was answered, AWS Tools for Powershell has been released and I basically have the same problem: I have an RDS snapshot on one AWS account that I would like to transfer to another. So far I've been able to select the snapshot that I want with the Get-RDSDBSnapshot cmdlet, and I'd like to take that Amazon.RDS.Model.DBSnapshot object and use it in the other account. I've been looking around and I think the Restore-RDSDBInstanceFromDBSnapshot cmdlet (maps to rds

AWS Elastic Beanstalk change RDS Endpoint

假如想象 提交于 2019-11-30 07:54:49
How do I change the configured RDS endpoint of an AWS Elastic Beanstalk environment? E.g. after the RDS database was deleted or should be replaced with a new RDS database. Update The topic remains complex and the AWS Elastic Beanstalk (EB) documentation could still do a better job to clarify available options. The question has been about how to change an RDS endpoint , which seems to be read in two different ways: One could interpret it about how to attach an existing externally managed RDS endpoint to an existing (not new!) EB environment - this is indeed not possible, rather one would need

Adjusting for the default time-zone setting on RDS

拥有回忆 提交于 2019-11-30 07:10:50
问题 We recently switched to an RDS instance and noticed that bunch of our database tasks were getting triggered 4 hours earlier than needed. On investigating further, the problem is caused by the default time-zone setting (UTC) on the RDS instance. Since this setting can not be altered, we would like to fix the issue on the code level globally across all our applications using this database instance. I tried to set the time-zone on the db instance I create to 'US/Eastern' by using set GLOBAL time

Point Heroku application to AWS RDS database

北慕城南 提交于 2019-11-30 06:51:41
问题 I need to point my Heroku application to my AWS RDS database. My RDS database is up and running and has a security group with 0.0.0.0/0 access. Currently, I've removed my Heroku postgreSQL database and I am attempting to point my Heroku application to my RDS database. For some reason my application is crashing. The step that I believe I am on is setting my DATABASE_URL on the Heroku side. Let's say that my database credentials are: db instance: mydb dbname: mydb user: wcronyn pass: password I

download RDS snapshot

杀马特。学长 韩版系。学妹 提交于 2019-11-30 04:10:51
I recently downgraded my EC2 instance. I can no longer connect to RDS. I think it might be that the internal IP is different and now the logins are attached to that specific IP. I haven't been able to figure it out. I would like to be able to get a backup from the snapshot. Is there a way to download it through AWS? You can't download an RDS snapshot. You can however connect to it and export your databases. Downgrading your instance should not affect connectivity unless you had set up your security groups incorrectly (Opening ports to an IP instead of another security group). abguy In addition

AWS Lambda can't connect to RDS instance, but I can locally?

北城以北 提交于 2019-11-30 01:48:10
问题 I am trying to connect to my RDS instance from a lambda. I wrote the lambda locally and tested locally, and everything worked peachy. I deploy to lambda, and suddenly it doesn't work. Below is the code I'm running, and if it helps, I'm invoking the lambda via a kinesis stream. 'use strict'; exports.handler = (event, context, handlerCallback) => { console.log('Recieved request for kinesis events!'); console.log(event); console.log(context); const connectionDetails = { host: RDS_HOST, port:

Is there a way to run initial SQL when creating an RDS database instance using CloudFormation?

ぃ、小莉子 提交于 2019-11-30 01:19:59
I am creating an RDS instance using CloudFormation using this: "Resources": { "myDB": { "Type": "AWS::RDS::DBInstance", "Properties": { "AllocatedStorage": "5", "DBInstanceClass": "db.m1.small", "Engine": "MySQL", "EngineVersion": "5.5", "DBName": "mydb", "MasterUsername": { "Ref": "DBUser" }, "MasterUserPassword": { "Ref": "DBPassword" }, "DBParameterGroupName": { "Ref": "myRDSParamGroup" } } } and it all works. But I need to run initial SQL on the DB when its created, to setup my apps schema. My current approach is to have the app self migrating, but I'd like to do it in the CloudFormation