Amazon Aurora DSQL is provided as a Preview service.
To learn more, see Betas and Previews
To connect to Aurora DSQL, use a standard Postgres driver configured with TLS. To connect, you specify a Postgres role as the user, a password, and an authentication token. Aurora DSQL provides libraries for you to generate authentication tokens in most AWS supported languages. Once you're connected, you can use your session to run transaction for up to 1 hour with a transaction timeout of 5 minutes each. If you start a transaction in the 60th minute, Aurora DSQL still runs the transaction until you reach the limit of five minutes before it closes the session.
Aurora DSQL authenticates each session with a state, such as prepared statements or an active query. A connection is a TLS-wrapped TCP connection that might get rejected if Aurora DSQL can't turn it into a session for any reason. Each session maps to exactly one connection. With a connection, a client can't have a session, and a connection can only have one session in Aurora DSQL.
To make sure that a user with revoked Postgres credentials can't connect to a cluster on an existing session, we authenticate the user against Aurora DSQL's IAM trust tables at the beginning of each transaction.
Connection limits
By default, you can create up to 1000 connections per cluster at 10 connections per second with a burst of 100. For example, if one connection is one token in a token bucket, you begin with 100 available tokens in the bucket. If you create 100 tokens, you have zero remaining tokens and have to wait for a second before you can create more connections. The refill rate is 10 tokens per second. To increase these limits, contact AWS support.
