The date by which this activation request should expire. The default value is 24 hours.
" + "documentation":"The date by which this activation request should expire, in timestamp format, such as \"2021-07-07T00:00:00\". You can specify a date up to 30 days in advance. If you don't provide an expiration date, the activation code expires in 24 hours.
" }, "Tags":{ "shape":"TagList", @@ -13166,6 +13166,7 @@ "max":64, "min":1 }, + "ResourceDataSyncEnableAllOpsDataSources":{"type":"boolean"}, "ResourceDataSyncIncludeFutureRegions":{"type":"boolean"}, "ResourceDataSyncInvalidConfigurationException":{ "type":"structure", @@ -13344,6 +13345,10 @@ "IncludeFutureRegions":{ "shape":"ResourceDataSyncIncludeFutureRegions", "documentation":"Whether to automatically synchronize and aggregate data from new AWS Regions when those Regions come online.
" + }, + "EnableAllOpsDataSources":{ + "shape":"ResourceDataSyncEnableAllOpsDataSources", + "documentation":"When you create a resource data sync, if you choose one of the AWS Organizations options, then Systems Manager automatically enables all OpsData sources in the selected AWS Regions for all AWS accounts in your organization (or in the selected organization units). For more information, see About multiple account and Region resource data syncs in the AWS Systems Manager User Guide.
" } }, "documentation":"Information about the source of the data included in the resource data sync.
" @@ -13384,6 +13389,10 @@ "State":{ "shape":"ResourceDataSyncState", "documentation":"The data type name for including resource data sync state. There are four sync states:
OrganizationNotExists: Your organization doesn't exist.
NoPermissions: The system can't locate the service-linked role. This role is automatically created when a user creates a resource data sync in Explorer.
InvalidOrganizationalUnit: You specified or selected an invalid unit in the resource data sync configuration.
TrustedAccessDisabled: You disabled Systems Manager access in the organization in AWS Organizations.
When you create a resource data sync, if you choose one of the AWS Organizations options, then Systems Manager automatically enables all OpsData sources in the selected AWS Regions for all AWS accounts in your organization (or in the selected organization units). For more information, see About multiple account and Region resource data syncs in the AWS Systems Manager User Guide.
" } }, "documentation":"The data type name for including resource data sync state. There are four sync states:
OrganizationNotExists (Your organization doesn't exist)
NoPermissions (The system can't locate the service-linked role. This role is automatically created when a user creates a resource data sync in Explorer.)
InvalidOrganizationalUnit (You specified or selected an invalid unit in the resource data sync configuration.)
TrustedAccessDisabled (You disabled Systems Manager access in the organization in AWS Organizations.)
User-defined criteria that maps to Key. For example, if you specified tag:ServerRole, you could specify value:WebServer to run a command on instances that include EC2 tags of ServerRole,WebServer.
User-defined criteria that maps to Key. For example, if you specified tag:ServerRole, you could specify value:WebServer to run a command on instances that include EC2 tags of ServerRole,WebServer.
Depending on the type of Target, the maximum number of values for a Key might be lower than the global maximum of 50.
An array of search criteria that targets instances using a Key,Value combination that you specify.
One or more targets must be specified for maintenance window Run Command-type tasks. Depending on the task, targets are optional for other maintenance window task types (Automation, AWS Lambda, and AWS Step Functions). For more information about running tasks that do not specify targets, see Registering maintenance window tasks without targets in the AWS Systems Manager User Guide.
Supported formats include the following.
Key=InstanceIds,Values=instance-id-1,instance-id-2,instance-id-3
Key=tag:my-tag-key,Values=my-tag-value-1,my-tag-value-2
Key=tag-key,Values=my-tag-key-1,my-tag-key-2
Run Command and Maintenance window targets only: Key=resource-groups:Name,Values=resource-group-name
Maintenance window targets only: Key=resource-groups:ResourceTypeFilters,Values=resource-type-1,resource-type-2
Automation targets only: Key=ResourceGroup;Values=resource-group-name
For example:
Key=InstanceIds,Values=i-02573cafcfEXAMPLE,i-0471e04240EXAMPLE,i-07782c72faEXAMPLE
Key=tag:CostCenter,Values=CostCenter1,CostCenter2,CostCenter3
Key=tag-key,Values=Name,Instance-Type,CostCenter
Run Command and Maintenance window targets only: Key=resource-groups:Name,Values=ProductionResourceGroup
This example demonstrates how to target all resources in the resource group ProductionResourceGroup in your maintenance window.
Maintenance window targets only: Key=resource-groups:ResourceTypeFilters,Values=AWS::EC2::INSTANCE,AWS::EC2::VPC
This example demonstrates how to target only EC2 instances and VPCs in your maintenance window.
Automation targets only: Key=ResourceGroup,Values=MyResourceGroup
State Manager association targets only: Key=InstanceIds,Values=*
This example demonstrates how to target all managed instances in the AWS Region where the association was created.
For more information about how to send commands that target instances using Key,Value parameters, see Targeting multiple instances in the AWS Systems Manager User Guide.