AWS continues to strengthen its services for its clients. Here’s what they came up with this month:
AWS has also announced that is now supporting large-scale OLAP deployments, including BW/4HANA for its EC2 X1 clusters. EC2 can support up to 7 nodes or 14 Tb of RAM. AWS’s new certification allows it to consolidate larger scale-out deployments into fewer but larger instances. This makes them more efficient and less costly to run and manage.
It doesn’t stop there—AWS has plans to make X1 instances available for other sizes too. Currently, AWS is in the process of testing clusters at 50 Tb.
AWS is happy to announce that it has released the AWS SDK for C++ version 1.0 for production use.
This version comes with several useful features that came from developer preview feedback of the SDK:
- Semantic versioning– From the very firist production version, further upgrades on 1.x won’t break your build.
- Transfer Manager– new interface based on TransferClient
- Build Process— The CMAke build chain has evolved to make it easier to override platform defaults
- Simplified Configuration– Easier to set SDK-wide configurations at runtime
- Encryption– Symmetric cryptography for all supported platforms
- NuGet– You can obtain this SDK through NuGet
- Fixes– version 1.0 has several bug fixes and build improvements
AWS has improved Elastic Beanstalk to support three new features: ASP.NET Core, Muti-App .NET, Application Load Balancer, and Nginx Proxy Server with Tomcat.
Firstly, you may now deploy applications using ASP.NET Core on Elastic Beanstalk using the AWS Management Console, the Elastic Beanstalk CLI, and the AWS Toolkit for Visual Studio.
Secondly, when building environments with Elastic Beanstalk, you may now choose between the new Application Load Balancer or Classic Load Balancer. The Application Load Balancer is useful for deploying applications that use Websocket protocol or HTTP/2.
Finally, you can run Tomcat applications with a Nignx proxy server in an AWS Elastic Beanstalk environment. To do this, you need to add a config file to .ebextensions in the application source bundle which you upload to Elastic Beanstalk.
AWS has also improved CloudWatch Logs with the following enhancements:
- Better log data formatting
- Simplified access to long log files
- Simpler searches through log groups
- Easier collaboration on log files
- Improved searches within time frame– you may refine searches to a custom range or time frame.
You can update to your application to use this endpoint, which provides you with two important features:
- Load Balancing — Connecting to the endpoint lets Aurora load-balance connections among the replicas in the DB cluster. By spreading the read workload, it improves performance and allows for better resource management.
- Highly Available — You may now install Aurora replicas across different Availability Zones and connect them to the endpoint. This way, your replicas can still send read information with few problems, even if one Zone should fail.
Finally, AWS Cost Explorer now lets you choose Usage Type from the Filtering Menu. This means you can zoom in and filter on as-billed units, such as each hour on EC2 or each Gig of data transfer.
On the other hand, if you require a summary of expenses, you can also zoom out by filtering per Usage Type Group. This will show you how much you spent on RDS, S3 API requests, and on EBS storage.
Join us next month for more updates on AWS!