Cloudant warehouse, deleted documents are not synced - ibm-cloud

I went through documentation on Cloudant warehouse but not able to find how are deleted documents synced. My requirement is that, just as in Cloudant replication, I would want documents deleted in Cloudant to also be deleted in dash DB. But I do not see that happening. How do I enable that?

Try synchronizing it again by restarting the warehouse from Cloudant dashboard.

Related

what to do after creating mongodb atlas cluster?

I have created a mongodb free tier atlas cluster. I added an user in Database Acess -> Database Users.
But I don't know if there is anything else to set up, any other kind of users inside the cluster.
Can someone help me with the extra steps (that mongodb "doesnt tell" you to do)?

MongoDB database is getting reset randonmly

I have created a instance of mongodb on AWS EC2 Instance.
I have 2 Spring boot/microservices connected to this database. One is just inserting the data and other is fetching data. In my microservices, I dont have any delete operation and no such code is provided atany time so by mistake data getting deleted scenario will not occure.
**But some how mongodb database is getting reset/cleared. All database is getting deleted.**
I have checked the mongodb configuration and I haven't explicitly changed anything.
Mongodb is community edition.
On spring boot microservices, I am directly using the Mongorepository
JPA to insert or fetch the data.
I dont have any constraints in POJOs.
Can someone point out what might be the issue? Does mongodb has any
default setting for resetting the database?

RDS Snapshot Location for Postgresql

I have Configured AWS RDS Postgresql 9.5 few months back. My DB size is almost 1TB. WHen ever i take a manual snapshot of my DB it is showing in Snapshot tab. Wanted to know the physical location of these files stored. My overall DB size is 2TB, I have taken some 20 snapshots. Where are these snapshot stored locally?
NOTE: I have not configured any S3 manually to store this snapshot.
Behind the scenes, the snapshot data is stored in Amazon S3. However, it is not accessible to you (it is stored in a bucket owned and managed by the Amazon RDS service).
You can only interact with the snapshots via the Amazon RDS console and API.
Snapshot Pricing
From Amazon RDS for PostgreSQL Pricing – Amazon Web Services:
There is no additional charge for backup storage up to 100% of your total database storage for a region. (Based on our experience as database administrators, the vast majority of databases require less raw storage for a backup than for the primary dataset, meaning that most customers will never pay for backup storage.)
After the DB instance is terminated, backup storage is billed at $0.095 per GiB-month.
Additional backup storage is $0.095 per GiB-month.

AWS DMS "Load complete, replication ongoing" not working MongoDB to DocDB

I am trying to make a PoC for MongoDB to DocDB migration with DMS.
I've set up a MongoDB instance with some dummy data and an empty DocDB. Source and Target endpoints are also set in DMS and both of them are connecting successfully to my databases.
When I create a migration task in DMS everything seems to be working fine. All existing data is successfully replicated from the MongoDB instance to DocDB and the migration task state is at "Load complete, replication ongoing".
At this point I tried creating new entries in existing collections as well as creating new empty collections in MongoDB but nothing happens in DocDB. If I understand correctly the replication should be real time and anything I create should be replicated instantly?
Also there are no indication of errors or warnings whatsoever... I don't suppose its a connectivity issue to the databases since the initial data is being replicated.
Also the users I am using for the migration have admin privileges in both databases.
Does anyone have any suggestions?
#PPetkov - could you check the following?
1. Check if right privileges were assigned to the user in the MongoDB endpoint according to https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html.
2. Check if replicate set to capture changes was appropriately configured in the MongoDB instance.
3. Once done, try to search for "]E:" or "]W:" in the CloudWatch logs to understand if there are any noticeable failures/warnings.

Using Amazon S3 as a File System for MongoDB

I am deciding to use MongoDB as a Document management DB in my application. Initially I was thinking to use S3 as a data store but it seems mongoDB uses local file system to store data. Can I use S3 as data store in MongoDB.
thanx
Provisioned IOPS in AWS is ideal for MongoDB.
This link has notes about running MongoDB on AWS and is rather useful.