53 stable releases

new 1.54.0 Nov 12, 2024
1.52.0 Oct 31, 2024
1.39.0 Jul 22, 2024
1.20.0 Mar 26, 2024
0.11.0 Nov 20, 2023

#2210 in Network programming

Download history 57/week @ 2024-07-27 48/week @ 2024-08-03 210/week @ 2024-08-10 89/week @ 2024-08-17 95/week @ 2024-08-24 136/week @ 2024-08-31 116/week @ 2024-09-07 148/week @ 2024-09-14 85/week @ 2024-09-21 92/week @ 2024-09-28 214/week @ 2024-10-05 65/week @ 2024-10-12 192/week @ 2024-10-19 170/week @ 2024-10-26 238/week @ 2024-11-02 121/week @ 2024-11-09

725 downloads per month

Apache-2.0

1.5MB
25K SLoC

aws-sdk-paymentcryptography

Amazon Web Services Payment Cryptography Control Plane APIs manage encryption keys for use during payment-related cryptographic operations. You can create, import, export, share, manage, and delete keys. You can also manage Identity and Access Management (IAM) policies for keys. For more information, see Identity and access management in the Amazon Web Services Payment Cryptography User Guide.

To use encryption keys for payment-related transaction processing and associated cryptographic operations, you use the Amazon Web Services Payment Cryptography Data Plane. You can perform actions like encrypt, decrypt, generate, and verify payment-related data.

All Amazon Web Services Payment Cryptography API calls must be signed and transmitted using Transport Layer Security (TLS). We recommend you always use the latest supported TLS version for logging API requests.

Amazon Web Services Payment Cryptography supports CloudTrail for control plane operations, a service that logs Amazon Web Services API calls and related events for your Amazon Web Services account and delivers them to an Amazon S3 bucket you specify. By using the information collected by CloudTrail, you can determine what requests were made to Amazon Web Services Payment Cryptography, who made the request, when it was made, and so on. If you don't configure a trail, you can still view the most recent events in the CloudTrail console. For more information, see the CloudTrail User Guide.

Getting Started

Examples are available for many services and operations, check out the examples folder in GitHub.

The SDK provides one crate per AWS service. You must add Tokio as a dependency within your Rust project to execute asynchronous code. To add aws-sdk-paymentcryptography to your project, add the following to your Cargo.toml file:

[dependencies]
aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
aws-sdk-paymentcryptography = "1.54.0"
tokio = { version = "1", features = ["full"] }

Then in code, a client can be created with the following:

use aws_sdk_paymentcryptography as paymentcryptography;

#[::tokio::main]
async fn main() -> Result<(), paymentcryptography::Error> {
    let config = aws_config::load_from_env().await;
    let client = aws_sdk_paymentcryptography::Client::new(&config);

    // ... make some calls with the client

    Ok(())
}

See the client documentation for information on what calls can be made, and the inputs and outputs for each of those calls.

Using the SDK

Until the SDK is released, we will be adding information about using the SDK to the Developer Guide. Feel free to suggest additional sections for the guide by opening an issue and describing what you are trying to do.

Getting Help

License

This project is licensed under the Apache-2.0 License.

Dependencies

~8–19MB
~283K SLoC