Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Artifact
Config Input A structure that contains the configuration for canary artifacts, including the encryption-at-rest settings for artifacts that the canary uploads to Amazon S3.
- Artifact
Config Output A structure that contains the configuration for canary artifacts, including the encryption-at-rest settings for artifacts that the canary uploads to Amazon S3.
- Base
Screenshot A structure representing a screenshot that is used as a baseline during visual monitoring comparisons made by the canary.
- Browser
Config A structure that specifies the browser type to use for a canary run.
- Canary
This structure contains all information about one canary in your account.
- Canary
Code Input Use this structure to input your script code for the canary. This structure contains the Lambda handler with the location where the canary should start running the script. If the script is stored in an Amazon S3 bucket, the bucket name, key, and version are also included. If the script was passed into the canary directly, the script code is contained in the value of
Zipfile.If you are uploading your canary scripts with an Amazon S3 bucket, your zip file should include your script in a certain folder structure.
-
For Node.js canaries, the folder structure must be
nodejs/node_modules/myCanaryFilename.jsFor more information, see Packaging your Node.js canary files -
For Python canaries, the folder structure must be
python/myCanaryFilename.pyorpython/myFolder/myCanaryFilename.pyFor more information, see Packaging your Python canary files
-
- Canary
Code Output This structure contains information about the canary's Lambda handler and where its code is stored by CloudWatch Synthetics.
- Canary
DryRun Config Output Returns the dry run configurations set for a canary.
- Canary
Last Run This structure contains information about the most recent run of a single canary.
- Canary
Run This structure contains the details about one run of one canary.
- Canary
RunConfig Input A structure that contains input information for a canary run.
- Canary
RunConfig Output A structure that contains information about a canary run.
- Canary
RunStatus This structure contains the status information about a canary run.
- Canary
RunTimeline This structure contains the start and end times of a single canary run.
- Canary
Schedule Input This structure specifies how often a canary is to make runs and the date and time when it should stop making runs.
- Canary
Schedule Output How long, in seconds, for the canary to continue making regular runs according to the schedule in the
Expressionvalue.- Canary
Status A structure that contains the current state of the canary.
- Canary
Timeline This structure contains information about when the canary was created and modified.
- Dependency
A structure that contains information about a dependency for a canary.
- DryRun
Config Output Returns the dry run configurations set for a canary.
- Engine
Config A structure of engine configurations for the canary, one for each browser type that the canary is configured to run on.
- Group
This structure contains information about one group.
- Group
Summary A structure containing some information about a group.
- Retry
Config Input This structure contains information about the canary's retry configuration.
The default account level concurrent execution limit from Lambda is 1000. When you have more than 1000 canaries, it's possible there are more than 1000 Lambda invocations due to retries and the console might hang. For more information on the Lambda execution limit, see Understanding Lambda function scaling.
For canary with
MaxRetries = 2, you need to set theCanaryRunConfigInput.TimeoutInSecondsto less than 600 seconds to avoid validation errors.- Retry
Config Output This structure contains information about the canary's retry configuration.
- Runtime
Version This structure contains information about one canary runtime version. For more information about runtime versions, see Canary Runtime Versions.
- S3Encryption
Config A structure that contains the configuration of encryption-at-rest settings for canary artifacts that the canary uploads to Amazon S3.
For more information, see Encrypting canary artifacts
- Visual
Reference Input An object that specifies what screenshots to use as a baseline for visual monitoring by this canary. It can optionally also specify parts of the screenshots to ignore during the visual monitoring comparison.
Visual monitoring is supported only on canaries running the syn-puppeteer-node-3.2 runtime or later. For more information, see Visual monitoring and Visual monitoring blueprint
- Visual
Reference Output If this canary performs visual monitoring by comparing screenshots, this structure contains the ID of the canary run that is used as the baseline for screenshots, and the coordinates of any parts of those screenshots that are ignored during visual monitoring comparison.
Visual monitoring is supported only on canaries running the syn-puppeteer-node-3.2 runtime or later.
- VpcConfig
Input If this canary is to test an endpoint in a VPC, this structure contains information about the subnets and security groups of the VPC endpoint. For more information, see Running a Canary in a VPC.
- VpcConfig
Output If this canary is to test an endpoint in a VPC, this structure contains information about the subnets and security groups of the VPC endpoint. For more information, see Running a Canary in a VPC.
Enums§
- Browser
Type - When writing a match expression against
BrowserType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Canary
RunState - When writing a match expression against
CanaryRunState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Canary
RunState Reason Code - When writing a match expression against
CanaryRunStateReasonCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Canary
RunTest Result - When writing a match expression against
CanaryRunTestResult, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Canary
State - When writing a match expression against
CanaryState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Canary
State Reason Code - When writing a match expression against
CanaryStateReasonCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dependency
Type - When writing a match expression against
DependencyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Encryption
Mode - When writing a match expression against
EncryptionMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Provisioned
Resource Cleanup Setting - When writing a match expression against
ProvisionedResourceCleanupSetting, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resource
ToTag - When writing a match expression against
ResourceToTag, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - RunType
- When writing a match expression against
RunType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.