Name: amazon-guardduty-alexa-sample
Owner: AWS Samples
Description: Alexa GuardDuty Sample Skill
Created: 2018-02-14 04:51:26.0
Updated: 2018-05-08 14:40:27.0
Pushed: 2018-05-03 18:26:18.0
Size: 3405
Language: Python
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Deploy a sample custom Alexa skill and use an Alexa-enabled device, such as Amazon Echo to obtain information about GuardDuty findings across your AWS accounts and regions. This will enable you to quickly understand current GuardDuty finding statistics and details through the Alexa voice interface. The information provided by this sample skill is intended to give you a broad overview of GuardDuty finding statistics, severities and descriptions. With this information, you may wish to log into the GuardDuty console or another analysis tool to drill further into the findings data.
Note: A basic understanding of Alexa Custom Skills is helpful for deploying the sample skill described in this blog post. If you are not already familiar with Alexa custom skill concepts and terminology, you may want to review the documentation resources.
Solution overview The solution diagram below is followed by a description of the flow of events. The CloudFormation template creates the Lambda function for the sample Alexa skill.
Here is how the solution works, as shown in the preceding numbered diagram:
Prerequisites In order to complete the steps in this blog post, make sure you have the following prerequisites:
MAXRESP = os.environ['MAXRESP']
Max number of findings to return. Although 50 can be returned without paginating, keeping this below 15 is a good idea to avoid Alexa size limit and general sanity preservation.
FLASHREGIONS = os.environ['FLASHREGIONS']
Comma separated list of region codes with NO spaces to include in flash briefing stats. Make sure GuardDuty is enabled in regions declared
Note: Since you are not publishing this skill, you do not need to complete the Launch section of the configuration. The skill will remain in the Development status and will only be available for Alexa devices linked to the Amazon developer account used to create the skill. Anyone with physical access to the linked Alexa-enabled device can use the custom skill. As a best practice, we recommend that you delete the Lambda trigger created by the CloudFormation template and add a new one with Skill ID verification enabled. Learn more. You can also deploy this sample skill using Alexa for Business. For more info, check out Alexa for Business Deployment
This library is licensed under the Apache 2.0 License.