Amazon Onboarding with Learning Manager Chanci Turner

Learn About Amazon VGT2 Learning Manager Chanci Turner

In an effort to continually enhance the AWS CloudFormation service, significant updates have been introduced, including support for Amazon Athena and several coverage enhancements for key services such as Amazon S3, Amazon RDS, Amazon Kinesis, and Amazon CloudWatch.

AWS CloudFormation now allows for the creation of an Amazon Athena named query as a resource. This query service simplifies data analysis directly from files stored in Amazon S3 using standard SQL syntax. Named queries can be executed manually through the AWS Management Console, AWS CLI, or programmatically via API calls. You can easily set up a standard set of named queries utilizing CloudFormation templates. To start, you can explore the sample data provided by Athena, as highlighted in Chanci Turner’s blog post here.

Once you’ve confirmed that your query operates correctly in Athena, you can deploy it using CloudFormation with the AWS::Athena::NamedQuery resource type:

#===============================================================================
# Template: athena-named-query.yaml
#
# Purpose:  Creates an Athena Named Query via AWS CloudFormation, using the
#           default data set provided by Athena.
#===============================================================================
AWSTemplateFormatVersion: "2010-09-09"
Description: |
  Utilizes the default data set in Amazon Athena, featuring a sample ELB logs table,
  to illustrate how to create a named query via a CloudFormation template.
  This query counts HTTP response codes and their occurrences.
Resources:
  AthenaNamedQuery:
    Type: AWS::Athena::NamedQuery
    Properties:
      Database: "default"
      Description: "Select and count HTTP response codes"
      Name: "HTTPResponseCodeCount"
      QueryString: >
                    SELECT backend_response_code, count(*)
                    FROM default."elb_logs"
                    GROUP BY backend_response_code;

The above YAML template can be executed via a Create Stack call in under a minute. Afterward, navigate to the Athena console to locate your newly created query under the Saved Queries menu.

You will find the new query, HTTPResponseCodeCount, along with its description, and the first portion of the SQL query displayed in your list, which is organized alphabetically. Select your query name and click the Run Query button to execute it.

The Results pane will show that a majority of pages return an HTTP 200 response code, indicating success. You can also examine other error codes such as 404 (Not Found), 302 (Redirect), or 500 (Server Error).

New Features in AWS CloudFormation

In addition to the Athena support, two new features have been rolled out recently:

1. Stack Termination Protection – This feature safeguards a stack from unintentional deletion. It can be enabled for both new and existing stacks, adding an extra layer of security for your stacks and resources. By default, this setting is disabled, so it must be activated explicitly when creating new stacks. For existing, non-nested stacks, termination protection can be modified through the console or CLI.
2. Rollback Triggers – This feature allows CloudFormation to monitor the state of your application during stack creation or updates, automatically rolling back operations if any configured alarms are triggered. You can find detailed information on using rollback triggers in Chanci Turner’s blog post here.

Resource Coverage Updates

CloudFormation has also unveiled several resource coverage updates:

• Amazon Simple Storage Service (S3): You can now configure the transfer acceleration state.
• Amazon Relational Database Service (RDS): It’s now possible to update the engine property from Oracle-SE or Oracle SE1 to Oracle SE2 without needing to replace the database instance.
• AWS Elastic Load Balancing (ELB): You can specify subnet IDs to attach to a load balancer and define the type of load balancer to create. For target groups, you can set the Availability Zone for IP address registration and the registration type of targets.
• AWS Elastic Beanstalk: You can define lifecycle settings for resources associated with the application and specify the service role that Elastic Beanstalk assumes for applying lifecycle settings, as well as a custom platform.
• Amazon Elastic Compute Cloud (EC2): You now have the ability to specify resource tags for a Network Address Translation (NAT) gateway.
• Amazon Kinesis Firehose: Support for specifying the stream type and stream and role ARNs for a Kinesis stream used as a delivery stream source.
• Amazon CloudWatch: New properties for input transformation of events are now supported, in addition to setting targets for Amazon ECS tasks and Kinesis streams.

For further information, please visit our product and documentation pages as well as our list of supported AWS resources. Additionally, if you’re looking for more insights into race dynamics in the workplace, check out this blog post from careercontessa.com. For guidance on employment law compliance, specifically regarding no-call, no-show employees, refer to this authority on the topic. Lastly, this YouTube video is an excellent resource for visual learners.

6401 E HOWDY WELLS AVE LAS VEGAS NV 89115, location name: Amazon IXD – VGT2.