What's New at AWS: DATA API, Kinesis Data Analytics, S3 Path

DATA API for Amazon Aurora Serverless

How does connecting to a traditional database work? You open a connection, use it to process one or more SQL queries or other statements, and then close the connection. You probably used a client library specific to your operating system, programming language, and database. At some point, you realized that creating connections took a lot of time and took up memory on the database engine.

The DATA API takes care of managing and scaling long-term database connections and returns data in JSON form for easy analysis. All traffic is crypto and occurs through HTTPS.

So what is the DATA API?

ExecuteStatement - execute a single SQL query.
BatchExecuteStatement - execute one SQL query for a data array.
BeginTransaction - start a transaction and return a transaction identifier.
CommitTransaction - complete the transaction and commit the SQL operations that were performed in it.
RollbackTransaction - roll back a transaction.

The only limitation is that each function must complete within a minute and can return up to 1 megabyte of data.

Read more.

- Art Tonoyan arttonoyan , Database Administrator at Provectus

Amazon Kinesis Data Analytics now allows you to assign AWS resource tags to your real-time applications

With the increase in data flow, the need to process and analyze this data in a special way increases. Amazon Kinesis Data Analytics is one of these services that enables you, by writing SQL or Java code (using Apache Flink), to begin collecting data from different sources, as well as process and analyze them in real time. Now, having received a more complete and multidimensional picture of your data, you can easily extract new useful information, as well as quickly respond to the needs of business and customers.

With the growing number of such applications, the need to competently manage them is growing. Amazon recently announced that it’s now possible to add resource tags to your applications in Amazon Kinesis Data Analytics, like other AWS resources. The tag is a key-value pair, where the value is an optional part. Using tags is a simple but effective way to manage AWS resources and organize data. Examples of possible tags:

Environment: Staging
Application: Application name
Project: Project name

Using tags, you can add more context to the application. In the case of Amazon Kinesis Data Analytics applications, tags can be used:
To determine billing for specific Amazon Kinesis Data Analytics applications.
To control access to application resources.
For the purposes defined by the user himself - you can determine the functionality of applications based on the presence of user tags.
You can find more information about tags for Amazon Kinesis Data Analytics applications here.

- Bulat Gaineyev grbulat , Software Engineer at Provectus

Amazon S3 Path Deprecation Plan - The Rest of the Story

In one of the most popular S3 services from Amazon Web Services (AWS), the way to get files by specifying a path-style will soon become obsolete, for example, s3.amazonaws.com/usmanovbf/docs/Bulat_Usmanov_CV.pdf or with a region - s3-us-east-2.amazonaws.com/usmanovbf/docs/Bulat_Usmanov_CV.pdf , where usmanovbf is the bucket, and /docs/Bulat_Usmanov_CV.pdf is the key to the file on this bucket.

Preference will be given to another method - using a virtual host (virtual-hosted style), for example, usmanovbf.s3.amazonaws.com/docs/Bulat_Usmanov_CV.pdf or also with the region - usmanovbf.s3-us-east-2.amazonaws. com / docs / Bulat_Usmanov_CV.pdf

The transition is expected to be done on September 30, 2020. Due to the openness of AWS engineers to the community, all path-style links created up to and including this date will not be deleted. That is, they will remain fully operational, just after this date you can use only the second method - virtual-hosted style.

This change is dictated by two main reasons:
1. A more centralized model, which is accessing files using path-style, limits effective scaling, since all traffic comes to a small set of input points: sub-domains of the third level s3, s3-us-east- 2, s3-us-east-1 and so on. For the same reason, it becomes inconvenient to work with DNS name resolution, security, and reflection of DDOS attacks.
Virtual-hosted style allows you to more flexibly control the data flow due to binding to a separate subdomain-bucket and to a region, for example, usmanovbf and s3-us-east-2 as in the example above.

2. AWS engineers do not stand still, and in order to introduce new functionality and abandon the old, they need to switch to virtual-hosted style. For example, it is planned to abandon the old encryption methods.

You can find more information about migrating to the new method on the official AWS blog.

- Bulat Usmanov usmanovbf , Software Engineer at Provectus

Learn more about Amazon's new services and products at AWS Dev Day Moscow!

#AWSDevDayMoscow is a one-day, free-of-charge conference for Machine Learning Engineers, Data Scientists, DevOps Engineers, Solution Architects, and Software Engineers who are interested or are already working with AWS services.

Let's discuss the hottest topics in the field of cloud technology with like-minded people and the AWS team very soon!

When: June 18
Where: Space "Vesna"
Spartakovsky Lane 2с1, entrance number 7

Registration

Meet me at AWS Dev Day Moscow!