Integration with RDS
See original GitHub issueThis issue collects all the requirements for RDS support in Spring Cloud AWS 3.0 (based on AWS SDK v2).
The key feature in RDS integration is support for read replicas:
- use RDS read replicas for
readOnly
connections (transactions started with@Transactional(readOnly=true)
Additionally we need to support:
Both can be achieved with official drivers:
Regarding read replicas support, in addition to what has been offered in 2.x we must support:
- ability to choose connection pool (in 2.x only Tomcat pool is supported)
- ability to choose JDBC driver
- Add support for passing query parameters to JDBC url #679
- Aurora
To research:
- should we support RDS proxy?
- should we support Aurora Serverless?
Issue Analytics
- State:
- Created a year ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Integrating an Amazon RDS for SQL Server DB instance with ...
You can transfer files between a DB instance running Amazon RDS for SQL Server and an Amazon S3 bucket. By doing this, you...
Read more >Amazon RDS and Integrate.io
With an intuitive interface to help you set up and operate your databases, RDS is a cost-efficient solution that can resize to any...
Read more >Amazon Relational Database Services (RDS) Integrations
Zapier lets you connect Amazon Relational Database Services (RDS) with thousands of the most popular apps, so you can automate your work and...
Read more >Amazon RDS MySQL Integration: 3 Easy Steps - Hevo Data
Steps to Set Up Amazon RDS MySQL Integration · Step 1: Generate a New MySQL DB Instance · Step 2: Download a Standard...
Read more >Integrating AWS S3 buckets with AWS RDS SQL Server
Use S3 integration with RDS SQL instance. Once we have applied for the IAM role in the RDS instance, we can connect to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For handling clusters -
can we add a flag
cloud.aws.employee-db.isCluster=true
And in https://github.com/spring-attic/spring-cloud-aws/blob/e9e7b8cb158013464caa792b3e2de9cf7179678a/spring-cloud-aws-jdbc/src/main/java/org/springframework/cloud/aws/jdbc/rds/AmazonRdsReadReplicaAwareDataSourceFactoryBean.java#L73
Replace
getDBInstance
withgetDBClusterInstance
which usesthis.amazonRds.describeDBClusters
to get the writer instance andgetReadReplicaIdentifiers
to get read replica identifiers and rest of the code remains the same?Hi I am assuming
spring-cloud-starter-aws-jdbc
is a “io.awspring.cloud” version of “spring-cloud-aws-jdbc” ( 2.x.x version)I feel this enhancement request should be backed in to 3.x.x if not already.
Steps to recreate:
In 2.x.x the library is attempting to “createInstance” and calls describe-db-instances which results below: (using cli to replicate the issue)
Class: AmazonRdsReadReplicaAwareDataSourceFactoryBean method: createInstance
From result: “ReadReplicaDBInstanceIdentifiers”: [ “abc-rr1”, “arn:aws:rds:us-west-2:12345678910:db:abc-rr-2” ],
An error occurred (InvalidParameterValue) when calling the DescribeDBInstances operation: The parameter Filter: db-instance-id is not a valid identifier. Identifiers must begin with a letter; must contain only ASCII letters, digits, and hyphens; and must not end with a hyphen or contain two consecutive hyphens.
Class: AmazonRdsDataSourceFactoryBean method: createDataSourceInstance -> getDbInstance
DescribeDBInstancesResult describeDBInstancesResult = this.amazonRds.describeDBInstances((new DescribeDBInstancesRequest()).withDBInstanceIdentifier(identifier)); -> This results in failure as we are doing describe-db-instances with an arn.
Potential solution: getDbInstance method should identify if aws returned an ARN and convert the describe-db-instances to be following
aws rds describe-db-instances --db-instance-identifier abc-rr-2 --region us-west-2
instead of calling directly using ARN.I am unable to open a PR as I am not sure where this module exists.