How to commit data models to Amazon Keyspaces and Apache Cassandra
This section shows you how to commit completed data models to Amazon Keyspaces and Apache Cassandra clusters. This process automatically creates the server-side resources for keyspaces and tables based on the settings that you defined in the data model.
![Console screenshot that shows the commit options.](/images/keyspaces/latest/devguide/images/workbench/key_nosql_commit.png)
Topics
Before you begin
Amazon Keyspaces requires the use of Transport Layer Security (TLS) to help secure connections with clients. To connect to Amazon Keyspaces using TLS, you need to complete the following task before you can start.
-
Download the Starfield digital certificate using the following command and save
sf-class2-root.crt
locally or in your home directory.curl https://certs.secureserver.net/repository/sf-class2-root.crt -O
Note
You can also use the Amazon digital certificate to connect to Amazon Keyspaces and can continue to do so if your client is connecting to Amazon Keyspaces successfully. The Starfield certificate provides additional backwards compatibility for clients using older certificate authorities.
curl https://certs.secureserver.net/repository/sf-class2-root.crt -O
After you have saved the certificate file, you can connect to Amazon Keyspaces. One option is to connect by using service-specific credentials. Service-specific credentials are a user name and password that are associated with a specific IAM user and can only be used with the specified service. The second option is to connect with IAM credentials that are using the AWS Signature Version 4 process (SigV4). To learn more about these two options, see Creating credentials to access Amazon Keyspaces programmatically.
To connect with service-specific credentials, see Connecting to Amazon Keyspaces with service-specific credentials.
To connect with IAM credentials, see Connecting to Amazon Keyspaces with AWS Identity and Access Management (IAM) credentials.