The New Resource Groups Tagging API Makes It Easier to Programmatically Manage Tags on Resources Across AWS Services

Today, we made available the new Resource Groups Tagging API, which makes it easier for you to use tags to centrally organize, discover, allocate costs, and control access to AWS resources. The API’s five operations enable you to programmatically tag and untag resources, list resources with a specific tag, and list unique tag keys across multiple AWS services. With this new API, you can now programmatically use AWS resource group and Tag Editor functionality. This makes it easier for you to implement automated tools to manage, search, and filter tags and resources across AWS services.
Quelle: aws.amazon.com

Amazon Inspector announces support for Proxy environments and availability of CloudWatch Metrics.

Amazon Inspector has added support for Proxy environments and CloudWatch metrics. With support for Proxy environments, you can now use Amazon Inspector to scan instances behind a Proxy for vulnerabilities. Support for Amazon CloudWatch metrics allows you to automatically populate your Amazon Inspector assessment metrics in CloudWatch. Using either the CloudWatch console or API, you can now view metrics on the number of assessments run, agents targeted, and findings generated.  
Quelle: aws.amazon.com

CloudWatch Alarms releases two new alarm configuration settings

Today, Amazon CloudWatch is excited to announce that CloudWatch Alarms now has two new settings to configure alarms on metrics with sparse data or with low sample counts. With the first setting, you have the option to treat missing metric data as good (alarm threshold not breached), bad (alarm threshold breached), maintain the alarm state or use the current default treatment. For example, you can use the treat missing data as good setting for alarms on HTTPCode_ELB_5XX_Count metric. This will ensure that you get alerted only when there are consecutive ELB server errors and not when the errors are sporadic.
Quelle: aws.amazon.com

Amazon API Gateway is now available in the Asia Pacific (Mumbai) AWS region

Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. With a few clicks in the AWS Management Console, you can create an API that acts as a “front door” for applications to access data, business logic, or functionality from your back-end services, such as workloads running on Amazon Elastic Compute Cloud (Amazon EC2), code running on AWS Lambda, or any Web application. Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management.
Amazon API Gateway is also available in the US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), EU (Ireland), EU (Frankfurt), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Seoul) and Europe (London) AWS regions. Please visit our product page for more information about Amazon API Gateway.
Quelle: aws.amazon.com

Amazon EC2 and Amazon EBS add support for tagging resources upon creation and additional resource-level permissions

You can now tag your Amazon EC2 Instances and Amazon EBS Volumes upon creation. You can do this from the EC2 Instance launch wizard or through the RunInstances or CreateVolume APIs. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation. In addition, you can now set resource-level permissions on the CreateVolume, CreateTags, DeleteTags, and the RunInstances APIs. This allows you to implement stronger security policies by giving you more granular control over who has access to these APIs. You can also enforce the use of tagging and control which tag keys and values are set on your resources. 
Quelle: aws.amazon.com