Perché ricevo l'errore "The snapshot is currently in use by an AMI" quando cerco di eliminare uno snapshot Amazon EBS?

Perché la pipeline di creazione immagini restituisce l'errore "Step timed out while step is verifying the Systems Manager Agent availability on the target instance(s)" (Passaggio scaduto durante la verifica della disponibilità dell'agente Systems Manager sulle istanze di destinazione) in Image Builder?

Perché non riesco a connettermi al mio cluster Amazon DocumentDB?

Come faccio a risolvere i problemi e risolvere l'elevato utilizzo della CPU sulle mie istanze Amazon DocumentDB? 

From the [list of Mongo APIs supported](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html) by DocumentDB in the documentation, it is clear that DocumentDB does not support noCursorTimeout like MongoDB.

Since it is evident that DocumentDB would close a connection after a period of inactivity,
- What is the maximum duration a cursor can remain inactive in DocumentDB? Is there a way to configure this?
- Is the inactivity period the same for all cursors (for Change Streams as well)?

Cursor timeout duration in DocumentDB

Contenuto pertinente