AWS Database Blog
Use Amazon RDS Proxy with IAM authentication for cross-account access
This post is a follow-up to Use Amazon RDS Proxy to provide access to RDS databases across AWS accounts, addressing cross-account connectivity when using RDS Proxy. We discuss how you can achieve cross-account connectivity while taking advantage of the simplicity and benefits of IAM authentication.
Faster development with Amazon DynamoDB and Amazon Q Developer
Amazon Q Developer, a generative artificial intelligence (AI) assistant, can help accelerate the development of applications on AWS. In this post, we create a DynamoDB table using IaC then perform create, read, update, and delete (CRUD) operations on the table using Python and Boto3 (with additional observations for JavaScript and Java at the end of the post). We demonstrate how Amazon Q can improve your speed of development for these tasks.
Obtaining item counts in Amazon DynamoDB
Customers often ask for guidance on how to obtain the count of items in a table or within specific partitions (item collections). In this post, we explore several methods to achieve this, each tailored to different use cases, with a focus on balancing accuracy, performance, and cost.
How Delivery Hero perfects restaurant operations using gamification with Amazon DynamoDB
In this post, we provide an overview of Delivery Hero’s goals and how we used Amazon DynamoDB to build a scalable and cost-efficient solution, leveraging gamification to improve restaurant operations.
Migrate an Oracle database to Amazon RDS for Oracle using Oracle GoldenGate Microservices Architecture
In this post, we show you how to migrate an Oracle database to an Amazon RDS for Oracle DB instance. The solution uses Oracle Data Pump for initial data load and Oracle GoldenGate Microservices Architecture installed on an Amazon Elastic Compute Cloud (Amazon EC2) instance as the Oracle GoldenGate hub for change data capture.
Create self-managed replicas for an Amazon RDS for Db2 instance for read scaling and disaster recovery
In this post, we explain how to use RDS Db2 Snapshot and AWS Database Migration Service (AWS DMS) to create cross Region replicas for your RDS for Db2 DB instance. If you want to use this replica for read scaling, there needs to be logic built at the application layer to direct only read traffic to the replica.
Resolving non-responsive connection issue to on-premises Oracle multitenant architecture database having local listeners behind firewall from the cloud
Oracle Multitenant Architecture uses a container-based architecture specifically designed for the cloud. It enables the Oracle database to function as multitenant container database (CDB) where application databases are created as pluggable databases (PDB) inside the container database (CDB). A PDB is a collection of schemas, schema objects and non-schema objects, and self-contained for an application […]
AWS DMS homogenous migration from document-oriented databases to Amazon DocumentDB
In this post, we discuss how to migrate a self-managed document database or Amazon DocumentDB database to Amazon DocumentDB using AWS DMS homogeneous migration.
Migrate Cassandra workloads to Amazon Keyspaces using CQLReplicator
In this post we walk through the steps to setup CQL Replicator and migrate a table from self-managed Cassandra cluster to Amazon Keyspaces. We demonstrate how to set up, run, and shut down the CQLReplicator job using command line tooling and observe changes flowing through the pipeline in Amazon CloudWatch.
How Phreesia replicated a 30 TB SQL Server database to Amazon S3 with AWS DMS
In this post, we discuss how Phreesia used AWS DMS to replicate their on-premises database to AWS in an effective and cost-optimized manner. Because of the database’s large size and complex data structure, properly tuning the AWS DMS configuration was critical to minimize the migration duration and cost. We outline the fine-tuning techniques that were applied to optimize the AWS DMS task settings, instance size, IOPS provisioning, and table mappings. Applying these performance optimizations allowed Phreesia to develop a migration strategy to move this 30 TB database to Amazon S3 in just 2 days without disruption to production workloads.