It is a simple yet efficient architecture for extracting and querying tagged resources based on AWS cloud-native features. The figure above depict the overall architecture discussed in this post. Amazon S3 Update: New Storage Class and General Availability of S3 Select.S3 Select and Glacier Select – Retrieving Subsets of Objects. By using S3 Select to retrieve only the data needed by the application, customers can achieve drastic performance increases – in many cases you can get as much as a 400% improvement. S3 Select enables applications to retrieve only a subset of data from an object by using simple SQL expressions. By doing so, customers can build automation that fits their need, e.g., code that extract, export, and queries tagged resources.įor further details, please read Resource Groups Tagging – Reference By relying on AWS cloud-native features, customers can save time and reduce costs while still being able to do customizations.įor customers unfamiliar with the Resource Tagging API and the S3 Select features, below is a very brief introduction.ĪWS customers can use the Resource Tagging API to programatically access the same resource group operations that had been accessible only from the AWS Management Console by now using the AWS SDKs or the AWS Command Line Interface (CLI). We provide sample code for the architecture discussed that can help customers to customize and/or extend the architecture for their own purpose. In this blog post, we introduce a simple yet efficient AWS architecture for extracting and querying tagged resources based on AWS cloud-native features such as the Resource Tagging API and S3 Select. In addition, automation allows customers to add validation checks to their CI/CD deployment pipelines, for instance, to check whether resources have been properly tagged. For instance, customers can build automation to generate custom CSV files for tagged resources and perhaps use SQL to query those resources. However, customers have asked for guidance on how to build custom automation mechanisms to extract and query tagged resources so that they can extend the built-in functionalities of the Tag Editor. They can use the tag editor to search for resources by resource type, region, or tag, and then manage the tags applied to those resources. Once a tagging strategy is defined and enforced, customers can use the AWS Tag Editor to view and manage tags on their AWS resources, regardless of service or region. Although there are no inherent types of tags, they enable customers to categorize resources by multiple criteria such as purpose, owner and, environment. Each tag is a simple label consisting of a customer-defined key and an optional value that can make it easier to manage, search for, and filter resources. AWS customers can use tags to assign metadata to their AWS resources.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |