The number of instantiations of the specified task definition to place and keep running in your service.
This is required if schedulingStrategy is REPLICA or isn't specified. If schedulingStrategy is DAEMON then this isn't required.
The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of 0 is used.
If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in the task definition health check parameters. For more information, see Health check.
If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.
", "DeploymentConfiguration$maximumPercent": "If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.
If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.
If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.
For services that do not use a load balancer, the following should be noted:
A service is considered healthy if all essential containers within the tasks in the service pass their health checks.
If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.
If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.
For services that do use a load balancer, the following should be noted:
If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.
If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.
If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.
For services that do not use a load balancer, the following should be noted:
A service is considered healthy if all essential containers within the tasks in the service pass their health checks.
If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.
If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.
For services that do use a load balancer, the following should be noted:
If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.
If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.
The default value for a replica service for minimumHealthyPercent is 100%. The default minimumHealthyPercent value for a service using the DAEMON service schedule is 0% for the CLI, the Amazon Web Services SDKs, and the APIs and 50% for the Amazon Web Services Management Console.
The minimum number of healthy tasks during a deployment is the desiredCount multiplied by the minimumHealthyPercent/100, rounded up to the nearest integer value.
If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
The maximum number of account setting results returned by DescribeCapacityProviders in paginated output. When this parameter is used, DescribeCapacityProviders only returns maxResults results in a single page along with a nextToken response element. The remaining results of the initial request can be seen by sending another DescribeCapacityProviders request with the returned nextToken value. This value can be between 1 and 10. If this parameter is not used, then DescribeCapacityProviders returns up to 10 results and a nextToken value if applicable.
The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you do not specify a transit encryption port, it will use the port selection strategy that the Amazon EFS mount helper uses. For more information, see EFS mount helper in the Amazon Elastic File System User Guide.
", "HealthCheck$interval": "The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.
", @@ -2334,7 +2334,7 @@ "RunTaskRequest$platformVersion": "The platform version the task uses. A platform version is only specified for tasks hosted on Fargate. If one isn't specified, the LATEST platform version is used. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide.
The reference ID to use for the task. The reference ID can have a maximum length of 1024 characters.
", "RunTaskRequest$startedBy": "An optional tag specified when a task is started. For example, if you automatically trigger a task to run a batch process job, you could apply a unique identifier for that job to your task with the startedBy parameter. You can then identify which tasks belong to that job by filtering the results of a ListTasks call with the startedBy value. Up to 128 letters (uppercase and lowercase), numbers, hyphens (-), and underscores (_) are allowed.
If a task is started by an Amazon ECS service, then the startedBy parameter contains the deployment ID of the service that starts it.
The family and revision (family:revision) or full ARN of the task definition to run. If a revision isn't specified, the latest ACTIVE revision is used.
When you create a policy for run-task, you can set the resource to be the latest task definition revision, or a specific revision.
The full ARN value must match the value that you specified as the Resource of the principal's permissions policy.
When you specify the policy resource as the latest task definition version (by setting the Resource in the policy to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName), then set this value to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName.
When you specify the policy resource as a specific task definition version (by setting the Resource in the policy to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1 or arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*), then set this value to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1.
For more information, see Policy Resources for Amazon ECS in the Amazon Elastic Container Service developer Guide.
", + "RunTaskRequest$taskDefinition": "The family and revision (family:revision) or full ARN of the task definition to run. If a revision isn't specified, the latest ACTIVE revision is used.
The full ARN value must match the value that you specified as the Resource of the principal's permissions policy.
When you specify a task definition, you must either specify a specific revision, or all revisions in the ARN.
To specify a specific revision, include the revision number in the ARN. For example, to specify revision 2, use arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:2.
To specify all revisions, use the wildcard (*) in the ARN. For example, to specify all revisions, use arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*.
For more information, see Policy Resources for Amazon ECS in the Amazon Elastic Container Service Developer Guide.
", "RunTaskRequest$clientToken": "An identifier that you provide to ensure the idempotency of the request. It must be unique and is case sensitive. Up to 64 characters are allowed. The valid characters are characters in the range of 33-126, inclusive. For more information, see Ensuring idempotency.
", "Secret$name": "The name of the secret.
", "Secret$valueFrom": "The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.
For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide.
If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
The resource ARN of the parent resource extracted from the request.
", - "TableOptimizerConfiguration$roleArn": "A role passed by the caller which gives the service permission to update the resources associated with the optimizer on the caller's behalf.
" + "TableOptimizerConfiguration$roleArn": "A role passed by the caller which gives the service permission to update the resources associated with the optimizer on the caller's behalf.
", + "ViewDefinition$Definer": "The definer of a view in SQL.
", + "ViewSubObjectsList$member": null } }, "AthenaConnectorSource": { @@ -813,6 +815,8 @@ "GetConnectionsRequest$HidePassword": "Allows you to retrieve the connection metadata without returning the password. For instance, the Glue console uses this flag to retrieve the connection, and does not display the password. Set this parameter when the caller might not have permission to use the KMS key to decrypt the password, but it does have permission to access the rest of the connection properties.
", "GetUnfilteredPartitionMetadataResponse$IsRegisteredWithLakeFormation": "A Boolean value that indicates whether the partition location is registered with Lake Formation.
", "GetUnfilteredTableMetadataResponse$IsRegisteredWithLakeFormation": "A Boolean value that indicates whether the partition location is registered with Lake Formation.
", + "GetUnfilteredTableMetadataResponse$IsMultiDialectView": "Specifies whether the view supports the SQL dialects of one or more different query engines and can therefore be read by those engines.
", + "GetUnfilteredTableMetadataResponse$IsProtected": "A flag that instructs the engine not to push user-provided operations into the logical plan of the view during query planning. However, if set this flag does not guarantee that the engine will comply. Refer to the engine's documentation to understand the guarantees provided, if any.
", "StorageDescriptor$Compressed": " True if the data in the table is compressed, or False if not.
True if the table data is stored in subdirectories, or False if not.
Indicates whether the table has been registered with Lake Formation.
", @@ -6257,10 +6261,13 @@ "InvalidInputException$FromFederationSource": "Indicates whether or not the exception relates to a federated source.
", "LakeFormationConfiguration$UseLakeFormationCredentials": "Specifies whether to use Lake Formation credentials for the crawler instead of the IAM role credentials.
", "MongoDBTarget$ScanAll": "Indicates whether to scan all the records, or to sample rows from the table. Scanning all the records can take a long time when the table is not a high throughput table.
A value of true means to scan all records, while a value of false means to sample the records. If no value is specified, the value defaults to true.
Specifies whether the view supports the SQL dialects of one or more different query engines and can therefore be read by those engines.
", "TableOptimizerConfiguration$enabled": "Whether table optimization is enabled.
", "UpdateCsvClassifierRequest$DisableValueTrimming": "Specifies not to trim values before identifying the type of column values. The default value is true.
", "UpdateCsvClassifierRequest$AllowSingleColumn": "Enables the processing of files that contain only one column.
", - "UpdateCsvClassifierRequest$CustomDatatypeConfigured": "Specifies the configuration of custom datatypes.
" + "UpdateCsvClassifierRequest$CustomDatatypeConfigured": "Specifies the configuration of custom datatypes.
", + "ViewDefinition$IsProtected": "You can set this flag as true to instruct the engine not to push user-provided operations into the logical plan of the view during query planning. However, setting this flag does not guarantee that the engine will comply. Refer to the engine's documentation to understand the guarantees provided, if any.
", + "ViewRepresentation$IsStale": "Dialects marked as stale are no longer valid and must be updated before they can be queried in their respective query engines.
" } }, "NullableDouble": { @@ -9172,16 +9179,42 @@ "DeleteSchemaVersionsInput$Versions": "A version range may be supplied which may be of the format:
a single version number, 5
a range, 5-8 : deletes versions 5, 6, 7, 8
A structure containing details for representations.
", + "refs": { + "Table$ViewDefinition": "A structure that contains all the information that defines the view, including the dialect or dialects for the view, and the query.
" + } + }, "ViewDialect": { "base": null, "refs": { - "SupportedDialect$Dialect": "The dialect of the query engine.
" + "SupportedDialect$Dialect": "The dialect of the query engine.
", + "ViewRepresentation$Dialect": "The dialect of the query engine.
" } }, "ViewDialectVersionString": { "base": null, "refs": { - "SupportedDialect$DialectVersion": "The version of the dialect of the query engine. For example, 3.0.0.
" + "SupportedDialect$DialectVersion": "The version of the dialect of the query engine. For example, 3.0.0.
", + "ViewRepresentation$DialectVersion": "The version of the dialect of the query engine. For example, 3.0.0.
" + } + }, + "ViewRepresentation": { + "base": "A structure that contains the dialect of the view, and the query that defines the view.
", + "refs": { + "ViewRepresentationList$member": null + } + }, + "ViewRepresentationList": { + "base": null, + "refs": { + "ViewDefinition$Representations": "A list of representations.
" + } + }, + "ViewSubObjectsList": { + "base": null, + "refs": { + "ViewDefinition$SubObjects": "A list of table Amazon Resource Names (ARNs).
" } }, "ViewTextString": { @@ -9190,7 +9223,9 @@ "Table$ViewOriginalText": "Included for Apache Hive compatibility. Not used in the normal course of Glue operations. If the table is a VIRTUAL_VIEW, certain Athena configuration encoded in base64.
Included for Apache Hive compatibility. Not used in the normal course of Glue operations.
", "TableInput$ViewOriginalText": "Included for Apache Hive compatibility. Not used in the normal course of Glue operations. If the table is a VIRTUAL_VIEW, certain Athena configuration encoded in base64.
Included for Apache Hive compatibility. Not used in the normal course of Glue operations.
" + "TableInput$ViewExpandedText": "Included for Apache Hive compatibility. Not used in the normal course of Glue operations.
", + "ViewRepresentation$ViewOriginalText": "The SELECT query provided by the customer during CREATE VIEW DDL. This SQL is not used during a query on a view (ViewExpandedText is used instead). ViewOriginalText is used for cases like SHOW CREATE VIEW where users want to see the original DDL command that created the view.
The expanded SQL for the view. This SQL is used by engines while processing a query on a view. Engines may perform operations during view creation to transform ViewOriginalText to ViewExpandedText. For example:
Fully qualify identifiers: SELECT * from table1 → SELECT * from db1.table1
Introduction
The Amazon IVS Chat control-plane API enables you to create and manage Amazon IVS Chat resources. You also need to integrate with the Amazon IVS Chat Messaging API, to enable users to interact with chat rooms in real time.
The API is an AWS regional service. For a list of supported regions and Amazon IVS Chat HTTPS service endpoints, see the Amazon IVS Chat information on the Amazon IVS page in the AWS General Reference.
Notes on terminology:
You create service applications using the Amazon IVS Chat API. We refer to these as applications.
You create front-end client applications (browser and Android/iOS apps) using the Amazon IVS Chat Messaging API. We refer to these as clients.
Resources
The following resources are part of Amazon IVS Chat:
LoggingConfiguration — A configuration that allows customers to store and record sent messages in a chat room. See the Logging Configuration endpoints for more information.
Room — The central Amazon IVS Chat resource through which clients connect to and exchange chat messages. See the Room endpoints for more information.
Tagging
A tag is a metadata label that you assign to an AWS resource. A tag comprises a key and a value, both set by you. For example, you might set a tag as topic:nature to label a particular video category. See Tagging AWS Resources for more information, including restrictions that apply to tags and \"Tag naming limits and requirements\"; Amazon IVS Chat has no service-specific constraints beyond what is documented there.
Tags can help you identify and organize your AWS resources. For example, you can use the same tag for different resources to indicate that they are related. You can also use tags to manage access (see Access Tags).
The Amazon IVS Chat API has these tag-related endpoints: TagResource, UntagResource, and ListTagsForResource. The following resource supports tagging: Room.
At most 50 tags can be applied to a resource.
API Access Security
Your Amazon IVS Chat applications (service applications and clients) must be authenticated and authorized to access Amazon IVS Chat resources. Note the differences between these concepts:
Authentication is about verifying identity. Requests to the Amazon IVS Chat API must be signed to verify your identity.
Authorization is about granting permissions. Your IAM roles need to have permissions for Amazon IVS Chat API requests.
Users (viewers) connect to a room using secure access tokens that you create using the CreateChatToken endpoint through the AWS SDK. You call CreateChatToken for every user’s chat session, passing identity and authorization information about the user.
Signing API Requests
HTTP API requests must be signed with an AWS SigV4 signature using your AWS security credentials. The AWS Command Line Interface (CLI) and the AWS SDKs take care of signing the underlying API calls for you. However, if your application calls the Amazon IVS Chat HTTP API directly, it’s your responsibility to sign the requests.
You generate a signature using valid AWS credentials for an IAM role that has permission to perform the requested action. For example, DeleteMessage requests must be made using an IAM role that has the ivschat:DeleteMessage permission.
For more information:
Authentication and generating signatures — See Authenticating Requests (Amazon Web Services Signature Version 4) in the Amazon Web Services General Reference.
Managing Amazon IVS permissions — See Identity and Access Management on the Security page of the Amazon IVS User Guide.
Amazon Resource Names (ARNs)
ARNs uniquely identify AWS resources. An ARN is required when you need to specify a resource unambiguously across all of AWS, such as in IAM policies and API calls. For more information, see Amazon Resource Names in the AWS General Reference.
Messaging Endpoints
DeleteMessage — Sends an event to a specific room which directs clients to delete a specific message; that is, unrender it from view and delete it from the client’s chat history. This event’s EventName is aws:DELETE_MESSAGE. This replicates the DeleteMessage WebSocket operation in the Amazon IVS Chat Messaging API.
DisconnectUser — Disconnects all connections using a specified user ID from a room. This replicates the DisconnectUser WebSocket operation in the Amazon IVS Chat Messaging API.
SendEvent — Sends an event to a room. Use this within your application’s business logic to send events to clients of a room; e.g., to notify clients to change the way the chat UI is rendered.
Chat Token Endpoint
CreateChatToken — Creates an encrypted token that is used by a chat participant to establish an individual WebSocket chat connection to a room. When the token is used to connect to chat, the connection is valid for the session duration specified in the request. The token becomes invalid at the token-expiration timestamp included in the response.
Room Endpoints
CreateRoom — Creates a room that allows clients to connect and pass messages.
DeleteRoom — Deletes the specified room.
GetRoom — Gets the specified room.
ListRooms — Gets summary information about all your rooms in the AWS region where the API request is processed.
UpdateRoom — Updates a room’s configuration.
Logging Configuration Endpoints
CreateLoggingConfiguration — Creates a logging configuration that allows clients to store and record sent messages.
DeleteLoggingConfiguration — Deletes the specified logging configuration.
GetLoggingConfiguration — Gets the specified logging configuration.
ListLoggingConfigurations — Gets summary information about all your logging configurations in the AWS region where the API request is processed.
UpdateLoggingConfiguration — Updates a specified logging configuration.
Tags Endpoints
ListTagsForResource — Gets information about AWS tags for the specified ARN.
TagResource — Adds or updates tags for the AWS resource with the specified ARN.
UntagResource — Removes tags from the resource with the specified ARN.
All the above are HTTP operations. There is a separate messaging API for managing Chat resources; see the Amazon IVS Chat Messaging API Reference.
", + "service": "Introduction
The Amazon IVS Chat control-plane API enables you to create and manage Amazon IVS Chat resources. You also need to integrate with the Amazon IVS Chat Messaging API, to enable users to interact with chat rooms in real time.
The API is an AWS regional service. For a list of supported regions and Amazon IVS Chat HTTPS service endpoints, see the Amazon IVS Chat information on the Amazon IVS page in the AWS General Reference.
Notes on terminology:
You create service applications using the Amazon IVS Chat API. We refer to these as applications.
You create front-end client applications (browser and Android/iOS apps) using the Amazon IVS Chat Messaging API. We refer to these as clients.
Key Concepts
LoggingConfiguration — A configuration that allows customers to store and record sent messages in a chat room.
Room — The central Amazon IVS Chat resource through which clients connect to and exchange chat messages.
Tagging
A tag is a metadata label that you assign to an AWS resource. A tag comprises a key and a value, both set by you. For example, you might set a tag as topic:nature to label a particular video category. See Tagging AWS Resources for more information, including restrictions that apply to tags and \"Tag naming limits and requirements\"; Amazon IVS Chat has no service-specific constraints beyond what is documented there.
Tags can help you identify and organize your AWS resources. For example, you can use the same tag for different resources to indicate that they are related. You can also use tags to manage access (see Access Tags).
The Amazon IVS Chat API has these tag-related endpoints: TagResource, UntagResource, and ListTagsForResource. The following resource supports tagging: Room.
At most 50 tags can be applied to a resource.
API Access Security
Your Amazon IVS Chat applications (service applications and clients) must be authenticated and authorized to access Amazon IVS Chat resources. Note the differences between these concepts:
Authentication is about verifying identity. Requests to the Amazon IVS Chat API must be signed to verify your identity.
Authorization is about granting permissions. Your IAM roles need to have permissions for Amazon IVS Chat API requests.
Users (viewers) connect to a room using secure access tokens that you create using the CreateChatToken endpoint through the AWS SDK. You call CreateChatToken for every user’s chat session, passing identity and authorization information about the user.
Signing API Requests
HTTP API requests must be signed with an AWS SigV4 signature using your AWS security credentials. The AWS Command Line Interface (CLI) and the AWS SDKs take care of signing the underlying API calls for you. However, if your application calls the Amazon IVS Chat HTTP API directly, it’s your responsibility to sign the requests.
You generate a signature using valid AWS credentials for an IAM role that has permission to perform the requested action. For example, DeleteMessage requests must be made using an IAM role that has the ivschat:DeleteMessage permission.
For more information:
Authentication and generating signatures — See Authenticating Requests (Amazon Web Services Signature Version 4) in the Amazon Web Services General Reference.
Managing Amazon IVS permissions — See Identity and Access Management on the Security page of the Amazon IVS User Guide.
Amazon Resource Names (ARNs)
ARNs uniquely identify AWS resources. An ARN is required when you need to specify a resource unambiguously across all of AWS, such as in IAM policies and API calls. For more information, see Amazon Resource Names in the AWS General Reference.
Messaging Endpoints
DeleteMessage — Sends an event to a specific room which directs clients to delete a specific message; that is, unrender it from view and delete it from the client’s chat history. This event’s EventName is aws:DELETE_MESSAGE. This replicates the DeleteMessage WebSocket operation in the Amazon IVS Chat Messaging API.
DisconnectUser — Disconnects all connections using a specified user ID from a room. This replicates the DisconnectUser WebSocket operation in the Amazon IVS Chat Messaging API.
SendEvent — Sends an event to a room. Use this within your application’s business logic to send events to clients of a room; e.g., to notify clients to change the way the chat UI is rendered.
Chat Token Endpoint
CreateChatToken — Creates an encrypted token that is used by a chat participant to establish an individual WebSocket chat connection to a room. When the token is used to connect to chat, the connection is valid for the session duration specified in the request. The token becomes invalid at the token-expiration timestamp included in the response.
Room Endpoints
CreateRoom — Creates a room that allows clients to connect and pass messages.
DeleteRoom — Deletes the specified room.
GetRoom — Gets the specified room.
ListRooms — Gets summary information about all your rooms in the AWS region where the API request is processed.
UpdateRoom — Updates a room’s configuration.
Logging Configuration Endpoints
CreateLoggingConfiguration — Creates a logging configuration that allows clients to store and record sent messages.
DeleteLoggingConfiguration — Deletes the specified logging configuration.
GetLoggingConfiguration — Gets the specified logging configuration.
ListLoggingConfigurations — Gets summary information about all your logging configurations in the AWS region where the API request is processed.
UpdateLoggingConfiguration — Updates a specified logging configuration.
Tags Endpoints
ListTagsForResource — Gets information about AWS tags for the specified ARN.
TagResource — Adds or updates tags for the AWS resource with the specified ARN.
UntagResource — Removes tags from the resource with the specified ARN.
All the above are HTTP operations. There is a separate messaging API for managing Chat resources; see the Amazon IVS Chat Messaging API Reference.
", "operations": { "CreateChatToken": "Creates an encrypted token that is used by a chat participant to establish an individual WebSocket chat connection to a room. When the token is used to connect to chat, the connection is valid for the session duration specified in the request. The token becomes invalid at the token-expiration timestamp included in the response.
Use the capabilities field to permit an end user to send messages or moderate a room.
The attributes field securely attaches structured data to the chat session; the data is included within each message sent by the end user and received by other participants in the room. Common use cases for attributes include passing end-user profile data like an icon, display name, colors, badges, and other display features.
Encryption keys are owned by Amazon IVS Chat and never used directly by your application.
", "CreateLoggingConfiguration": "Creates a logging configuration that allows clients to store and record sent messages.
", diff --git a/models/apis/rolesanywhere/2018-05-10/api-2.json b/models/apis/rolesanywhere/2018-05-10/api-2.json index b96623c3bc7..07ab8a533da 100644 --- a/models/apis/rolesanywhere/2018-05-10/api-2.json +++ b/models/apis/rolesanywhere/2018-05-10/api-2.json @@ -822,7 +822,7 @@ "RoleArnList":{ "type":"list", "member":{"shape":"RoleArn"}, - "max":50, + "max":250, "min":0 }, "ScalarCrlRequest":{ diff --git a/models/apis/rolesanywhere/2018-05-10/docs-2.json b/models/apis/rolesanywhere/2018-05-10/docs-2.json index c4820e70908..3f11e0446d8 100644 --- a/models/apis/rolesanywhere/2018-05-10/docs-2.json +++ b/models/apis/rolesanywhere/2018-05-10/docs-2.json @@ -79,7 +79,7 @@ "CreateProfileRequestDurationSecondsInteger": { "base": null, "refs": { - "CreateProfileRequest$durationSeconds": " Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details.
Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details. In requests, if this value is not provided, the default value will be 3600.
The number of resources in the paginated list.
", - "ProfileDetail$durationSeconds": " Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details.
Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details. In requests, if this value is not provided, the default value will be 3600.
Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details.
Used to determine how long sessions vended using this profile are valid for. See the Expiration section of the CreateSession API documentation page for more details. In requests, if this value is not provided, the default value will be 3600.
Security Hub provides you with a comprehensive view of the security state of your Amazon Web Services environment and resources. It also provides you with the readiness status of your environment based on controls from supported security standards. Security Hub collects security data from Amazon Web Services accounts, services, and integrated third-party products and helps you analyze security trends in your environment to identify the highest priority security issues. For more information about Security Hub, see the Security Hub User Guide .
When you use operations in the Security Hub API, the requests are executed only in the Amazon Web Services Region that is currently active or in the specific Amazon Web Services Region that you specify in your request. Any configuration or settings change that results from the operation is applied only to that Region. To make the same change in other Regions, run the same command for each Region in which you want to apply the change.
For example, if your Region is set to us-west-2, when you use CreateMembers to add a member account to Security Hub, the association of the member account with the administrator account is created only in the us-west-2 Region. Security Hub must be enabled for the member account in the same Region that the invitation was sent from.
The following throttling limits apply to using Security Hub API operations.
BatchEnableStandards - RateLimit of 1 request per second. BurstLimit of 1 request per second.
GetFindings - RateLimit of 3 requests per second. BurstLimit of 6 requests per second.
BatchImportFindings - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
BatchUpdateFindings - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
UpdateStandardsControl - RateLimit of 1 request per second. BurstLimit of 5 requests per second.
All other operations - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
Security Hub provides you with a comprehensive view of your security state in Amazon Web Services and helps you assess your Amazon Web Services environment against security industry standards and best practices.
Security Hub collects security data across Amazon Web Services accounts, Amazon Web Services, and supported third-party products and helps you analyze your security trends and identify the highest priority security issues.
To help you manage the security state of your organization, Security Hub supports multiple security standards. These include the Amazon Web Services Foundational Security Best Practices (FSBP) standard developed by Amazon Web Services, and external compliance frameworks such as the Center for Internet Security (CIS), the Payment Card Industry Data Security Standard (PCI DSS), and the National Institute of Standards and Technology (NIST). Each standard includes several security controls, each of which represents a security best practice. Security Hub runs checks against security controls and generates control findings to help you assess your compliance against security best practices.
In addition to generating control findings, Security Hub also receives findings from other Amazon Web Services, such as Amazon GuardDuty and Amazon Inspector, and supported third-party products. This gives you a single pane of glass into a variety of security-related issues. You can also send Security Hub findings to other Amazon Web Services and supported third-party products.
Security Hub offers automation features that help you triage and remediate security issues. For example, you can use automation rules to automatically update critical findings when a security check fails. You can also leverage the integration with Amazon EventBridge to trigger automatic responses to specific findings.
This guide, the Security Hub API Reference, provides information about the Security Hub API. This includes supported resources, HTTP methods, parameters, and schemas. If you're new to Security Hub, you might find it helpful to also review the Security Hub User Guide . The user guide explains key concepts and provides procedures that demonstrate how to use Security Hub features. It also provides information about topics such as integrating Security Hub with other Amazon Web Services.
In addition to interacting with Security Hub by making calls to the Security Hub API, you can use a current version of an Amazon Web Services command line tool or SDK. Amazon Web Services provides tools and SDKs that consist of libraries and sample code for various languages and platforms, such as PowerShell, Java, Go, Python, C++, and .NET. These tools and SDKs provide convenient, programmatic access to Security Hub and other Amazon Web Services . They also handle tasks such as signing requests, managing errors, and retrying requests automatically. For information about installing and using the Amazon Web Services tools and SDKs, see Tools to Build on Amazon Web Services.
With the exception of operations that are related to central configuration, Security Hub API requests are executed only in the Amazon Web Services Region that is currently active or in the specific Amazon Web Services Region that you specify in your request. Any configuration or settings change that results from the operation is applied only to that Region. To make the same change in other Regions, call the same API operation in each Region in which you want to apply the change. When you use central configuration, API requests for enabling Security Hub, standards, and controls are executed in the home Region and all linked Regions. For a list of central configuration operations, see the Central configuration terms and concepts section of the Security Hub User Guide.
The following throttling limits apply to Security Hub API operations.
BatchEnableStandards - RateLimit of 1 request per second. BurstLimit of 1 request per second.
GetFindings - RateLimit of 3 requests per second. BurstLimit of 6 requests per second.
BatchImportFindings - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
BatchUpdateFindings - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
UpdateStandardsControl - RateLimit of 1 request per second. BurstLimit of 5 requests per second.
All other operations - RateLimit of 10 requests per second. BurstLimit of 30 requests per second.
Accepts the invitation to be a member account and be monitored by the Security Hub administrator account that the invitation was sent from.
This operation is only used by member accounts that are not added through Organizations.
When the member account accepts the invitation, permission is granted to the administrator account to view findings generated in the member account.
", "AcceptInvitation": "This method is deprecated. Instead, use AcceptAdministratorInvitation.
The Security Hub console continues to use AcceptInvitation. It will eventually change to use AcceptAdministratorInvitation. Any IAM policies that specifically control access to this function must continue to use AcceptInvitation. You should also add AcceptAdministratorInvitation to your policies to ensure that the correct permissions are in place after the console begins to use AcceptAdministratorInvitation.
Accepts the invitation to be a member account and be monitored by the Security Hub administrator account that the invitation was sent from.
This operation is only used by member accounts that are not added through Organizations.
When the member account accepts the invitation, permission is granted to the administrator account to view findings generated in the member account.
", @@ -3927,7 +3927,7 @@ "refs": { "CreateInsightRequest$Filters": "One or more attributes used to filter the findings included in the insight. The insight only includes findings that match the criteria defined in the filters.
", "GetFindingsRequest$Filters": "The finding attributes used to define a condition to filter the returned findings.
You can filter by up to 10 finding attributes. For each attribute, you can provide up to 20 filter values.
Note that in the available filter fields, WorkflowState is deprecated. To search for a finding based on its workflow status, use WorkflowStatus.
One or more attributes used to filter the findings included in the insight. The insight only includes findings that match the criteria defined in the filters.
", + "Insight$Filters": "One or more attributes used to filter the findings included in the insight. You can filter by up to ten finding attributes. For each attribute, you can provide up to 20 filter values. The insight only includes findings that match the criteria defined in the filters.
", "UpdateFindingsRequest$Filters": "A collection of attributes that specify which findings you want to update.
", "UpdateInsightRequest$Filters": "The updated filters that define this insight.
" } @@ -4965,21 +4965,21 @@ "DateFilterList": { "base": null, "refs": { - "AutomationRulesFindingFilters$FirstObservedAt": "A timestamp that indicates when the potential security issue captured by a finding was first observed by the security findings product.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", - "AutomationRulesFindingFilters$LastObservedAt": "A timestamp that indicates when the potential security issue captured by a finding was most recently observed by the security findings product.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", - "AutomationRulesFindingFilters$CreatedAt": "A timestamp that indicates when this finding record was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", - "AutomationRulesFindingFilters$UpdatedAt": "A timestamp that indicates when the finding record was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", - "AutomationRulesFindingFilters$NoteUpdatedAt": " The timestamp of when the note was updated. Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", - "AwsSecurityFindingFilters$FirstObservedAt": "An ISO8601-formatted timestamp that indicates when the security findings provider first observed the potential security issue that a finding captured.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
An ISO8601-formatted timestamp that indicates when the security findings provider most recently observed the potential security issue that a finding captured.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
An ISO8601-formatted timestamp that indicates when the security findings provider captured the potential security issue that a finding captured.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
An ISO8601-formatted timestamp that indicates when the security findings provider last updated the finding record.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that identifies when the process was launched.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that identifies when the process was terminated.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that indicates when the potential security issue captured by a finding was first observed by the security findings product.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", + "AutomationRulesFindingFilters$LastObservedAt": "A timestamp that indicates when the potential security issue captured by a finding was most recently observed by the security findings product.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", + "AutomationRulesFindingFilters$CreatedAt": "A timestamp that indicates when this finding record was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", + "AutomationRulesFindingFilters$UpdatedAt": "A timestamp that indicates when the finding record was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", + "AutomationRulesFindingFilters$NoteUpdatedAt": "The timestamp of when the note was updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Array Members: Minimum number of 1 item. Maximum number of 20 items.
", + "AwsSecurityFindingFilters$FirstObservedAt": "A timestamp that indicates when the security findings provider first observed the potential security issue that a finding captured.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the security findings provider most recently observed the potential security issue that a finding captured.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the security findings provider created the potential security issue that a finding reflects.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the security findings provider last updated the finding record.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that identifies when the process was launched.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that identifies when the process was terminated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that identifies the last observation of a threat intelligence indicator.
", "AwsSecurityFindingFilters$ResourceAwsEc2InstanceLaunchedAt": "The date and time the instance was launched.
", "AwsSecurityFindingFilters$ResourceAwsIamAccessKeyCreatedAt": "The creation date/time of the IAM access key related to a finding.
", - "AwsSecurityFindingFilters$ResourceContainerLaunchedAt": "A timestamp that identifies when the container was started.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that identifies when the container was started.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The timestamp of when the note was updated.
" } }, @@ -5208,7 +5208,7 @@ "AwsEc2LaunchTemplateDataInstanceRequirementsMemoryGiBPerVCpuDetails$Min": "The minimum amount of memory per vCPU, in GiB. If this parameter is omitted, there's no maximum limit.
", "AwsEc2LaunchTemplateDataInstanceRequirementsTotalLocalStorageGBDetails$Max": "The maximum amount of total local storage, in GB.
", "AwsEc2LaunchTemplateDataInstanceRequirementsTotalLocalStorageGBDetails$Min": "The minimum amount of total local storage, in GB.
", - "AwsKmsKeyDetails$CreationDate": "Indicates when the KMS key was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the KMS key was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The number of megabytes per second being transferred from the backup storage. Returns the average rate for a completed backup.
This field is only updated when you restore to DC2 and DS2 node types.
", "Cvss$BaseScore": "The base CVSS score.
", "DoubleConfigurationOptions$DefaultValue": "The Security Hub default value for a control parameter that is a double.
", @@ -6379,8 +6379,8 @@ "AwsApiCallAction$Api": "The name of the API method that was issued.
", "AwsApiCallAction$ServiceName": "The name of the Amazon Web Services service that the API method belongs to.
", "AwsApiCallAction$CallerType": "Indicates whether the API call originated from a remote IP address (remoteip) or from a DNS domain (domain).
An ISO8601-formatted timestamp that indicates when the API call was first observed.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
An ISO8601-formatted timestamp that indicates when the API call was most recently observed.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that indicates when the API call was first observed.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the API call was most recently observed.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the DNS domain that issued the API call.
", "AwsApiGatewayAccessLogSettings$Format": "A single-line format of the access logs of data, as specified by selected $context variables. The format must include at least $context.requestId.
The ARN of the CloudWatch Logs log group that receives the access logs.
", @@ -6392,7 +6392,7 @@ "AwsApiGatewayRestApiDetails$Id": "The identifier of the REST API.
", "AwsApiGatewayRestApiDetails$Name": "The name of the REST API.
", "AwsApiGatewayRestApiDetails$Description": "A description of the REST API.
", - "AwsApiGatewayRestApiDetails$CreatedDate": "Indicates when the API was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the API was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The version identifier for the REST API.
", "AwsApiGatewayRestApiDetails$ApiKeySource": "The source of the API key for metering requests according to a usage plan.
HEADER indicates whether to read the API key from the X-API-Key header of a request.
AUTHORIZER indicates whether to read the API key from the UsageIdentifierKey from a custom authorizer.
The identifier of the deployment that the stage points to.
", @@ -6402,13 +6402,13 @@ "AwsApiGatewayStageDetails$CacheClusterSize": "If a cache cluster is enabled, the size of the cache cluster.
", "AwsApiGatewayStageDetails$CacheClusterStatus": "If a cache cluster is enabled, the status of the cache cluster.
", "AwsApiGatewayStageDetails$DocumentationVersion": "The version of the API documentation that is associated with the stage.
", - "AwsApiGatewayStageDetails$CreatedDate": "Indicates when the stage was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the stage was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the stage was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the stage was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The ARN of the web ACL associated with the stage.
", "AwsApiGatewayV2ApiDetails$ApiEndpoint": "The URI of the API.
Uses the format <api-id>.execute-api.<region>.amazonaws.com
The stage name is typically appended to the URI to form a complete path to a deployed API stage.
", "AwsApiGatewayV2ApiDetails$ApiId": "The identifier of the API.
", "AwsApiGatewayV2ApiDetails$ApiKeySelectionExpression": "An API key selection expression. Supported only for WebSocket APIs.
", - "AwsApiGatewayV2ApiDetails$CreatedDate": "Indicates when the API was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the API was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A description of the API.
", "AwsApiGatewayV2ApiDetails$Version": "The version identifier for the API.
", "AwsApiGatewayV2ApiDetails$Name": "The name of the API.
", @@ -6416,10 +6416,10 @@ "AwsApiGatewayV2ApiDetails$RouteSelectionExpression": "The route selection expression for the API.
For HTTP APIs, must be ${request.method} ${request.path}. This is the default value for HTTP APIs.
For WebSocket APIs, there is no default value.
", "AwsApiGatewayV2RouteSettings$LoggingLevel": "The logging level. The logging level affects the log entries that are pushed to CloudWatch Logs. Supported only for WebSocket APIs.
If the logging level is ERROR, then the logs only include error-level entries.
If the logging level is INFO, then the logs include both ERROR events and extra informational events.
Valid values: OFF | ERROR | INFO
The identifier of a client certificate for a stage. Supported only for WebSocket API calls.
", - "AwsApiGatewayV2StageDetails$CreatedDate": "Indicates when the stage was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the stage was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The description of the stage.
", "AwsApiGatewayV2StageDetails$DeploymentId": "The identifier of the deployment that the stage is associated with.
", - "AwsApiGatewayV2StageDetails$LastUpdatedDate": "Indicates when the stage was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the stage was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the stage.
", "AwsApiGatewayV2StageDetails$LastDeploymentStatusMessage": "The status of the last deployment of a stage. Supported only if the stage has automatic deployment enabled.
", "AwsAppSyncGraphQlApiAdditionalAuthenticationProvidersDetails$AuthenticationType": "The type of security configuration for your GraphQL API: API key, Identity and Access Management (IAM), OpenID Connect (OIDC), Amazon Cognito user pools, or Lambda.
", @@ -6447,7 +6447,7 @@ "AwsAutoScalingAutoScalingGroupAvailabilityZonesListDetails$Value": "The name of the Availability Zone.
", "AwsAutoScalingAutoScalingGroupDetails$LaunchConfigurationName": "The name of the launch configuration.
", "AwsAutoScalingAutoScalingGroupDetails$HealthCheckType": "The service to use for the health checks. Valid values are EC2 or ELB.
Indicates when the auto scaling group was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the auto scaling group was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the launch template. You must specify either LaunchTemplateId or LaunchTemplateName.
The name of the launch template. You must specify either LaunchTemplateId or LaunchTemplateName.
Identifies the version of the launch template. You can specify a version identifier, or use the values $Latest or $Default.
The snapshot ID of the volume to use.
You must specify either VolumeSize or SnapshotId.
The volume type. Valid values are as follows:
gp2
gp3
io1
sc1
st1
standard
The identifier of a ClassicLink-enabled VPC that EC2-Classic instances are linked to.
", - "AwsAutoScalingLaunchConfigurationDetails$CreatedTime": "The creation date and time for the launch configuration.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The creation date and time for the launch configuration.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name or the ARN of the instance profile associated with the IAM role for the instance. The instance profile contains the IAM role.
", "AwsAutoScalingLaunchConfigurationDetails$ImageId": "The identifier of the Amazon Machine Image (AMI) that is used to launch EC2 instances.
", "AwsAutoScalingLaunchConfigurationDetails$InstanceType": "The instance type for the instances.
", @@ -6513,15 +6513,15 @@ "AwsBackupRecoveryPointDetails$StatusMessage": "A message explaining the reason of the recovery point deletion failure.
", "AwsBackupRecoveryPointDetails$StorageClass": "Specifies the storage class of the recovery point. Valid values are as follows:
COLD
DELETED
WARM
The ARN of the private certificate authority (CA) that will be used to issue the certificate.
", - "AwsCertificateManagerCertificateDetails$CreatedAt": "Indicates when the certificate was requested.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the certificate was requested.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The fully qualified domain name (FQDN), such as www.example.com, that is secured by the certificate.
", "AwsCertificateManagerCertificateDetails$FailureReason": "For a failed certificate request, the reason for the failure.
Valid values: NO_AVAILABLE_CONTACTS | ADDITIONAL_VERIFICATION_REQUIRED | DOMAIN_NOT_ALLOWED | INVALID_PUBLIC_DOMAIN | DOMAIN_VALIDATION_DENIED | CAA_ERROR | PCA_LIMIT_EXCEEDED | PCA_INVALID_ARN | PCA_INVALID_STATE | PCA_REQUEST_FAILED | PCA_NAME_CONSTRAINTS_VALIDATION | PCA_RESOURCE_NOT_FOUND | PCA_INVALID_ARGS | PCA_INVALID_DURATION | PCA_ACCESS_DENIED | SLR_NOT_FOUND | OTHER
Indicates when the certificate was imported. Provided if the certificate type is IMPORTED.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the certificate was issued. Provided if the certificate type is AMAZON_ISSUED.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the certificate was imported. Provided if the certificate type is IMPORTED.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the certificate was issued. Provided if the certificate type is AMAZON_ISSUED.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the certificate authority that issued and signed the certificate.
", "AwsCertificateManagerCertificateDetails$KeyAlgorithm": "The algorithm that was used to generate the public-private key pair.
Valid values: RSA_2048 | RSA_1024 | RSA_4096 | EC_prime256v1 | EC_secp384r1 | EC_secp521r1
The time after which the certificate becomes invalid.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The time before which the certificate is not valid.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The time after which the certificate becomes invalid.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The time before which the certificate is not valid.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Whether the certificate is eligible for renewal.
Valid values: ELIGIBLE | INELIGIBLE
The serial number of the certificate.
", "AwsCertificateManagerCertificateDetails$SignatureAlgorithm": "The algorithm that was used to sign the certificate.
", @@ -6538,7 +6538,7 @@ "AwsCertificateManagerCertificateOptions$CertificateTransparencyLoggingPreference": "Whether to add the certificate to a transparency log.
Valid values: DISABLED | ENABLED
The status of the Certificate Manager managed renewal of the certificate.
Valid values: PENDING_AUTO_RENEWAL | PENDING_VALIDATION | SUCCESS | FAILED
The reason that a renewal request was unsuccessful. This attribute is used only when RenewalStatus is FAILED.
Valid values: NO_AVAILABLE_CONTACTS | ADDITIONAL_VERIFICATION_REQUIRED | DOMAIN_NOT_ALLOWED | INVALID_PUBLIC_DOMAIN | DOMAIN_VALIDATION_DENIED | CAA_ERROR | PCA_LIMIT_EXCEEDED | PCA_INVALID_ARN | PCA_INVALID_STATE | PCA_REQUEST_FAILED | PCA_NAME_CONSTRAINTS_VALIDATION | PCA_RESOURCE_NOT_FOUND | PCA_INVALID_ARGS | PCA_INVALID_DURATION | PCA_ACCESS_DENIED | SLR_NOT_FOUND | OTHER
Indicates when the renewal summary was last updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the renewal summary was last updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the resource.
", "AwsCertificateManagerCertificateResourceRecord$Type": "The type of resource.
", "AwsCertificateManagerCertificateResourceRecord$Value": "The value of the resource.
", @@ -6559,7 +6559,7 @@ "AwsCloudFrontDistributionDetails$DefaultRootObject": "The object that CloudFront sends in response to requests from the origin (for example, index.html) when a viewer requests the root URL for the distribution (http://www.example.com) instead of an object in your distribution (http://www.example.com/product-description.html).
", "AwsCloudFrontDistributionDetails$DomainName": "The domain name corresponding to the distribution.
", "AwsCloudFrontDistributionDetails$ETag": "The entity tag is a hash of the object.
", - "AwsCloudFrontDistributionDetails$LastModifiedTime": "Indicates when that the distribution was last modified.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when that the distribution was last modified.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates the current status of the distribution.
", "AwsCloudFrontDistributionDetails$WebAclId": "A unique identifier that specifies the WAF web ACL, if any, to associate with this distribution.
", "AwsCloudFrontDistributionLogging$Bucket": "The S3 bucket to store the access logs in.
", @@ -6662,8 +6662,8 @@ "AwsDynamoDbTableAttributeDefinition$AttributeName": "The name of the attribute.
", "AwsDynamoDbTableAttributeDefinition$AttributeType": "The type of the attribute.
", "AwsDynamoDbTableBillingModeSummary$BillingMode": "The method used to charge for read and write throughput and to manage capacity.
", - "AwsDynamoDbTableBillingModeSummary$LastUpdateToPayPerRequestDateTime": "If the billing mode is PAY_PER_REQUEST, indicates when the billing mode was set to that value.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the table was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
If the billing mode is PAY_PER_REQUEST, indicates when the billing mode was set to that value.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the table was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The version of global tables being used.
", "AwsDynamoDbTableDetails$LatestStreamArn": "The ARN of the latest stream for the table.
", "AwsDynamoDbTableDetails$LatestStreamLabel": "The label of the latest stream. The label is not a unique identifier.
", @@ -6678,8 +6678,8 @@ "AwsDynamoDbTableLocalSecondaryIndex$IndexArn": "The ARN of the index.
", "AwsDynamoDbTableLocalSecondaryIndex$IndexName": "The name of the index.
", "AwsDynamoDbTableProjection$ProjectionType": "The types of attributes that are projected into the index. Valid values are as follows:
ALL
INCLUDE
KEYS_ONLY
Indicates when the provisioned throughput was last decreased.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the provisioned throughput was last increased.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the provisioned throughput was last decreased.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the provisioned throughput was last increased.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the KMS key that will be used for KMS encryption for the replica.
", "AwsDynamoDbTableReplica$RegionName": "The name of the Region where the replica is located.
", "AwsDynamoDbTableReplica$ReplicaStatus": "The current status of the replica. Valid values are as follows:
ACTIVE
CREATING
CREATION_FAILED
DELETING
UPDATING
The name of the index.
", "AwsDynamoDbTableRestoreSummary$SourceBackupArn": "The ARN of the source backup from which the table was restored.
", "AwsDynamoDbTableRestoreSummary$SourceTableArn": "The ARN of the source table for the backup.
", - "AwsDynamoDbTableRestoreSummary$RestoreDateTime": "Indicates the point in time that the table was restored to.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
If the key is inaccessible, the date and time when DynamoDB detected that the key was inaccessible.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates the point in time that the table was restored to.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
If the key is inaccessible, the date and time when DynamoDB detected that the key was inaccessible.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The status of the server-side encryption.
", "AwsDynamoDbTableSseDescription$SseType": "The type of server-side encryption.
", "AwsDynamoDbTableSseDescription$KmsMasterKeyArn": "The ARN of the KMS key that is used for the KMS encryption.
", @@ -6727,7 +6727,7 @@ "AwsEc2InstanceDetails$IamInstanceProfileArn": "The IAM profile ARN of the instance.
", "AwsEc2InstanceDetails$VpcId": "The identifier of the VPC that the instance was launched in.
", "AwsEc2InstanceDetails$SubnetId": "The identifier of the subnet that the instance was launched in.
", - "AwsEc2InstanceDetails$LaunchedAt": "Indicates when the instance was launched.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the instance was launched.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The virtualization type of the Amazon Machine Image (AMI) required to launch the instance.
", "AwsEc2InstanceMetadataOptions$HttpEndpoint": "Enables or disables the HTTP metadata endpoint on the instance.
", "AwsEc2InstanceMetadataOptions$HttpProtocolIpv6": "Enables or disables the IPv6 endpoint for the instance metadata service.
", @@ -6799,7 +6799,7 @@ "AwsEc2NetworkAclEntry$Ipv6CidrBlock": "The IPV6 network range for which to deny or allow access.
", "AwsEc2NetworkAclEntry$Protocol": "The protocol that the rule applies to. To deny or allow access to all protocols, use the value -1.
Whether the rule is used to allow access or deny access.
", - "AwsEc2NetworkInterfaceAttachment$AttachTime": "Indicates when the attachment initiated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the attachment initiated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the network interface attachment
", "AwsEc2NetworkInterfaceAttachment$InstanceId": "The ID of the instance.
", "AwsEc2NetworkInterfaceAttachment$InstanceOwnerId": "The Amazon Web Services account ID of the owner of the instance.
", @@ -6850,7 +6850,7 @@ "AwsEc2VolumeAttachment$AttachTime": "The datetime when the attachment initiated.
", "AwsEc2VolumeAttachment$InstanceId": "The identifier of the EC2 instance.
", "AwsEc2VolumeAttachment$Status": "The attachment state of the volume. Valid values are as follows:
attaching
attached
busy
detaching
detached
Indicates when the volume was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the volume was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The device name for the volume that is attached to the instance.
", "AwsEc2VolumeDetails$SnapshotId": "The snapshot from which the volume was created.
", "AwsEc2VolumeDetails$Status": "The volume state. Valid values are as follows:
available
creating
deleted
deleting
error
in-use
The CIDR block associated with the local subnet of the customer data center.
", "AwsEc2VpnConnectionRoutesDetails$State": "The current state of the static route.
", "AwsEc2VpnConnectionVgwTelemetryDetails$CertificateArn": "The ARN of the VPN tunnel endpoint certificate.
", - "AwsEc2VpnConnectionVgwTelemetryDetails$LastStatusChange": "The date and time of the last change in status.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The date and time of the last change in status.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The Internet-routable IP address of the virtual private gateway's outside interface.
", "AwsEc2VpnConnectionVgwTelemetryDetails$Status": "The status of the VPN tunnel. Valid values are DOWN or UP.
If an error occurs, a description of the error.
", @@ -6895,7 +6895,7 @@ "AwsEcrContainerImageDetails$RepositoryName": "The name of the repository that the image belongs to.
", "AwsEcrContainerImageDetails$Architecture": "The architecture of the image. Valid values are as follows:
arm64
i386
x86_64
The sha256 digest of the image manifest.
", - "AwsEcrContainerImageDetails$ImagePublishedAt": "The date and time when the image was pushed to the repository.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The date and time when the image was pushed to the repository.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The ARN of the repository.
", "AwsEcrRepositoryDetails$ImageTagMutability": "The tag mutability setting for the repository. Valid values are IMMUTABLE or MUTABLE.
The name of the repository.
", @@ -7068,7 +7068,7 @@ "AwsElbLoadBalancerAdditionalAttribute$Value": "The value of the attribute.
", "AwsElbLoadBalancerDetails$CanonicalHostedZoneName": "The name of the Amazon Route 53 hosted zone for the load balancer.
", "AwsElbLoadBalancerDetails$CanonicalHostedZoneNameID": "The ID of the Amazon Route 53 hosted zone for the load balancer.
", - "AwsElbLoadBalancerDetails$CreatedTime": "Indicates when the load balancer was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the load balancer was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The DNS name of the load balancer.
", "AwsElbLoadBalancerDetails$LoadBalancerName": "The name of the load balancer.
", "AwsElbLoadBalancerDetails$Scheme": "The type of load balancer. Only provided if the load balancer is in a VPC.
If Scheme is internet-facing, the load balancer has a public DNS name that resolves to a public IP address.
If Scheme is internal, the load balancer has a public DNS name that resolves to a private IP address.
The name of the load balancer attribute.
", "AwsElbv2LoadBalancerAttribute$Value": "The value of the load balancer attribute.
", "AwsElbv2LoadBalancerDetails$CanonicalHostedZoneId": "The ID of the Amazon Route 53 hosted zone associated with the load balancer.
", - "AwsElbv2LoadBalancerDetails$CreatedTime": "Indicates when the load balancer was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the load balancer was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The public DNS name of the load balancer.
", "AwsElbv2LoadBalancerDetails$IpAddressType": "The type of IP addresses used by the subnets for your load balancer. The possible values are ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses).
The nodes of an Internet-facing load balancer have public IP addresses.
", @@ -7121,13 +7121,13 @@ "AwsGuardDutyDetectorFeaturesDetails$Name": "Indicates the name of the feature that is activated for the detector.
", "AwsGuardDutyDetectorFeaturesDetails$Status": "Indicates the status of the feature that is activated for the detector.
", "AwsIamAccessKeyDetails$UserName": "The user associated with the IAM access key related to a finding.
The UserName parameter has been replaced with the PrincipalName parameter because access keys can also be assigned to principals that are not IAM users.
Indicates when the IAM access key was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the IAM access key was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The ID of the principal associated with an access key.
", "AwsIamAccessKeyDetails$PrincipalType": "The type of principal associated with an access key.
", "AwsIamAccessKeyDetails$PrincipalName": "The name of the principal.
", "AwsIamAccessKeyDetails$AccountId": "The Amazon Web Services account ID of the account for the key.
", "AwsIamAccessKeyDetails$AccessKeyId": "The identifier of the access key.
", - "AwsIamAccessKeySessionContextAttributes$CreationDate": "Indicates when the session was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the session was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The type of principal (user, role, or group) that created the session.
", "AwsIamAccessKeySessionContextSessionIssuer$PrincipalId": "The principal ID of the principal (user, role, or group) that created the session.
", "AwsIamAccessKeySessionContextSessionIssuer$Arn": "The ARN of the session.
", @@ -7135,38 +7135,38 @@ "AwsIamAccessKeySessionContextSessionIssuer$UserName": "The name of the principal that created the session.
", "AwsIamAttachedManagedPolicy$PolicyName": "The name of the policy.
", "AwsIamAttachedManagedPolicy$PolicyArn": "The ARN of the policy.
", - "AwsIamGroupDetails$CreateDate": "Indicates when the IAM group was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the IAM group was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the IAM group.
", "AwsIamGroupDetails$GroupName": "The name of the IAM group.
", "AwsIamGroupDetails$Path": "The path to the group.
", "AwsIamGroupPolicy$PolicyName": "The name of the policy.
", "AwsIamInstanceProfile$Arn": "The ARN of the instance profile.
", - "AwsIamInstanceProfile$CreateDate": "Indicates when the instance profile was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the instance profile was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the instance profile.
", "AwsIamInstanceProfile$InstanceProfileName": "The name of the instance profile.
", "AwsIamInstanceProfile$Path": "The path to the instance profile.
", "AwsIamInstanceProfileRole$Arn": "The ARN of the role.
", - "AwsIamInstanceProfileRole$CreateDate": "Indicates when the role was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the role was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The path to the role.
", "AwsIamInstanceProfileRole$RoleId": "The identifier of the role.
", "AwsIamInstanceProfileRole$RoleName": "The name of the role.
", "AwsIamPermissionsBoundary$PermissionsBoundaryArn": "The ARN of the policy used to set the permissions boundary.
", "AwsIamPermissionsBoundary$PermissionsBoundaryType": "The usage type for the permissions boundary.
", - "AwsIamPolicyDetails$CreateDate": "When the policy was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
When the policy was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the default version of the policy.
", "AwsIamPolicyDetails$Description": "A description of the policy.
", "AwsIamPolicyDetails$Path": "The path to the policy.
", "AwsIamPolicyDetails$PolicyId": "The unique identifier of the policy.
", "AwsIamPolicyDetails$PolicyName": "The name of the policy.
", - "AwsIamPolicyDetails$UpdateDate": "When the policy was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
When the policy was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the policy version.
", - "AwsIamPolicyVersion$CreateDate": "Indicates when the version was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the role was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the version was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the role was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The stable and unique string identifying the role.
", "AwsIamRoleDetails$RoleName": "The friendly name that identifies the role.
", "AwsIamRoleDetails$Path": "The path to the role.
", "AwsIamRolePolicy$PolicyName": "The name of the policy.
", - "AwsIamUserDetails$CreateDate": "Indicates when the user was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the user was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The path to the user.
", "AwsIamUserDetails$UserId": "The unique identifier for the user.
", "AwsIamUserDetails$UserName": "The name of the user.
", @@ -7190,7 +7190,7 @@ "AwsLambdaFunctionDetails$FunctionName": "The name of the function.
", "AwsLambdaFunctionDetails$Handler": "The function that Lambda calls to begin executing your function.
", "AwsLambdaFunctionDetails$KmsKeyArn": "The KMS key that is used to encrypt the function's environment variables. This key is only returned if you've configured a customer managed customer managed key.
", - "AwsLambdaFunctionDetails$LastModified": "Indicates when the function was last updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the function was last updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
For Lambda@Edge functions, the ARN of the master function.
", "AwsLambdaFunctionDetails$RevisionId": "The latest updated revision of the function or alias.
", "AwsLambdaFunctionDetails$Role": "The function's execution role.
", @@ -7202,7 +7202,7 @@ "AwsLambdaFunctionLayer$Arn": "The ARN of the function layer.
", "AwsLambdaFunctionTracingConfig$Mode": "The tracing mode.
", "AwsLambdaFunctionVpcConfig$VpcId": "The ID of the VPC.
", - "AwsLambdaLayerVersionDetails$CreatedDate": "Indicates when the version was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the version was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume.
The path on the container to mount the host volume at.
", "AwsMskClusterClusterInfoDetails$CurrentVersion": "The current version of the cluster.
", @@ -7262,7 +7262,7 @@ "AwsRdsDbClusterDetails$HostedZoneId": "Specifies the identifier that Amazon Route 53 assigns when you create a hosted zone.
", "AwsRdsDbClusterDetails$KmsKeyId": "The ARN of the KMS master key that is used to encrypt the database instances in the DB cluster.
", "AwsRdsDbClusterDetails$DbClusterResourceId": "The identifier of the DB cluster. The identifier must be unique within each Amazon Web Services Region and is immutable.
", - "AwsRdsDbClusterDetails$ClusterCreateTime": "Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The database engine mode of the DB cluster.Valid values are as follows:
global
multimaster
parallelquery
provisioned
serverless
The status of the database activity stream. Valid values are as follows:
started
starting
stopped
stopping
The name of the DB cluster parameter group for the DB cluster.
", @@ -7273,11 +7273,11 @@ "AwsRdsDbClusterOptionGroupMembership$DbClusterOptionGroupName": "The name of the DB cluster option group.
", "AwsRdsDbClusterOptionGroupMembership$Status": "The status of the DB cluster option group.
", "AwsRdsDbClusterSnapshotDbClusterSnapshotAttribute$AttributeName": " The name of the manual DB cluster snapshot attribute. The attribute named restore refers to the list of Amazon Web Services accounts that have permission to copy or restore the manual DB cluster snapshot.
Indicates when the snapshot was taken.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the snapshot was taken.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the database engine that you want to use for this DB instance.
", "AwsRdsDbClusterSnapshotDetails$Status": "The status of this DB cluster snapshot.
", "AwsRdsDbClusterSnapshotDetails$VpcId": "The VPC ID that is associated with the DB cluster snapshot.
", - "AwsRdsDbClusterSnapshotDetails$ClusterCreateTime": "Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the master user for the DB cluster.
", "AwsRdsDbClusterSnapshotDetails$EngineVersion": "The version of the database engine to use.
", "AwsRdsDbClusterSnapshotDetails$LicenseModel": "The license model information for this DB cluster snapshot.
", @@ -7300,7 +7300,7 @@ "AwsRdsDbInstanceDetails$DBName": "The meaning of this parameter differs according to the database engine you use.
MySQL, MariaDB, SQL Server, PostgreSQL
Contains the name of the initial database of this instance that was provided at create time, if one was specified when the DB instance was created. This same name is returned for the life of the DB instance.
Oracle
Contains the Oracle System ID (SID) of the created DB instance. Not shown when the returned parameters do not apply to an Oracle DB instance.
", "AwsRdsDbInstanceDetails$Engine": "Provides the name of the database engine to use for this DB instance.
", "AwsRdsDbInstanceDetails$EngineVersion": "Indicates the database engine version.
", - "AwsRdsDbInstanceDetails$InstanceCreateTime": "Indicates when the DB instance was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the DB instance was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
If StorageEncrypted is true, the KMS key identifier for the encrypted DB instance.
The ARN from the key store with which the instance is associated for TDE encryption.
", "AwsRdsDbInstanceDetails$EnhancedMonitoringResourceArn": "The ARN of the CloudWatch Logs log stream that receives the enhanced monitoring metrics data for the DB instance.
", @@ -7309,7 +7309,7 @@ "AwsRdsDbInstanceDetails$PreferredBackupWindow": "The range of time each day when automated backups are created, if automated backups are enabled.
Uses the format HH:MM-HH:MM. For example, 04:52-05:22.
The Availability Zone where the DB instance will be created.
", "AwsRdsDbInstanceDetails$PreferredMaintenanceWindow": "The weekly time range during which system maintenance can occur, in Universal Coordinated Time (UTC).
Uses the format <day>:HH:MM-<day>:HH:MM.
For the day values, use mon|tue|wed|thu|fri|sat|sun.
For example, sun:09:32-sun:10:02.
Specifies the latest time to which a database can be restored with point-in-time restore.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Specifies the latest time to which a database can be restored with point-in-time restore.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
If this DB instance is a read replica, contains the identifier of the source DB instance.
", "AwsRdsDbInstanceDetails$LicenseModel": "License model information for this DB instance.
", "AwsRdsDbInstanceDetails$CharacterSetName": "The name of the character set that this DB instance is associated with.
", @@ -7384,7 +7384,7 @@ "AwsRdsEventSubscriptionDetails$SnsTopicArn": "The ARN of the SNS topic to post the event notifications to.
", "AwsRdsEventSubscriptionDetails$SourceType": "The source type for the event notification subscription.
", "AwsRdsEventSubscriptionDetails$Status": "The status of the event notification subscription.
Valid values: creating | modifying | deleting | active | no-permission | topic-not-exist
The datetime when the event notification subscription was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The datetime when the event notification subscription was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The role of the node. A node might be a leader node or a compute node.
", "AwsRedshiftClusterClusterNode$PrivateIpAddress": "The private IP address of the node.
", "AwsRedshiftClusterClusterNode$PublicIpAddress": "The public IP address of the node.
", @@ -7397,12 +7397,12 @@ "AwsRedshiftClusterClusterSecurityGroup$Status": "The status of the cluster security group.
", "AwsRedshiftClusterClusterSnapshotCopyStatus$DestinationRegion": "The destination Region that snapshots are automatically copied to when cross-Region snapshot copy is enabled.
", "AwsRedshiftClusterClusterSnapshotCopyStatus$SnapshotCopyGrantName": "The name of the snapshot copy grant.
", - "AwsRedshiftClusterDeferredMaintenanceWindow$DeferMaintenanceEndTime": "The end of the time window for which maintenance was deferred.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The end of the time window for which maintenance was deferred.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The identifier of the maintenance window.
", - "AwsRedshiftClusterDeferredMaintenanceWindow$DeferMaintenanceStartTime": "The start of the time window for which maintenance was deferred.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The start of the time window for which maintenance was deferred.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the Availability Zone in which the cluster is located.
", "AwsRedshiftClusterDetails$ClusterAvailabilityStatus": "The availability status of the cluster for queries. Possible values are the following:
Available - The cluster is available for queries.
Unavailable - The cluster is not available for queries.
Maintenance - The cluster is intermittently available for queries due to maintenance activities.
Modifying -The cluster is intermittently available for queries due to changes that modify the cluster.
Failed - The cluster failed and is not available for queries.
Indicates when the cluster was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the cluster was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The unique identifier of the cluster.
", "AwsRedshiftClusterDetails$ClusterPublicKey": "The public key for the cluster.
", "AwsRedshiftClusterDetails$ClusterRevisionNumber": "The specific revision number of the database in the cluster.
", @@ -7411,12 +7411,12 @@ "AwsRedshiftClusterDetails$ClusterVersion": "The version ID of the Amazon Redshift engine that runs on the cluster.
", "AwsRedshiftClusterDetails$DBName": "The name of the initial database that was created when the cluster was created.
The same name is returned for the life of the cluster.
If an initial database is not specified, a database named devdev is created by default.
The number of nodes that you can use the elastic resize method to resize the cluster to.
", - "AwsRedshiftClusterDetails$ExpectedNextSnapshotScheduleTime": "Indicates when the next snapshot is expected to be taken. The cluster must have a valid snapshot schedule and have backups enabled.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the next snapshot is expected to be taken. The cluster must have a valid snapshot schedule and have backups enabled.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The status of the next expected snapshot.
Valid values: OnTrack | Pending
The identifier of the KMS encryption key that is used to encrypt data in the cluster.
", "AwsRedshiftClusterDetails$MaintenanceTrackName": "The name of the maintenance track for the cluster.
", "AwsRedshiftClusterDetails$MasterUsername": "The master user name for the cluster. This name is used to connect to the database that is specified in as the value of DBName.
Indicates the start of the next maintenance window.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates the start of the next maintenance window.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The node type for the nodes in the cluster.
", "AwsRedshiftClusterDetails$PreferredMaintenanceWindow": "The weekly time range, in Universal Coordinated Time (UTC), during which system maintenance can occur.
Format: <day>:HH:MM-<day>:HH:MM
For the day values, use mon | tue | wed | thu | fri | sat | sun
For example, sun:09:32-sun:10:02
A unique identifier for the cluster snapshot schedule.
", @@ -7432,8 +7432,8 @@ "AwsRedshiftClusterIamRole$IamRoleArn": "The ARN of the IAM role.
", "AwsRedshiftClusterLoggingStatus$BucketName": "The name of the S3 bucket where the log files are stored.
", "AwsRedshiftClusterLoggingStatus$LastFailureMessage": "The message indicating that the logs failed to be delivered.
", - "AwsRedshiftClusterLoggingStatus$LastFailureTime": "The last time when logs failed to be delivered.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The last time that logs were delivered successfully.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The last time when logs failed to be delivered.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The last time that logs were delivered successfully.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Provides the prefix applied to the log file names.
", "AwsRedshiftClusterPendingModifiedValues$ClusterIdentifier": "The pending or in-progress change to the identifier for the cluster.
", "AwsRedshiftClusterPendingModifiedValues$ClusterType": "The pending or in-progress change to the cluster type.
", @@ -7459,7 +7459,7 @@ "AwsS3AccessPointDetails$Name": "The name of the specified access point.
", "AwsS3AccessPointDetails$NetworkOrigin": "Indicates whether this access point allows access from the public internet.
", "AwsS3AccessPointVpcConfigurationDetails$VpcId": "If this field is specified, this access point will only allow connections from the specified VPC ID.
", - "AwsS3BucketBucketLifecycleConfigurationRulesDetails$ExpirationDate": "The date when objects are moved or deleted.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
The date when objects are moved or deleted.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The unique identifier of the rule.
", "AwsS3BucketBucketLifecycleConfigurationRulesDetails$Prefix": "A prefix that identifies one or more objects that the rule applies to.
", "AwsS3BucketBucketLifecycleConfigurationRulesDetails$Status": "The current status of the rule. Indicates whether the rule is currently being applied.
", @@ -7472,13 +7472,13 @@ "AwsS3BucketBucketLifecycleConfigurationRulesFilterPredicateTagDetails$Key": "The tag key.
", "AwsS3BucketBucketLifecycleConfigurationRulesFilterPredicateTagDetails$Value": "The tag value
", "AwsS3BucketBucketLifecycleConfigurationRulesNoncurrentVersionTransitionsDetails$StorageClass": "The class of storage to change the object to after the object is noncurrent for the specified number of days.
", - "AwsS3BucketBucketLifecycleConfigurationRulesTransitionsDetails$Date": "A date on which to transition objects to the specified storage class. If you provide Date, you cannot provide Days.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
A date on which to transition objects to the specified storage class. If you provide Date, you cannot provide Days.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The storage class to transition the object to. Valid values are as follows:
DEEP_ARCHIVE
GLACIER
INTELLIGENT_TIERING
ONEZONE_IA
STANDARD_IA
The versioning status of the S3 bucket. Valid values are Enabled or Suspended.
The canonical user ID of the owner of the S3 bucket.
", "AwsS3BucketDetails$OwnerName": "The display name of the owner of the S3 bucket.
", "AwsS3BucketDetails$OwnerAccountId": "The Amazon Web Services account identifier of the account that owns the S3 bucket.
", - "AwsS3BucketDetails$CreatedAt": "Indicates when the S3 bucket was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the S3 bucket was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The access control list for the S3 bucket.
", "AwsS3BucketDetails$Name": "The name of the bucket.
", "AwsS3BucketLoggingConfiguration$DestinationBucketName": "The name of the S3 bucket where log files for the S3 bucket are stored.
", @@ -7502,7 +7502,7 @@ "AwsS3BucketWebsiteConfigurationRoutingRuleRedirect$Protocol": "The protocol to use to redirect the request. By default, uses the protocol from the original request.
", "AwsS3BucketWebsiteConfigurationRoutingRuleRedirect$ReplaceKeyPrefixWith": "The object key prefix to use in the redirect request.
Cannot be provided if ReplaceKeyWith is present.
The specific object key to use in the redirect request.
Cannot be provided if ReplaceKeyPrefixWith is present.
Indicates when the object was last modified.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the object was last modified.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The opaque identifier assigned by a web server to a specific version of a resource found at a URL.
", "AwsS3ObjectDetails$VersionId": "The version of the object.
", "AwsS3ObjectDetails$ContentType": "A standard MIME type describing the format of the object data.
", @@ -7536,14 +7536,14 @@ "AwsSecurityFinding$Region": "The Region from which the finding was generated.
Security Hub populates this attribute automatically for each finding. You cannot update it using BatchImportFindings or BatchUpdateFindings.
The identifier for the solution-specific component (a discrete unit of logic) that generated a finding. In various security findings providers' solutions, this generator can be called a rule, a check, a detector, a plugin, etc.
", "AwsSecurityFinding$AwsAccountId": "The Amazon Web Services account ID that a finding is generated in.
", - "AwsSecurityFinding$FirstObservedAt": "Indicates when the security findings provider first observed the potential security issue that a finding captured.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the security findings provider most recently observed the potential security issue that a finding captured.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the security findings provider created the potential security issue that a finding captured.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the security findings provider last updated the finding record.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the security findings provider first observed the potential security issue that a finding captured.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the security findings provider most recently observed the potential security issue that a finding captured.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the security findings provider created the potential security issue that a finding captured.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the security findings provider last updated the finding record.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A finding's title.
In this release, Title is a required property.
A finding's description.
In this release, Description is a required property.
A URL that links to a page about the current finding in the security findings provider's solution.
", - "AwsSecurityFinding$ProcessedAt": "An ISO8601-formatted timestamp that indicates when Security Hub received a finding and begins to process it.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A imestamp that indicates when Security Hub received a finding and begins to process it.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The name of the Amazon Web Services account from which a finding was generated.
", "AwsSecurityFindingIdentifier$Id": "The identifier of the finding that was specified by the finding provider.
", "AwsSecurityFindingIdentifier$ProductArn": "The ARN generated by Security Hub that uniquely identifies a product that generates findings. This can be the ARN for a third-party product that is integrated with Security Hub, or the ARN for a custom integration.
", @@ -7670,7 +7670,7 @@ "ContainerDetails$Name": "The name of the container related to a finding.
", "ContainerDetails$ImageId": "The identifier of the container image related to a finding.
", "ContainerDetails$ImageName": "The name of the container image related to a finding.
", - "ContainerDetails$LaunchedAt": "Indicates when the container started.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the container started.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The 2-letter ISO 3166 country code for the country.
", "Country$CountryName": "The name of the country.
", "CreateActionTargetRequest$Name": "The name of the custom action target. Can contain up to 20 characters.
", @@ -7699,8 +7699,8 @@ "Cvss$BaseVector": "The base scoring vector for the CVSS score.
", "Cvss$Source": "The origin of the original CVSS score and vector.
", "DataClassificationDetails$DetailedResultsLocation": "The path to the folder or file that contains the sensitive data.
", - "DateFilter$Start": "A timestamp that provides the start date for the date filter.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that provides the end date for the date filter.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that provides the start date for the date filter.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that provides the end date for the date filter.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The Amazon Resource Name (ARN) of the custom action target to delete.
", "DeleteActionTargetResponse$ActionTargetArn": "The ARN of the custom action target that was deleted.
", "DeleteConfigurationPolicyRequest$Identifier": "The Amazon Resource Name (ARN) or universally unique identifier (UUID) of the configuration policy.
", @@ -7811,7 +7811,7 @@ "NonEmptyStringList$member": null, "Note$Text": "The text of a note.
", "Note$UpdatedBy": "The principal that created a note.
", - "Note$UpdatedAt": "The timestamp of when the note was updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
A timestamp that indicates when the note was updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The updated note text.
", "NoteUpdate$UpdatedBy": "The principal that updated the note.
", "OrganizationConfiguration$StatusMessage": " Provides an explanation if the value of Status is equal to FAILED when ConfigurationType is equal to CENTRAL.
A control parameter that is an enum.
", "Parameters$key": null, "PatchSummary$Id": "The identifier of the compliance standard that was used to determine the patch compliance status.
", - "PatchSummary$OperationStartTime": "Indicates when the operation started.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the operation completed.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the operation started.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the operation completed.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The reboot option specified for the instance.
", "PatchSummary$Operation": "The type of patch operation performed. For Patch Manager, the values are SCAN and INSTALL.
The name of the process.
", "ProcessDetails$Path": "The path to the process executable.
", - "ProcessDetails$LaunchedAt": "Indicates when the process was launched.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the process was terminated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the process was launched.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the process was terminated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The ARN assigned to the product.
", "Product$ProductName": "The name of the product.
", "Product$CompanyName": "The name of the company that provides the product.
", @@ -7970,7 +7970,7 @@ "Threat$Name": "The name of the threat.
", "Threat$Severity": "The severity of the threat.
", "ThreatIntelIndicator$Value": "The value of a threat intelligence indicator.
", - "ThreatIntelIndicator$LastObservedAt": "Indicates when the most recent instance of a threat intelligence indicator was observed.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the most recent instance of a threat intelligence indicator was observed.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The source of the threat intelligence indicator.
", "ThreatIntelIndicator$SourceUrl": "The URL to the page or site where you can get more information about the threat intelligence indicator.
", "TypeList$member": null, @@ -8017,8 +8017,8 @@ "VulnerabilityVendor$Name": "The name of the vendor.
", "VulnerabilityVendor$Url": "The URL of the vulnerability advisory.
", "VulnerabilityVendor$VendorSeverity": "The severity that the vendor assigned to the vulnerability.
", - "VulnerabilityVendor$VendorCreatedAt": "Indicates when the vulnerability advisory was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the vulnerability advisory was last updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces, and date and time should be separated by T. For example, 2020-03-22T13:22:13.933Z.
Indicates when the vulnerability advisory was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Indicates when the vulnerability advisory was last updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
Specifies how you want WAF to respond to requests that match the settings in a rule.
Valid settings include the following:
ALLOW - WAF allows requests
BLOCK - WAF blocks requests
COUNT - WAF increments a counter of the requests that match all of the conditions in the rule. WAF then continues to inspect the web request based on the remaining rules in the web ACL. You can't specify COUNT for the default action for a web ACL.
The unique identifier for the rule to exclude from the rule group.
", "WafOverrideAction$Type": " COUNT overrides the action specified by the individual rule within a RuleGroup .
If set to NONE, the rule's action takes place.
The instruction set architecture that the function uses. Valid values are x86_64 or arm64.
A list of VPC security groups IDs.
", "AwsLambdaFunctionVpcConfig$SubnetIds": "A list of VPC subnet IDs.
", - "AwsLambdaLayerVersionDetails$CompatibleRuntimes": "The layer's compatible runtimes. Maximum number of five items.
Valid values: nodejs10.x | nodejs12.x | java8 | java11 | python2.7 | python3.6 | python3.7 | python3.8 | dotnetcore1.0 | dotnetcore2.1 | go1.x | ruby2.5 | provided
The layer's compatible function runtimes.
The following list includes deprecated runtimes. For more information, see Runtime deprecation policy in the Lambda Developer Guide.
Array Members: Maximum number of 5 items.
Valid Values: nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | nodejs10.x | nodejs12.x | nodejs14.x | nodejs16.x | java8 | java8.al2 | java11 | python2.7 | python3.6 | python3.7 | python3.8 | python3.9 | dotnetcore1.0 | dotnetcore2.0 | dotnetcore2.1 | dotnetcore3.1 | dotnet6 | nodejs4.3-edge | go1.x | ruby2.5 | ruby2.7 | provided | provided.al2 | nodejs18.x | python3.10 | java17 | ruby3.2 | python3.11 | nodejs20.x | provided.al2023 | python3.12 | java21
The list of security group IDs that are associated with the VPC endpoints for the domain.
", "AwsOpenSearchServiceDomainVpcOptionsDetails$SubnetIds": "A list of subnet IDs that are associated with the VPC endpoints for the domain.
", "AwsRdsDbClusterSnapshotDbClusterSnapshotAttribute$AttributeValues": " The value(s) for the manual DB cluster snapshot attribute. If the AttributeName field is set to restore, then this element returns a list of IDs of the Amazon Web Services accounts that are authorized to copy or restore the manual DB cluster snapshot. If a value of all is in the list, then the manual DB cluster snapshot is public and available for any Amazon Web Services account to copy or restore.
A timestamp that indicates when the rule was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
A timestamp that indicates when the rule was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
A timestamp that indicates when the rule was created.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
A timestamp that indicates when the rule was most recently updated.
Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time Format. The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z.
A timestamp that indicates when the rule was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the rule was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the rule was created.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
A timestamp that indicates when the rule was most recently updated.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The date and time, in UTC and ISO 8601 format, that the configuration policy association was last updated.
", "ConfigurationPolicySummary$UpdatedAt": "The date and time, in UTC and ISO 8601 format, that the configuration policy was last updated.
", "CreateConfigurationPolicyResponse$UpdatedAt": "The date and time, in UTC and ISO 8601 format, that the configuration policy was last updated.
", "CreateConfigurationPolicyResponse$CreatedAt": "The date and time, in UTC and ISO 8601 format, that the configuration policy was created.
", - "FindingHistoryRecord$UpdateTime": "An ISO 8601-formatted timestamp that indicates when Security Hub processed the updated finding record.
A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
A timestamp that indicates when Security Hub processed the updated finding record.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The date and time, in UTC and ISO 8601 format, that the configuration policy association was last updated.
", "GetConfigurationPolicyResponse$UpdatedAt": "The date and time, in UTC and ISO 8601 format, that the configuration policy was last updated.
", "GetConfigurationPolicyResponse$CreatedAt": "The date and time, in UTC and ISO 8601 format, that the configuration policy was created.
", - "GetFindingHistoryRequest$StartTime": " An ISO 8601-formatted timestamp that indicates the start time of the requested finding history. A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
If you provide values for both StartTime and EndTime, Security Hub returns finding history for the specified time period. If you provide a value for StartTime but not for EndTime, Security Hub returns finding history from the StartTime to the time at which the API is called. If you provide a value for EndTime but not for StartTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime. If you provide neither StartTime nor EndTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the time at which the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is limited to 90 days.
An ISO 8601-formatted timestamp that indicates the end time of the requested finding history. A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot contain spaces, and date and time should be separated by T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format.
If you provide values for both StartTime and EndTime, Security Hub returns finding history for the specified time period. If you provide a value for StartTime but not for EndTime, Security Hub returns finding history from the StartTime to the time at which the API is called. If you provide a value for EndTime but not for StartTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime. If you provide neither StartTime nor EndTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the time at which the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is limited to 90 days.
A timestamp that indicates the start time of the requested finding history.
If you provide values for both StartTime and EndTime, Security Hub returns finding history for the specified time period. If you provide a value for StartTime but not for EndTime, Security Hub returns finding history from the StartTime to the time at which the API is called. If you provide a value for EndTime but not for StartTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime. If you provide neither StartTime nor EndTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the time at which the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is limited to 90 days.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
An ISO 8601-formatted timestamp that indicates the end time of the requested finding history.
If you provide values for both StartTime and EndTime, Security Hub returns finding history for the specified time period. If you provide a value for StartTime but not for EndTime, Security Hub returns finding history from the StartTime to the time at which the API is called. If you provide a value for EndTime but not for StartTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime. If you provide neither StartTime nor EndTime, Security Hub returns finding history from the CreatedAt timestamp of the finding to the time at which the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is limited to 90 days.
This field accepts only the specified formats. Timestamps can end with Z or (\"+\" / \"-\") time-hour [\":\" time-minute]. The time-secfrac after seconds is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z)
YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59)
YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759)
YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59)
The timestamp of when the invitation was sent.
", "Member$InvitedAt": "A timestamp for the date and time when the invitation was sent to the member account.
", "Member$UpdatedAt": "The timestamp for the date and time when the member account was updated.
", diff --git a/models/endpoints/endpoints.json b/models/endpoints/endpoints.json index 6f90de45fc4..bce7521055b 100644 --- a/models/endpoints/endpoints.json +++ b/models/endpoints/endpoints.json @@ -3738,6 +3738,7 @@ "ap-southeast-1" : { }, "ap-southeast-2" : { }, "ap-southeast-3" : { }, + "ap-southeast-4" : { }, "ca-central-1" : { }, "eu-central-1" : { }, "eu-central-2" : { }, @@ -16636,6 +16637,25 @@ "deprecated" : true, "hostname" : "servicediscovery-fips.ca-central-1.amazonaws.com" }, + "ca-west-1" : { + "variants" : [ { + "hostname" : "servicediscovery-fips.ca-west-1.amazonaws.com", + "tags" : [ "fips" ] + }, { + "hostname" : "servicediscovery-fips.ca-west-1.api.aws", + "tags" : [ "dualstack", "fips" ] + }, { + "hostname" : "servicediscovery.ca-west-1.api.aws", + "tags" : [ "dualstack" ] + } ] + }, + "ca-west-1-fips" : { + "credentialScope" : { + "region" : "ca-west-1" + }, + "deprecated" : true, + "hostname" : "servicediscovery-fips.ca-west-1.amazonaws.com" + }, "eu-central-1" : { "variants" : [ { "hostname" : "servicediscovery.eu-central-1.api.aws", @@ -22451,6 +22471,18 @@ }, "bedrock" : { "endpoints" : { + "bedrock-runtime-us-gov-west-1" : { + "credentialScope" : { + "region" : "us-gov-west-1" + }, + "hostname" : "bedrock-runtime.us-gov-west-1.amazonaws.com" + }, + "bedrock-us-gov-west-1" : { + "credentialScope" : { + "region" : "us-gov-west-1" + }, + "hostname" : "bedrock.us-gov-west-1.amazonaws.com" + }, "us-gov-west-1" : { } } }, diff --git a/service/ecs/api.go b/service/ecs/api.go index aeeb5279682..f4ebcdd3b1e 100644 --- a/service/ecs/api.go +++ b/service/ecs/api.go @@ -12529,6 +12529,15 @@ type DeploymentConfiguration struct { // and the load balancer target group health check to return a healthy status // before counting the task towards the minimum healthy percent total. // + // The default value for a replica service for minimumHealthyPercent is 100%. + // The default minimumHealthyPercent value for a service using the DAEMON service + // schedule is 0% for the CLI, the Amazon Web Services SDKs, and the APIs and + // 50% for the Amazon Web Services Management Console. + // + // The minimum number of healthy tasks during a deployment is the desiredCount + // multiplied by the minimumHealthyPercent/100, rounded up to the nearest integer + // value. + // // If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment // types and is running tasks that use the EC2 launch type, the minimum healthy // percent value is set to the default value and is used to define the lower @@ -20634,23 +20643,20 @@ type RunTaskInput struct { // The family and revision (family:revision) or full ARN of the task definition // to run. If a revision isn't specified, the latest ACTIVE revision is used. // - // When you create a policy for run-task, you can set the resource to be the - // latest task definition revision, or a specific revision. - // // The full ARN value must match the value that you specified as the Resource // of the principal's permissions policy. // - // When you specify the policy resource as the latest task definition version - // (by setting the Resource in the policy to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName), - // then set this value to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName. + // When you specify a task definition, you must either specify a specific revision, + // or all revisions in the ARN. + // + // To specify a specific revision, include the revision number in the ARN. For + // example, to specify revision 2, use arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:2. // - // When you specify the policy resource as a specific task definition version - // (by setting the Resource in the policy to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1 - // or arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*), - // then set this value to arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:1. + // To specify all revisions, use the wildcard (*) in the ARN. For example, to + // specify all revisions, use arn:aws:ecs:us-east-1:111122223333:task-definition/TaskFamilyName:*. // // For more information, see Policy Resources for Amazon ECS (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies-resources) - // in the Amazon Elastic Container Service developer Guide. + // in the Amazon Elastic Container Service Developer Guide. // // TaskDefinition is a required field TaskDefinition *string `locationName:"taskDefinition" type:"string" required:"true"` diff --git a/service/glue/api.go b/service/glue/api.go index 1c896b7f5bb..630ded8ded9 100644 --- a/service/glue/api.go +++ b/service/glue/api.go @@ -51490,6 +51490,16 @@ type GetUnfilteredTableMetadataOutput struct { // A list of column row filters. CellFilters []*ColumnRowFilter `type:"list"` + // Specifies whether the view supports the SQL dialects of one or more different + // query engines and can therefore be read by those engines. + IsMultiDialectView *bool `type:"boolean"` + + // A flag that instructs the engine not to push user-provided operations into + // the logical plan of the view during query planning. However, if set this + // flag does not guarantee that the engine will comply. Refer to the engine's + // documentation to understand the guarantees provided, if any. + IsProtected *bool `type:"boolean"` + // A Boolean value that indicates whether the partition location is registered // with Lake Formation. IsRegisteredWithLakeFormation *bool `type:"boolean"` @@ -51539,6 +51549,18 @@ func (s *GetUnfilteredTableMetadataOutput) SetCellFilters(v []*ColumnRowFilter) return s } +// SetIsMultiDialectView sets the IsMultiDialectView field's value. +func (s *GetUnfilteredTableMetadataOutput) SetIsMultiDialectView(v bool) *GetUnfilteredTableMetadataOutput { + s.IsMultiDialectView = &v + return s +} + +// SetIsProtected sets the IsProtected field's value. +func (s *GetUnfilteredTableMetadataOutput) SetIsProtected(v bool) *GetUnfilteredTableMetadataOutput { + s.IsProtected = &v + return s +} + // SetIsRegisteredWithLakeFormation sets the IsRegisteredWithLakeFormation field's value. func (s *GetUnfilteredTableMetadataOutput) SetIsRegisteredWithLakeFormation(v bool) *GetUnfilteredTableMetadataOutput { s.IsRegisteredWithLakeFormation = &v @@ -71768,6 +71790,10 @@ type TableData struct { // Catalog. FederatedTable *FederatedTable `type:"structure"` + // Specifies whether the view supports the SQL dialects of one or more different + // query engines and can therefore be read by those engines. + IsMultiDialectView *bool `type:"boolean"` + // Indicates whether the table has been registered with Lake Formation. IsRegisteredWithLakeFormation *bool `type:"boolean"` @@ -71829,6 +71855,10 @@ type TableData struct { // The ID of the table version. VersionId *string `min:"1" type:"string"` + // A structure that contains all the information that defines the view, including + // the dialect or dialects for the view, and the query. + ViewDefinition *ViewDefinition `type:"structure"` + // Included for Apache Hive compatibility. Not used in the normal course of // Glue operations. ViewExpandedText *string `type:"string"` @@ -71893,6 +71923,12 @@ func (s *TableData) SetFederatedTable(v *FederatedTable) *TableData { return s } +// SetIsMultiDialectView sets the IsMultiDialectView field's value. +func (s *TableData) SetIsMultiDialectView(v bool) *TableData { + s.IsMultiDialectView = &v + return s +} + // SetIsRegisteredWithLakeFormation sets the IsRegisteredWithLakeFormation field's value. func (s *TableData) SetIsRegisteredWithLakeFormation(v bool) *TableData { s.IsRegisteredWithLakeFormation = &v @@ -71971,6 +72007,12 @@ func (s *TableData) SetVersionId(v string) *TableData { return s } +// SetViewDefinition sets the ViewDefinition field's value. +func (s *TableData) SetViewDefinition(v *ViewDefinition) *TableData { + s.ViewDefinition = v + return s +} + // SetViewExpandedText sets the ViewExpandedText field's value. func (s *TableData) SetViewExpandedText(v string) *TableData { s.ViewExpandedText = &v @@ -77518,6 +77560,145 @@ func (s *VersionMismatchException) RequestID() string { return s.RespMetadata.RequestID } +// A structure containing details for representations. +type ViewDefinition struct { + _ struct{} `type:"structure"` + + // The definer of a view in SQL. + Definer *string `min:"20" type:"string"` + + // You can set this flag as true to instruct the engine not to push user-provided + // operations into the logical plan of the view during query planning. However, + // setting this flag does not guarantee that the engine will comply. Refer to + // the engine's documentation to understand the guarantees provided, if any. + IsProtected *bool `type:"boolean"` + + // A list of representations. + Representations []*ViewRepresentation `min:"1" type:"list"` + + // A list of table Amazon Resource Names (ARNs). + SubObjects []*string `type:"list"` +} + +// String returns the string representation. +// +// API parameter values that are decorated as "sensitive" in the API will not +// be included in the string output. The member name will be present, but the +// value will be replaced with "sensitive". +func (s ViewDefinition) String() string { + return awsutil.Prettify(s) +} + +// GoString returns the string representation. +// +// API parameter values that are decorated as "sensitive" in the API will not +// be included in the string output. The member name will be present, but the +// value will be replaced with "sensitive". +func (s ViewDefinition) GoString() string { + return s.String() +} + +// SetDefiner sets the Definer field's value. +func (s *ViewDefinition) SetDefiner(v string) *ViewDefinition { + s.Definer = &v + return s +} + +// SetIsProtected sets the IsProtected field's value. +func (s *ViewDefinition) SetIsProtected(v bool) *ViewDefinition { + s.IsProtected = &v + return s +} + +// SetRepresentations sets the Representations field's value. +func (s *ViewDefinition) SetRepresentations(v []*ViewRepresentation) *ViewDefinition { + s.Representations = v + return s +} + +// SetSubObjects sets the SubObjects field's value. +func (s *ViewDefinition) SetSubObjects(v []*string) *ViewDefinition { + s.SubObjects = v + return s +} + +// A structure that contains the dialect of the view, and the query that defines +// the view. +type ViewRepresentation struct { + _ struct{} `type:"structure"` + + // The dialect of the query engine. + Dialect *string `type:"string" enum:"ViewDialect"` + + // The version of the dialect of the query engine. For example, 3.0.0. + DialectVersion *string `min:"1" type:"string"` + + // Dialects marked as stale are no longer valid and must be updated before they + // can be queried in their respective query engines. + IsStale *bool `type:"boolean"` + + // The expanded SQL for the view. This SQL is used by engines while processing + // a query on a view. Engines may perform operations during view creation to + // transform ViewOriginalText to ViewExpandedText. For example: + // + // * Fully qualify identifiers: SELECT * from table1 → SELECT * from db1.table1 + ViewExpandedText *string `type:"string"` + + // The SELECT query provided by the customer during CREATE VIEW DDL. This SQL + // is not used during a query on a view (ViewExpandedText is used instead). + // ViewOriginalText is used for cases like SHOW CREATE VIEW where users want + // to see the original DDL command that created the view. + ViewOriginalText *string `type:"string"` +} + +// String returns the string representation. +// +// API parameter values that are decorated as "sensitive" in the API will not +// be included in the string output. The member name will be present, but the +// value will be replaced with "sensitive". +func (s ViewRepresentation) String() string { + return awsutil.Prettify(s) +} + +// GoString returns the string representation. +// +// API parameter values that are decorated as "sensitive" in the API will not +// be included in the string output. The member name will be present, but the +// value will be replaced with "sensitive". +func (s ViewRepresentation) GoString() string { + return s.String() +} + +// SetDialect sets the Dialect field's value. +func (s *ViewRepresentation) SetDialect(v string) *ViewRepresentation { + s.Dialect = &v + return s +} + +// SetDialectVersion sets the DialectVersion field's value. +func (s *ViewRepresentation) SetDialectVersion(v string) *ViewRepresentation { + s.DialectVersion = &v + return s +} + +// SetIsStale sets the IsStale field's value. +func (s *ViewRepresentation) SetIsStale(v bool) *ViewRepresentation { + s.IsStale = &v + return s +} + +// SetViewExpandedText sets the ViewExpandedText field's value. +func (s *ViewRepresentation) SetViewExpandedText(v string) *ViewRepresentation { + s.ViewExpandedText = &v + return s +} + +// SetViewOriginalText sets the ViewOriginalText field's value. +func (s *ViewRepresentation) SetViewOriginalText(v string) *ViewRepresentation { + s.ViewOriginalText = &v + return s +} + // A workflow is a collection of multiple dependent Glue jobs and crawlers that // are run to complete a complex ETL task. A workflow manages the execution // and monitoring of all its jobs and crawlers. diff --git a/service/ivschat/doc.go b/service/ivschat/doc.go index 5b7356acb41..fcd36aed1e4 100644 --- a/service/ivschat/doc.go +++ b/service/ivschat/doc.go @@ -23,17 +23,13 @@ // - You create front-end client applications (browser and Android/iOS apps) // using the Amazon IVS Chat Messaging API. We refer to these as clients. // -// # Resources -// -// The following resources are part of Amazon IVS Chat: +// Key Concepts // // - LoggingConfiguration — A configuration that allows customers to store -// and record sent messages in a chat room. See the Logging Configuration -// endpoints for more information. +// and record sent messages in a chat room. // // - Room — The central Amazon IVS Chat resource through which clients -// connect to and exchange chat messages. See the Room endpoints for more -// information. +// connect to and exchange chat messages. // // # Tagging // diff --git a/service/rolesanywhere/api.go b/service/rolesanywhere/api.go index 4c951e2a9ec..cbfcafafbeb 100644 --- a/service/rolesanywhere/api.go +++ b/service/rolesanywhere/api.go @@ -2720,7 +2720,8 @@ type CreateProfileInput struct { // Used to determine how long sessions vended using this profile are valid for. // See the Expiration section of the CreateSession API documentation (https://docs.aws.amazon.com/rolesanywhere/latest/userguide/authentication-create-session.html#credentials-object) - // page for more details. + // page for more details. In requests, if this value is not provided, the default + // value will be 3600. DurationSeconds *int64 `locationName:"durationSeconds" min:"900" type:"integer"` // Specifies whether the profile is enabled. @@ -5174,7 +5175,8 @@ type ProfileDetail struct { // Used to determine how long sessions vended using this profile are valid for. // See the Expiration section of the CreateSession API documentation (https://docs.aws.amazon.com/rolesanywhere/latest/userguide/authentication-create-session.html#credentials-object) - // page for more details. + // page for more details. In requests, if this value is not provided, the default + // value will be 3600. DurationSeconds *int64 `locationName:"durationSeconds" type:"integer"` // Indicates whether the profile is enabled. @@ -6406,7 +6408,8 @@ type UpdateProfileInput struct { // Used to determine how long sessions vended using this profile are valid for. // See the Expiration section of the CreateSession API documentation (https://docs.aws.amazon.com/rolesanywhere/latest/userguide/authentication-create-session.html#credentials-object) - // page for more details. + // page for more details. In requests, if this value is not provided, the default + // value will be 3600. DurationSeconds *int64 `locationName:"durationSeconds" min:"900" type:"integer"` // A list of managed policy ARNs that apply to the vended session credentials. diff --git a/service/securityhub/api.go b/service/securityhub/api.go index fbf9af61f7e..e7105160ecd 100644 --- a/service/securityhub/api.go +++ b/service/securityhub/api.go @@ -9774,9 +9774,20 @@ type AutomationRulesConfig struct { // A timestamp that indicates when the rule was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt *time.Time `type:"timestamp" timestampFormat:"iso8601"` // The principal that created a rule. @@ -9818,9 +9829,20 @@ type AutomationRulesConfig struct { // A timestamp that indicates when the rule was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdatedAt *time.Time `type:"timestamp" timestampFormat:"iso8601"` } @@ -10092,9 +10114,20 @@ type AutomationRulesFindingFilters struct { // A timestamp that indicates when this finding record was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // Array Members: Minimum number of 1 item. Maximum number of 20 items. CreatedAt []*DateFilter `type:"list"` @@ -10117,9 +10150,20 @@ type AutomationRulesFindingFilters struct { // A timestamp that indicates when the potential security issue captured by // a finding was first observed by the security findings product. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // Array Members: Minimum number of 1 item. Maximum number of 20 items. FirstObservedAt []*DateFilter `type:"list"` @@ -10137,9 +10181,20 @@ type AutomationRulesFindingFilters struct { // A timestamp that indicates when the potential security issue captured by // a finding was most recently observed by the security findings product. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // Array Members: Minimum number of 1 item. Maximum number of 20 items. LastObservedAt []*DateFilter `type:"list"` @@ -10149,9 +10204,22 @@ type AutomationRulesFindingFilters struct { // Array Members: Minimum number of 1 item. Maximum number of 20 items. NoteText []*StringFilter `type:"list"` - // The timestamp of when the note was updated. Uses the date-time format specified - // in RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). - // The value cannot contain spaces. For example, 2020-03-22T13:22:13.933Z. + // The timestamp of when the note was updated. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // Array Members: Minimum number of 1 item. Maximum number of 20 items. NoteUpdatedAt []*DateFilter `type:"list"` @@ -10262,9 +10330,20 @@ type AutomationRulesFindingFilters struct { // A timestamp that indicates when the finding record was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // Array Members: Minimum number of 1 item. Maximum number of 20 items. UpdatedAt []*DateFilter `type:"list"` @@ -10538,9 +10617,20 @@ type AutomationRulesMetadata struct { // A timestamp that indicates when the rule was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt *time.Time `type:"timestamp" timestampFormat:"iso8601"` // The principal that created a rule. @@ -10576,9 +10666,20 @@ type AutomationRulesMetadata struct { // A timestamp that indicates when the rule was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces. For example, 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdatedAt *time.Time `type:"timestamp" timestampFormat:"iso8601"` } @@ -11282,20 +11383,40 @@ type AwsApiCallAction struct { // that the API call originated from. DomainDetails *AwsApiCallActionDomainDetails `type:"structure"` - // An ISO8601-formatted timestamp that indicates when the API call was first - // observed. + // A timestamp that indicates when the API call was first observed. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) FirstSeen *string `type:"string"` - // An ISO8601-formatted timestamp that indicates when the API call was most - // recently observed. + // A timestamp that indicates when the API call was most recently observed. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastSeen *string `type:"string"` // Provided if CallerType is remoteIp. Provides information about the remote @@ -11714,10 +11835,20 @@ type AwsApiGatewayRestApiDetails struct { // Indicates when the API was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedDate *string `type:"string"` // A description of the REST API. @@ -11839,10 +11970,20 @@ type AwsApiGatewayStageDetails struct { // Indicates when the stage was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedDate *string `type:"string"` // The identifier of the deployment that the stage points to. @@ -11856,10 +11997,20 @@ type AwsApiGatewayStageDetails struct { // Indicates when the stage was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastUpdatedDate *string `type:"string"` // Defines the method settings for the stage. @@ -12026,10 +12177,20 @@ type AwsApiGatewayV2ApiDetails struct { // Indicates when the API was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedDate *string `type:"string"` // A description of the API. @@ -12230,10 +12391,20 @@ type AwsApiGatewayV2StageDetails struct { // Indicates when the stage was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedDate *string `type:"string"` // Default route settings for the stage. @@ -12251,10 +12422,20 @@ type AwsApiGatewayV2StageDetails struct { // Indicates when the stage was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastUpdatedDate *string `type:"string"` // The route settings for the stage. @@ -13033,10 +13214,20 @@ type AwsAutoScalingAutoScalingGroupDetails struct { // Indicates when the auto scaling group was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedTime *string `type:"string"` // The amount of time, in seconds, that Amazon EC2 Auto Scaling waits before @@ -13649,10 +13840,20 @@ type AwsAutoScalingLaunchConfigurationDetails struct { // The creation date and time for the launch configuration. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedTime *string `type:"string"` // Whether the launch configuration is optimized for Amazon EBS I/O. @@ -14820,10 +15021,20 @@ type AwsCertificateManagerCertificateDetails struct { // Indicates when the certificate was requested. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt *string `type:"string"` // The fully qualified domain name (FQDN), such as www.example.com, that is @@ -14853,10 +15064,20 @@ type AwsCertificateManagerCertificateDetails struct { // Indicates when the certificate was imported. Provided if the certificate // type is IMPORTED. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ImportedAt *string `type:"string"` // The list of ARNs for the Amazon Web Services resources that use the certificate. @@ -14865,10 +15086,20 @@ type AwsCertificateManagerCertificateDetails struct { // Indicates when the certificate was issued. Provided if the certificate type // is AMAZON_ISSUED. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) IssuedAt *string `type:"string"` // The name of the certificate authority that issued and signed the certificate. @@ -14885,18 +15116,38 @@ type AwsCertificateManagerCertificateDetails struct { // The time after which the certificate becomes invalid. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) NotAfter *string `type:"string"` // The time before which the certificate is not valid. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) NotBefore *string `type:"string"` // Provides a value that specifies whether to add the certificate to a transparency @@ -15322,10 +15573,20 @@ type AwsCertificateManagerCertificateRenewalSummary struct { // Indicates when the renewal summary was last updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdatedAt *string `type:"string"` } @@ -15810,10 +16071,20 @@ type AwsCloudFrontDistributionDetails struct { // Indicates when that the distribution was last modified. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastModifiedTime *string `type:"string"` // A complex type that controls whether access logs are written for the distribution. @@ -18293,10 +18564,20 @@ type AwsDynamoDbTableBillingModeSummary struct { // If the billing mode is PAY_PER_REQUEST, indicates when the billing mode was // set to that value. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastUpdateToPayPerRequestDateTime *string `type:"string"` } @@ -18342,10 +18623,20 @@ type AwsDynamoDbTableDetails struct { // Indicates when the table was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreationDateTime *string `type:"string"` // Indicates whether deletion protection is to be enabled (true) or disabled @@ -18826,18 +19117,38 @@ type AwsDynamoDbTableProvisionedThroughput struct { // Indicates when the provisioned throughput was last decreased. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastDecreaseDateTime *string `type:"string"` // Indicates when the provisioned throughput was last increased. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastIncreaseDateTime *string `type:"string"` // The number of times during the current UTC calendar day that the provisioned @@ -19068,10 +19379,20 @@ type AwsDynamoDbTableRestoreSummary struct { // Indicates the point in time that the table was restored to. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) RestoreDateTime *string `type:"string"` // Whether a restore is currently in progress. @@ -19133,10 +19454,20 @@ type AwsDynamoDbTableSseDescription struct { // If the key is inaccessible, the date and time when DynamoDB detected that // the key was inaccessible. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) InaccessibleEncryptionDateTime *string `type:"string"` // The ARN of the KMS key that is used for the KMS encryption. @@ -19901,10 +20232,20 @@ type AwsEc2InstanceDetails struct { // Indicates when the instance was launched. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LaunchedAt *string `type:"string"` // Details about the metadata options for the Amazon EC2 instance. @@ -22650,10 +22991,20 @@ type AwsEc2NetworkInterfaceAttachment struct { // Indicates when the attachment initiated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) AttachTime *string `type:"string"` // The identifier of the network interface attachment @@ -23747,10 +24098,20 @@ type AwsEc2VolumeDetails struct { // Indicates when the volume was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateTime *string `type:"string"` // The device name for the volume that is attached to the instance. @@ -24702,10 +25063,20 @@ type AwsEc2VpnConnectionVgwTelemetryDetails struct { // The date and time of the last change in status. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastStatusChange *string `type:"string"` // The Internet-routable IP address of the virtual private gateway's outside @@ -24791,10 +25162,20 @@ type AwsEcrContainerImageDetails struct { // The date and time when the image was pushed to the repository. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ImagePublishedAt *string `type:"string"` // The list of tags that are associated with the image. @@ -30474,10 +30855,20 @@ type AwsElbLoadBalancerDetails struct { // Indicates when the load balancer was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedTime *string `type:"string"` // The DNS name of the load balancer. @@ -31023,10 +31414,20 @@ type AwsElbv2LoadBalancerDetails struct { // Indicates when the load balancer was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedTime *string `type:"string"` // The public DNS name of the load balancer. @@ -32113,10 +32514,20 @@ type AwsIamAccessKeyDetails struct { // Indicates when the IAM access key was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt *string `type:"string"` // The ID of the principal associated with an access key. @@ -32262,10 +32673,20 @@ type AwsIamAccessKeySessionContextAttributes struct { // Indicates when the session was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreationDate *string `type:"string"` // Indicates whether the session used multi-factor authentication (MFA). @@ -32421,10 +32842,20 @@ type AwsIamGroupDetails struct { // Indicates when the IAM group was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // The identifier of the IAM group. @@ -32535,10 +32966,20 @@ type AwsIamInstanceProfile struct { // Indicates when the instance profile was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // The identifier of the instance profile. @@ -32640,10 +33081,20 @@ type AwsIamInstanceProfileRole struct { // Indicates when the role was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // The path to the role. @@ -32774,10 +33225,20 @@ type AwsIamPolicyDetails struct { // When the policy was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // The identifier of the default version of the policy. @@ -32807,10 +33268,20 @@ type AwsIamPolicyDetails struct { // When the policy was most recently updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdateDate *string `type:"string"` } @@ -32904,10 +33375,20 @@ type AwsIamPolicyVersion struct { // Indicates when the version was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // Whether the version is the default version. @@ -32965,10 +33446,20 @@ type AwsIamRoleDetails struct { // Indicates when the role was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // The list of instance profiles that contain this role. @@ -33137,10 +33628,20 @@ type AwsIamUserDetails struct { // Indicates when the user was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreateDate *string `type:"string"` // A list of IAM groups that the user belongs to. @@ -33384,10 +33885,20 @@ type AwsKmsKeyDetails struct { // Indicates when the KMS key was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreationDate *float64 `type:"double"` // A description of the KMS key. @@ -33621,10 +34132,20 @@ type AwsLambdaFunctionDetails struct { // Indicates when the function was last updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastModified *string `type:"string"` // The function's layers. @@ -34009,19 +34530,38 @@ func (s *AwsLambdaFunctionVpcConfig) SetVpcId(v string) *AwsLambdaFunctionVpcCon type AwsLambdaLayerVersionDetails struct { _ struct{} `type:"structure"` - // The layer's compatible runtimes. Maximum number of five items. + // The layer's compatible function runtimes (https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html). + // + // The following list includes deprecated runtimes. For more information, see + // Runtime deprecation policy (https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy) + // in the Lambda Developer Guide. // - // Valid values: nodejs10.x | nodejs12.x | java8 | java11 | python2.7 | python3.6 - // | python3.7 | python3.8 | dotnetcore1.0 | dotnetcore2.1 | go1.x | ruby2.5 - // | provided + // Array Members: Maximum number of 5 items. + // + // Valid Values: nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | nodejs10.x | + // nodejs12.x | nodejs14.x | nodejs16.x | java8 | java8.al2 | java11 | python2.7 + // | python3.6 | python3.7 | python3.8 | python3.9 | dotnetcore1.0 | dotnetcore2.0 + // | dotnetcore2.1 | dotnetcore3.1 | dotnet6 | nodejs4.3-edge | go1.x | ruby2.5 + // | ruby2.7 | provided | provided.al2 | nodejs18.x | python3.10 | java17 | + // ruby3.2 | python3.11 | nodejs20.x | provided.al2023 | python3.12 | java21 CompatibleRuntimes []*string `type:"list"` // Indicates when the version was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedDate *string `type:"string"` // The version number. @@ -35767,10 +36307,20 @@ type AwsRdsDbClusterDetails struct { // Indicates when the DB cluster was created, in Universal Coordinated Time // (UTC). // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ClusterCreateTime *string `type:"string"` // Whether tags are copied from the DB cluster to snapshots of the DB cluster. @@ -36311,10 +36861,20 @@ type AwsRdsDbClusterSnapshotDetails struct { // Indicates when the DB cluster was created, in Universal Coordinated Time // (UTC). // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ClusterCreateTime *string `type:"string"` // The DB cluster identifier. @@ -36353,10 +36913,20 @@ type AwsRdsDbClusterSnapshotDetails struct { // Indicates when the snapshot was taken. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) SnapshotCreateTime *string `type:"string"` // The type of DB cluster snapshot. @@ -36738,10 +37308,20 @@ type AwsRdsDbInstanceDetails struct { // Indicates when the DB instance was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) InstanceCreateTime *string `type:"string"` // Specifies the provisioned IOPS (I/O operations per second) for this DB instance. @@ -36754,10 +37334,20 @@ type AwsRdsDbInstanceDetails struct { // Specifies the latest time to which a database can be restored with point-in-time // restore. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LatestRestorableTime *string `type:"string"` // License model information for this DB instance. @@ -38351,10 +38941,20 @@ type AwsRdsEventSubscriptionDetails struct { // The datetime when the event notification subscription was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) SubscriptionCreationTime *string `type:"string"` } @@ -38749,10 +39349,20 @@ type AwsRedshiftClusterDeferredMaintenanceWindow struct { // The end of the time window for which maintenance was deferred. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) DeferMaintenanceEndTime *string `type:"string"` // The identifier of the maintenance window. @@ -38760,10 +39370,20 @@ type AwsRedshiftClusterDeferredMaintenanceWindow struct { // The start of the time window for which maintenance was deferred. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) DeferMaintenanceStartTime *string `type:"string"` } @@ -38835,10 +39455,20 @@ type AwsRedshiftClusterDetails struct { // Indicates when the cluster was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ClusterCreateTime *string `type:"string"` // The unique identifier of the cluster. @@ -38909,10 +39539,20 @@ type AwsRedshiftClusterDetails struct { // Indicates when the next snapshot is expected to be taken. The cluster must // have a valid snapshot schedule and have backups enabled. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ExpectedNextSnapshotScheduleTime *string `type:"string"` // The status of the next expected snapshot. @@ -38954,10 +39594,20 @@ type AwsRedshiftClusterDetails struct { // Indicates the start of the next maintenance window. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) NextMaintenanceWindowStartTime *string `type:"string"` // The node type for the nodes in the cluster. @@ -39488,18 +40138,38 @@ type AwsRedshiftClusterLoggingStatus struct { // The last time when logs failed to be delivered. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastFailureTime *string `type:"string"` // The last time that logs were delivered successfully. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastSuccessfulDeliveryTime *string `type:"string"` // Indicates whether logging is enabled. @@ -40364,10 +41034,20 @@ type AwsS3BucketBucketLifecycleConfigurationRulesDetails struct { // The date when objects are moved or deleted. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ExpirationDate *string `type:"string"` // The length in days of the lifetime for objects that are subject to the rule. @@ -40766,10 +41446,20 @@ type AwsS3BucketBucketLifecycleConfigurationRulesTransitionsDetails struct { // A date on which to transition objects to the specified storage class. If // you provide Date, you cannot provide Days. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) Date *string `type:"string"` // The number of days after which to transition the object to the specified @@ -40893,10 +41583,20 @@ type AwsS3BucketDetails struct { // Indicates when the S3 bucket was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt *string `type:"string"` // The name of the bucket. @@ -41783,10 +42483,20 @@ type AwsS3ObjectDetails struct { // Indicates when the object was last modified. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastModified *string `type:"string"` // The identifier of the KMS symmetric customer managed key that was used for @@ -42290,10 +43000,20 @@ type AwsSecurityFinding struct { // Indicates when the security findings provider created the potential security // issue that a finding captured. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // CreatedAt is a required field CreatedAt *string `type:"string" required:"true"` @@ -42319,10 +43039,20 @@ type AwsSecurityFinding struct { // Indicates when the security findings provider first observed the potential // security issue that a finding captured. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) FirstObservedAt *string `type:"string"` // Provides metadata for the Amazon CodeGuru detector associated with a finding. @@ -42347,10 +43077,20 @@ type AwsSecurityFinding struct { // Indicates when the security findings provider most recently observed the // potential security issue that a finding captured. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastObservedAt *string `type:"string"` // A list of malware related to a finding. @@ -42373,12 +43113,23 @@ type AwsSecurityFinding struct { // The details of process-related information about a finding. Process *ProcessDetails `type:"structure"` - // An ISO8601-formatted timestamp that indicates when Security Hub received - // a finding and begins to process it. + // A imestamp that indicates when Security Hub received a finding and begins + // to process it. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ProcessedAt *string `type:"string"` // The ARN generated by Security Hub that uniquely identifies a product that @@ -42464,10 +43215,20 @@ type AwsSecurityFinding struct { // Indicates when the security findings provider last updated the finding record. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // UpdatedAt is a required field UpdatedAt *string `type:"string" required:"true"` @@ -42917,12 +43678,23 @@ type AwsSecurityFindingFilters struct { // zero percent confidence and 100 means 100 percent confidence. Confidence []*NumberFilter `type:"list"` - // An ISO8601-formatted timestamp that indicates when the security findings - // provider captured the potential security issue that a finding captured. + // A timestamp that indicates when the security findings provider created the + // potential security issue that a finding reflects. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) CreatedAt []*DateFilter `type:"list"` // The level of importance assigned to the resources associated with the finding. @@ -42970,12 +43742,23 @@ type AwsSecurityFindingFilters struct { // | Unusual Behaviors | Sensitive Data Identifications FindingProviderFieldsTypes []*StringFilter `type:"list"` - // An ISO8601-formatted timestamp that indicates when the security findings - // provider first observed the potential security issue that a finding captured. + // A timestamp that indicates when the security findings provider first observed + // the potential security issue that a finding captured. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) FirstObservedAt []*DateFilter `type:"list"` // The identifier for the solution-specific component (a discrete unit of logic) @@ -42991,13 +43774,23 @@ type AwsSecurityFindingFilters struct { // Deprecated: The Keyword property is deprecated. Keyword []*KeywordFilter `deprecated:"true" type:"list"` - // An ISO8601-formatted timestamp that indicates when the security findings - // provider most recently observed the potential security issue that a finding - // captured. + // A timestamp that indicates when the security findings provider most recently + // observed the potential security issue that a finding captured. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastObservedAt []*DateFilter `type:"list"` // The name of the malware that was observed. @@ -43057,9 +43850,20 @@ type AwsSecurityFindingFilters struct { // A timestamp that identifies when the process was launched. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ProcessLaunchedAt []*DateFilter `type:"list"` // The name of the process. @@ -43077,9 +43881,20 @@ type AwsSecurityFindingFilters struct { // A timestamp that identifies when the process was terminated. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ProcessTerminatedAt []*DateFilter `type:"list"` // The ARN generated by Security Hub that uniquely identifies a third-party @@ -43173,9 +43988,20 @@ type AwsSecurityFindingFilters struct { // A timestamp that identifies when the container was started. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) ResourceContainerLaunchedAt []*DateFilter `type:"list"` // The name of the container related to a finding. @@ -43250,12 +44076,23 @@ type AwsSecurityFindingFilters struct { // a finding. Type []*StringFilter `type:"list"` - // An ISO8601-formatted timestamp that indicates when the security findings - // provider last updated the finding record. + // A timestamp that indicates when the security findings provider last updated + // the finding record. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdatedAt []*DateFilter `type:"list"` // A list of name/value string pairs associated with the finding. These are @@ -49003,10 +49840,20 @@ type ContainerDetails struct { // Indicates when the container started. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LaunchedAt *string `type:"string"` // The name of the container related to a finding. @@ -50174,16 +51021,38 @@ type DateFilter struct { // A timestamp that provides the end date for the date filter. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) End *string `type:"string"` // A timestamp that provides the start date for the date filter. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) Start *string `type:"string"` } @@ -52346,12 +53215,23 @@ type FindingHistoryRecord struct { // or an Security Hub customer may call BatchUpdateFindings (https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_BatchUpdateFindings.html). UpdateSource *FindingHistoryUpdateSource `type:"structure"` - // An ISO 8601-formatted timestamp that indicates when Security Hub processed - // the updated finding record. + // A timestamp that indicates when Security Hub processed the updated finding + // record. // - // A correctly formatted example is 2020-05-21T20:16:34.724Z. The value cannot - // contain spaces, and date and time should be separated by T. For more information, - // see RFC 3339 section 5.6, Internet Date/Time Format (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) UpdateTime *time.Time `type:"timestamp" timestampFormat:"iso8601"` // An array of objects that provides details about the finding change event, @@ -53504,10 +54384,7 @@ type GetFindingHistoryInput struct { _ struct{} `type:"structure"` // An ISO 8601-formatted timestamp that indicates the end time of the requested - // finding history. A correctly formatted example is 2020-05-21T20:16:34.724Z. - // The value cannot contain spaces, and date and time should be separated by - // T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format - // (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // finding history. // // If you provide values for both StartTime and EndTime, Security Hub returns // finding history for the specified time period. If you provide a value for @@ -53520,6 +54397,21 @@ type GetFindingHistoryInput struct { // of the finding to the time at which the API is called. In all of these scenarios, // the response is limited to 100 results, and the maximum time period is limited // to 90 days. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) EndTime *time.Time `type:"timestamp" timestampFormat:"iso8601"` // Identifies which finding to get the finding history for. @@ -53537,11 +54429,7 @@ type GetFindingHistoryInput struct { // Hub returns up to 100 results of finding history for each request. NextToken *string `type:"string"` - // An ISO 8601-formatted timestamp that indicates the start time of the requested - // finding history. A correctly formatted example is 2020-05-21T20:16:34.724Z. - // The value cannot contain spaces, and date and time should be separated by - // T. For more information, see RFC 3339 section 5.6, Internet Date/Time Format - // (https://www.rfc-editor.org/rfc/rfc3339#section-5.6). + // A timestamp that indicates the start time of the requested finding history. // // If you provide values for both StartTime and EndTime, Security Hub returns // finding history for the specified time period. If you provide a value for @@ -53554,6 +54442,21 @@ type GetFindingHistoryInput struct { // of the finding to the time at which the API is called. In all of these scenarios, // the response is limited to 100 results, and the maximum time period is limited // to 90 days. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) StartTime *time.Time `type:"timestamp" timestampFormat:"iso8601"` } @@ -54368,8 +55271,9 @@ type Insight struct { _ struct{} `type:"structure"` // One or more attributes used to filter the findings included in the insight. - // The insight only includes findings that match the criteria defined in the - // filters. + // You can filter by up to ten finding attributes. For each attribute, you can + // provide up to 20 filter values. The insight only includes findings that match + // the criteria defined in the filters. // // Filters is a required field Filters *AwsSecurityFindingFilters `type:"structure" required:"true"` @@ -57092,12 +57996,22 @@ type Note struct { // Text is a required field Text *string `type:"string" required:"true"` - // The timestamp of when the note was updated. + // A timestamp that indicates when the note was updated. + // + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) // // UpdatedAt is a required field UpdatedAt *string `type:"string" required:"true"` @@ -57737,18 +58651,38 @@ type PatchSummary struct { // Indicates when the operation completed. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) OperationEndTime *string `type:"string"` // Indicates when the operation started. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) OperationStartTime *string `type:"string"` // The reboot option specified for the instance. @@ -58088,10 +59022,20 @@ type ProcessDetails struct { // Indicates when the process was launched. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LaunchedAt *string `type:"string"` // The name of the process. @@ -58109,10 +59053,20 @@ type ProcessDetails struct { // Indicates when the process was terminated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) TerminatedAt *string `type:"string"` } @@ -63608,10 +64562,20 @@ type ThreatIntelIndicator struct { // Indicates when the most recent instance of a threat intelligence indicator // was observed. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) LastObservedAt *string `type:"string"` // The source of the threat intelligence indicator. @@ -65586,10 +66550,20 @@ type VulnerabilityVendor struct { // Indicates when the vulnerability advisory was created. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) VendorCreatedAt *string `type:"string"` // The severity that the vendor assigned to the vulnerability. @@ -65597,10 +66571,20 @@ type VulnerabilityVendor struct { // Indicates when the vulnerability advisory was last updated. // - // Uses the date-time format specified in RFC 3339 section 5.6, Internet Date/Time - // Format (https://tools.ietf.org/html/rfc3339#section-5.6). The value cannot - // contain spaces, and date and time should be separated by T. For example, - // 2020-03-22T13:22:13.933Z. + // This field accepts only the specified formats. Timestamps can end with Z + // or ("+" / "-") time-hour [":" time-minute]. The time-secfrac after seconds + // is limited to a maximum of 9 digits. The offset is bounded by +/-18:00. Here + // are valid timestamp formats with examples: + // + // * YYYY-MM-DDTHH:MM:SSZ (for example, 2019-01-31T23:00:00Z) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ (for example, 2019-01-31T23:00:00.123456789Z) + // + // * YYYY-MM-DDTHH:MM:SS+HH:MM (for example, 2024-01-04T15:25:10+17:59) + // + // * YYYY-MM-DDTHH:MM:SS-HHMM (for example, 2024-01-04T15:25:10-1759) + // + // * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM (for example, 2024-01-04T15:25:10.123456789+17:59) VendorUpdatedAt *string `type:"string"` } diff --git a/service/securityhub/doc.go b/service/securityhub/doc.go index f5499c8a0cd..79a3a8673ae 100644 --- a/service/securityhub/doc.go +++ b/service/securityhub/doc.go @@ -3,29 +3,68 @@ // Package securityhub provides the client and types for making API // requests to AWS SecurityHub. // -// Security Hub provides you with a comprehensive view of the security state -// of your Amazon Web Services environment and resources. It also provides you -// with the readiness status of your environment based on controls from supported -// security standards. Security Hub collects security data from Amazon Web Services -// accounts, services, and integrated third-party products and helps you analyze -// security trends in your environment to identify the highest priority security -// issues. For more information about Security Hub, see the Security Hub User -// Guide (https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html). -// -// When you use operations in the Security Hub API, the requests are executed -// only in the Amazon Web Services Region that is currently active or in the -// specific Amazon Web Services Region that you specify in your request. Any -// configuration or settings change that results from the operation is applied -// only to that Region. To make the same change in other Regions, run the same -// command for each Region in which you want to apply the change. -// -// For example, if your Region is set to us-west-2, when you use CreateMembers -// to add a member account to Security Hub, the association of the member account -// with the administrator account is created only in the us-west-2 Region. Security -// Hub must be enabled for the member account in the same Region that the invitation -// was sent from. -// -// The following throttling limits apply to using Security Hub API operations. +// Security Hub provides you with a comprehensive view of your security state +// in Amazon Web Services and helps you assess your Amazon Web Services environment +// against security industry standards and best practices. +// +// Security Hub collects security data across Amazon Web Services accounts, +// Amazon Web Services, and supported third-party products and helps you analyze +// your security trends and identify the highest priority security issues. +// +// To help you manage the security state of your organization, Security Hub +// supports multiple security standards. These include the Amazon Web Services +// Foundational Security Best Practices (FSBP) standard developed by Amazon +// Web Services, and external compliance frameworks such as the Center for Internet +// Security (CIS), the Payment Card Industry Data Security Standard (PCI DSS), +// and the National Institute of Standards and Technology (NIST). Each standard +// includes several security controls, each of which represents a security best +// practice. Security Hub runs checks against security controls and generates +// control findings to help you assess your compliance against security best +// practices. +// +// In addition to generating control findings, Security Hub also receives findings +// from other Amazon Web Services, such as Amazon GuardDuty and Amazon Inspector, +// and supported third-party products. This gives you a single pane of glass +// into a variety of security-related issues. You can also send Security Hub +// findings to other Amazon Web Services and supported third-party products. +// +// Security Hub offers automation features that help you triage and remediate +// security issues. For example, you can use automation rules to automatically +// update critical findings when a security check fails. You can also leverage +// the integration with Amazon EventBridge to trigger automatic responses to +// specific findings. +// +// This guide, the Security Hub API Reference, provides information about the +// Security Hub API. This includes supported resources, HTTP methods, parameters, +// and schemas. If you're new to Security Hub, you might find it helpful to +// also review the Security Hub User Guide (https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html). +// The user guide explains key concepts and provides procedures that demonstrate +// how to use Security Hub features. It also provides information about topics +// such as integrating Security Hub with other Amazon Web Services. +// +// In addition to interacting with Security Hub by making calls to the Security +// Hub API, you can use a current version of an Amazon Web Services command +// line tool or SDK. Amazon Web Services provides tools and SDKs that consist +// of libraries and sample code for various languages and platforms, such as +// PowerShell, Java, Go, Python, C++, and .NET. These tools and SDKs provide +// convenient, programmatic access to Security Hub and other Amazon Web Services +// . They also handle tasks such as signing requests, managing errors, and retrying +// requests automatically. For information about installing and using the Amazon +// Web Services tools and SDKs, see Tools to Build on Amazon Web Services (http://aws.amazon.com/developer/tools/). +// +// With the exception of operations that are related to central configuration, +// Security Hub API requests are executed only in the Amazon Web Services Region +// that is currently active or in the specific Amazon Web Services Region that +// you specify in your request. Any configuration or settings change that results +// from the operation is applied only to that Region. To make the same change +// in other Regions, call the same API operation in each Region in which you +// want to apply the change. When you use central configuration, API requests +// for enabling Security Hub, standards, and controls are executed in the home +// Region and all linked Regions. For a list of central configuration operations, +// see the Central configuration terms and concepts (https://docs.aws.amazon.com/securityhub/latest/userguide/central-configuration-intro.html#central-configuration-concepts) +// section of the Security Hub User Guide. +// +// The following throttling limits apply to Security Hub API operations. // // - BatchEnableStandards - RateLimit of 1 request per second. BurstLimit // of 1 request per second.