Amazon Neptune | Security Flashcards
How far behind the primary will my replicas be?
Security
Amazon Neptune | Database
Since Amazon Neptune Replicas share the same data volume as the primary instance, there is virtually no replication lag. We typically observe lag times in the 10s of milliseconds.
Can I use Amazon Neptune in Amazon Virtual Private Cloud (Amazon VPC)?
Security
Amazon Neptune | Database
Yes, all Amazon Neptune DB Instances must be created in a VPC. With Amazon VPC, you can define a virtual network topology that closely resembles a traditional network that you might operate in your own datacenter. This gives you complete control over who can access your Amazon Neptune databases.
Does Amazon Neptune support encrypting my data in transit and at rest?
Security
Amazon Neptune | Database
Yes. Amazon Neptune supports encrypting your data in transit using TLS (HTTPS), including the AES-256 cipher suite, to secure the connection between the database instance and the application. This is currently not enabled by default, but can be configured through the cluster parameter group. Amazon Neptune also allows you to encrypt your databases using keys you manage through AWS Key Management Service (KMS). On a database instance running with Amazon Neptune encryption, data stored at rest in the underlying storage is encrypted, as are its automated backups, snapshots, and replicas in the same cluster. Encryption and decryption are handled seamlessly. For more information about the use of KMS with Amazon Neptune, see the Amazon Neptune User Guide.
Can I encrypt an existing unencrypted database?
Security
Amazon Neptune | Database
Currently, encrypting an existing unencrypted Neptune instance is not supported. To use Amazon Neptune encryption for an existing unencrypted database, create a new DB Instance with encryption enabled and migrate your data into it.
