AWS SDK for C++ Ready for Production Use -- Visual Studio Magazine

AWS SDK for C++ Ready for Production Use

The experiment is over and now C++ developers can tap into the production-ready version of AWS SDK that allows them to create modern C++ interfaces to AWS.

By David Ramel
09/13/2016

The Amazon Web Services Software Development Kit for C++ that was introduced as an experiment a year ago is now ready for prime time. That means C++ developers can finally use the open source SDK in production environments.

The company launched a developer preview of the AWS SDK for C++ last March, following an experimental launch in September of last year. Now it's finally ready for real-world development.

"After almost a year of developer feedback and contributions, version 1.0 of the AWS SDK for C++ is now available and recommended for production use," AWS spokesperson Jeff Barr announced in a blog post Tuesday.

According to its GitHub site, "The AWS SDK for C++ provides a modern C++ (version C++ 11 or later) interface for Amazon Web Services (AWS). It is meant to be performant and fully functioning with low- and high-level SDKs, while minimizing dependencies and providing platform portability (Windows, OSX, Linux, and mobile)."

Along with supporting Android and iOS development, it supports CMake, the open source build system generator. In the nuts-and-bolts department, it features customizable memory management so developers can plug in their own solution to fine-tune how memory gets allocated and deallocated.

Its C++ library lets developers easily integrate it with AWS services such as Amazon S3, Amazon Kinesis and Amazon DynamoDB. It will be updated frequently to support the latest AWS API changes. Barr said it will use semantic versioning, so from now on developers can be assured future versions won't break their builds.

Barr also listed the following recent changes to the SDK, based on feedback garnered from the developer preview:

Transfer Manager -- The original TransferClient has evolved into the new and improved TransferManager interface.
Build Process -- The CMake build chain has been improved in order to make it easier to override platform defaults.
Simplified Configuration -- It is now easier to set SDK-wide configuration options at runtime. Encryption – The SDK now includes symmetric cryptography support on all supported platforms.
Fixes -- The 1.0 codebase includes numerous bug fixes and build improvements.

AWS announced in July that the SDK for C++ was available via NuGet, a primary package manager for .NET developers.

Barr said AWS will release more high-level APIs to make C++ development on AWS easier and more secure, and he invited developers to submit feedback on the 1.0 SDK and file issues or submit pull requests to improve it.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.