AWS Native is in preview. AWS Classic is fully supported.
aws-native.ssm.getAssociation
Explore with Pulumi AI
AWS Native is in preview. AWS Classic is fully supported.
The AWS::SSM::Association resource associates an SSM document in AWS Systems Manager with EC2 instances that contain a configuration agent to process the document.
Using getAssociation
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getAssociation(args: GetAssociationArgs, opts?: InvokeOptions): Promise<GetAssociationResult>
function getAssociationOutput(args: GetAssociationOutputArgs, opts?: InvokeOptions): Output<GetAssociationResult>
def get_association(association_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetAssociationResult
def get_association_output(association_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetAssociationResult]
func LookupAssociation(ctx *Context, args *LookupAssociationArgs, opts ...InvokeOption) (*LookupAssociationResult, error)
func LookupAssociationOutput(ctx *Context, args *LookupAssociationOutputArgs, opts ...InvokeOption) LookupAssociationResultOutput
> Note: This function is named LookupAssociation
in the Go SDK.
public static class GetAssociation
{
public static Task<GetAssociationResult> InvokeAsync(GetAssociationArgs args, InvokeOptions? opts = null)
public static Output<GetAssociationResult> Invoke(GetAssociationInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetAssociationResult> getAssociation(GetAssociationArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: aws-native:ssm:getAssociation
arguments:
# arguments dictionary
The following arguments are supported:
- Association
Id string - Unique identifier of the association.
- Association
Id string - Unique identifier of the association.
- association
Id String - Unique identifier of the association.
- association
Id string - Unique identifier of the association.
- association_
id str - Unique identifier of the association.
- association
Id String - Unique identifier of the association.
getAssociation Result
The following output properties are available:
- Apply
Only boolAt Cron Interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- Association
Id string - Unique identifier of the association.
- Association
Name string - The name of the association.
- Automation
Target stringParameter Name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- Calendar
Names List<string> - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- Compliance
Severity Pulumi.Aws Native. Ssm. Association Compliance Severity - The severity level that is assigned to the association.
- Document
Version string - The version of the SSM document to associate with the target.
- Instance
Id string - The ID of the instance that the SSM document is associated with.
- Max
Concurrency string The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- Max
Errors string The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- Name string
- The name of the SSM document.
- Output
Location Pulumi.Aws Native. Ssm. Outputs. Association Instance Association Output Location - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- Parameters
Dictionary<string, Immutable
Array<string>> - Parameter values that the SSM document uses at runtime.
- Schedule
Expression string - A Cron or Rate expression that specifies when the association is applied to the target.
- Schedule
Offset int - Number of days to wait after the scheduled day to run an association.
- Sync
Compliance Pulumi.Aws Native. Ssm. Association Sync Compliance The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- Targets
List<Pulumi.
Aws Native. Ssm. Outputs. Association Target> - The targets that the SSM document sends commands to.
- Apply
Only boolAt Cron Interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- Association
Id string - Unique identifier of the association.
- Association
Name string - The name of the association.
- Automation
Target stringParameter Name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- Calendar
Names []string - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- Compliance
Severity AssociationCompliance Severity - The severity level that is assigned to the association.
- Document
Version string - The version of the SSM document to associate with the target.
- Instance
Id string - The ID of the instance that the SSM document is associated with.
- Max
Concurrency string The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- Max
Errors string The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- Name string
- The name of the SSM document.
- Output
Location AssociationInstance Association Output Location - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- Parameters map[string][]string
- Parameter values that the SSM document uses at runtime.
- Schedule
Expression string - A Cron or Rate expression that specifies when the association is applied to the target.
- Schedule
Offset int - Number of days to wait after the scheduled day to run an association.
- Sync
Compliance AssociationSync Compliance The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- Targets
[]Association
Target - The targets that the SSM document sends commands to.
- apply
Only BooleanAt Cron Interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- association
Id String - Unique identifier of the association.
- association
Name String - The name of the association.
- automation
Target StringParameter Name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- calendar
Names List<String> - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- compliance
Severity AssociationCompliance Severity - The severity level that is assigned to the association.
- document
Version String - The version of the SSM document to associate with the target.
- instance
Id String - The ID of the instance that the SSM document is associated with.
- max
Concurrency String The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- max
Errors String The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- name String
- The name of the SSM document.
- output
Location AssociationInstance Association Output Location - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- parameters Map<String,List<String>>
- Parameter values that the SSM document uses at runtime.
- schedule
Expression String - A Cron or Rate expression that specifies when the association is applied to the target.
- schedule
Offset Integer - Number of days to wait after the scheduled day to run an association.
- sync
Compliance AssociationSync Compliance The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- targets
List<Association
Target> - The targets that the SSM document sends commands to.
- apply
Only booleanAt Cron Interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- association
Id string - Unique identifier of the association.
- association
Name string - The name of the association.
- automation
Target stringParameter Name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- calendar
Names string[] - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- compliance
Severity AssociationCompliance Severity - The severity level that is assigned to the association.
- document
Version string - The version of the SSM document to associate with the target.
- instance
Id string - The ID of the instance that the SSM document is associated with.
- max
Concurrency string The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- max
Errors string The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- name string
- The name of the SSM document.
- output
Location AssociationInstance Association Output Location - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- parameters {[key: string]: string[]}
- Parameter values that the SSM document uses at runtime.
- schedule
Expression string - A Cron or Rate expression that specifies when the association is applied to the target.
- schedule
Offset number - Number of days to wait after the scheduled day to run an association.
- sync
Compliance AssociationSync Compliance The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- targets
Association
Target[] - The targets that the SSM document sends commands to.
- apply_
only_ boolat_ cron_ interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- association_
id str - Unique identifier of the association.
- association_
name str - The name of the association.
- automation_
target_ strparameter_ name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- calendar_
names Sequence[str] - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- compliance_
severity AssociationCompliance Severity - The severity level that is assigned to the association.
- document_
version str - The version of the SSM document to associate with the target.
- instance_
id str - The ID of the instance that the SSM document is associated with.
- max_
concurrency str The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- max_
errors str The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- name str
- The name of the SSM document.
- output_
location AssociationInstance Association Output Location - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- parameters Mapping[str, Sequence[str]]
- Parameter values that the SSM document uses at runtime.
- schedule_
expression str - A Cron or Rate expression that specifies when the association is applied to the target.
- schedule_
offset int - Number of days to wait after the scheduled day to run an association.
- sync_
compliance AssociationSync Compliance The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- targets
Sequence[Association
Target] - The targets that the SSM document sends commands to.
- apply
Only BooleanAt Cron Interval - By default, when you create a new association, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you create it. This parameter is not supported for rate expressions.
- association
Id String - Unique identifier of the association.
- association
Name String - The name of the association.
- automation
Target StringParameter Name - Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- calendar
Names List<String> - The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- compliance
Severity "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "UNSPECIFIED" - The severity level that is assigned to the association.
- document
Version String - The version of the SSM document to associate with the target.
- instance
Id String - The ID of the instance that the SSM document is associated with.
- max
Concurrency String The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new managed node starts and attempts to run an association while Systems Manager is running
MaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.- max
Errors String The number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 managed nodes and set
MaxError
to 10%, then the system stops sending the request when the sixth error is received.Executions that are already running an association when
MaxErrors
is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won't be more than max-errors failed executions, setMaxConcurrency
to 1 so that executions proceed one at a time.- name String
- The name of the SSM document.
- output
Location Property Map - An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- parameters Map<List<String>>
- Parameter values that the SSM document uses at runtime.
- schedule
Expression String - A Cron or Rate expression that specifies when the association is applied to the target.
- schedule
Offset Number - Number of days to wait after the scheduled day to run an association.
- sync
Compliance "AUTO" | "MANUAL" The mode for generating association compliance. You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn't run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
as a parameter for thePutComplianceItems
API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to thePutComplianceItems
API action.By default, all associations use
AUTO
mode.- targets List<Property Map>
- The targets that the SSM document sends commands to.
Supporting Types
AssociationComplianceSeverity
AssociationInstanceAssociationOutputLocation
- S3Location
Pulumi.
Aws Native. Ssm. Inputs. Association S3Output Location S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
- S3Location
Association
S3Output Location S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
- s3Location
Association
S3Output Location S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
- s3Location
Association
S3Output Location S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
- s3_
location AssociationS3Output Location S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
- s3Location Property Map
S3OutputLocation
is a property of the InstanceAssociationOutputLocation property that specifies an Amazon S3 bucket where you want to store the results of this request.
AssociationS3OutputLocation
- Output
S3Bucket stringName - The name of the S3 bucket.
- Output
S3Key stringPrefix - The S3 bucket subfolder.
- Output
S3Region string - The AWS Region of the S3 bucket.
- Output
S3Bucket stringName - The name of the S3 bucket.
- Output
S3Key stringPrefix - The S3 bucket subfolder.
- Output
S3Region string - The AWS Region of the S3 bucket.
- output
S3Bucket StringName - The name of the S3 bucket.
- output
S3Key StringPrefix - The S3 bucket subfolder.
- output
S3Region String - The AWS Region of the S3 bucket.
- output
S3Bucket stringName - The name of the S3 bucket.
- output
S3Key stringPrefix - The S3 bucket subfolder.
- output
S3Region string - The AWS Region of the S3 bucket.
- output_
s3_ strbucket_ name - The name of the S3 bucket.
- output_
s3_ strkey_ prefix - The S3 bucket subfolder.
- output_
s3_ strregion - The AWS Region of the S3 bucket.
- output
S3Bucket StringName - The name of the S3 bucket.
- output
S3Key StringPrefix - The S3 bucket subfolder.
- output
S3Region String - The AWS Region of the S3 bucket.
AssociationSyncCompliance
AssociationTarget
- Key string
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- Values List<string>
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
- Key string
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- Values []string
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
- key String
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- values List<String>
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
- key string
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- values string[]
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
- key str
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- values Sequence[str]
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
- key String
- User-defined criteria for sending commands that target managed nodes that meet the criteria.
- values List<String>
User-defined criteria that maps to
Key
. For example, if you specifiedtag:ServerRole
, you could specifyvalue:WebServer
to run a command on instances that include EC2 tags ofServerRole,WebServer
.Depending on the type of target, the maximum number of values for a key might be lower than the global maximum of 50.
Package Details
- Repository
- AWS Native pulumi/pulumi-aws-native
- License
- Apache-2.0
AWS Native is in preview. AWS Classic is fully supported.