AWS EventBridge (version v1.*.*)

activate_event_source#

Activates a partner event source that has been deactivated. Once activated, your matching event bus will start receiving events from the event source.
This operation is performed by AWS customers, not by SaaS partners.

{
  "Name" : "The name of the partner event source to activate."
}

create_event_bus#

Creates a new event bus within your account. This can be a custom event bus which you can use to receive events from your own custom applications and services, or it can be a partner event bus which can be matched to a partner event source.
This operation is used by AWS customers, not by SaaS partners.

{
  "EventSourceName" : "If you're creating a partner event bus, this specifies the partner event source that the new event bus will be matched with.",
  "Name" : "The name of the new event bus.  \nThe names of custom event buses can't contain the / character. You can't use the name default for a custom event bus because this name is already used for your account's default event bus. \nIf this is a partner event bus, the name must exactly match the name of the partner event source that this event bus is matched to. This name will include the / character."
}

create_partner_event_source#

Called by an SaaS partner to create a partner event source.
This operation is not used by AWS customers.
Each partner event source can be used by one AWS account to create a matching partner event bus in that AWS account. A SaaS partner must create one partner event source for each AWS account that wants to receive those event types.
A partner event source creates events based on resources in the SaaS partner's service or application.
An AWS account that creates a partner event bus that matches the partner event source can use that event bus to receive events from the partner, and then process them using AWS Events rules and targets.
Partner event source names follow this format:
aws.partner/partner_name/event_namespace/event_name
partner_name is determined during partner registration and identifies the partner to AWS customers.
For event_namespace, we recommend that partners use a string that identifies the AWS customer within the partner's system. This should not be the customer's AWS account ID.
event_name is determined by the partner, and should uniquely identify an event-generating resource within the partner system. This should help AWS customers decide whether to create an event bus to receive these events.

{
  "Account" : "The AWS account ID of the customer who is permitted to create a matching partner event bus for this partner event source.",
  "Name" : "The name of the partner event source. This name must be unique and must be in the format  partner_name/event_namespace/event_name . The AWS account that wants to use this partner event source must create a partner event bus with a name that matches the name of the partner event source."
}

deactivate_event_source#

An AWS customer uses this operation to temporarily stop receiving events from the specified partner event source. The matching event bus isn't deleted.
When you deactivate a partner event source, the source goes into PENDING state. If it remains in PENDING state for more than two weeks, it's deleted.
To activate a deactivated partner event source, use ActivateEventSource.

{
  "Name" : "The name of the partner event source to deactivate."
}

delete_event_bus#

Deletes the specified custom event bus or partner event bus. All rules associated with this event bus are also deleted. You can't delete your account's default event bus.
This operation is performed by AWS customers, not by SaaS partners.

{
  "Name" : "The name of the event bus to delete."
}

delete_partner_event_source#

This operation is used by SaaS partners to delete a partner event source. AWS customers don't use this operation.
When you delete an event source, the status of the corresponding partner event bus in the AWS customer account becomes DELETED.

{
  "Account" : "The AWS account ID of the AWS customer that the event source was created for.",
  "Name" : "The name of the event source to delete."
}

delete_rule#

Deletes the specified rule.
Before you can delete the rule, you must remove all targets, using RemoveTargets.
When you delete a rule, incoming events might continue to match to the deleted rule. Allow a short period of time for changes to take effect.
Managed rules are rules created and managed by another AWS service on your behalf. These rules are created by those other AWS services to support functionality in those services. You can delete these rules using the Force option, but you should do so only if you're sure that the other service isn't still using that rule.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Force" : "If this is a managed rule, created by an AWS service on your behalf, you must specify Force as True to delete the rule. This parameter is ignored for rules that are not managed rules. You can check whether a rule is a managed rule by using DescribeRule or ListRules and checking the ManagedBy field of the response.",
  "Name" : "The name of the rule."
}

describe_event_bus#

Displays details about an event bus in your account. This can include the external AWS accounts that are permitted to write events to your default event bus, and the associated policy. For custom event buses and partner event buses, it displays the name, ARN, policy, state, and creation time.
To enable your account to receive events from other accounts on its default event bus, use PutPermission.
For more information about partner event buses, see CreateEventBus.

{
  "Name" : "The name of the event bus to show details for. If you omit this, the default event bus is displayed."
}

describe_event_source#

This operation lists details about a partner event source that is shared with your account.
This operation is run by AWS customers, not by SaaS partners.

{
  "Name" : "The name of the partner event source to display the details of."
}

describe_partner_event_source#

An SaaS partner can use this operation to list details about a partner event source that they have created.
AWS customers do not use this operation. Instead, AWS customers can use DescribeEventSource to see details about a partner event source that is shared with them.

{
  "Name" : "The name of the event source to display."
}

describe_rule#

Describes the specified rule.
DescribeRule doesn't list the targets of a rule. To see the targets associated with a rule, use ListTargetsByRule.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Name" : "The name of the rule."
}

disable_rule#

Disables the specified rule. A disabled rule won't match any events and won't self-trigger if it has a schedule expression.
When you disable a rule, incoming events might continue to match to the disabled rule. Allow a short period of time for changes to take effect.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Name" : "The name of the rule."
}

enable_rule#

Enables the specified rule. If the rule doesn't exist, the operation fails.
When you enable a rule, incoming events might not immediately start matching to a newly enabled rule. Allow a short period of time for changes to take effect.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Name" : "The name of the rule."
}

list_event_buses#

Lists all the event buses in your account, including the default event bus, custom event buses, and partner event buses.
This operation is run by AWS customers, not by SaaS partners.

{
  "NamePrefix" : "Specifying this limits the results to only those event buses with names that start with the specified prefix.",
  "NextToken" : "The token returned by a previous call to retrieve the next set of results.",
  "Limit" : "Specifying this limits the number of results returned by this operation. The operation also returns a NextToken that you can use in a subsequent operation to retrieve the next set of results."
}

list_event_sources#

You can use this to see all the partner event sources that have been shared with your AWS account. For more information about partner event sources, see CreateEventBus.
This operation is run by AWS customers, not by SaaS partners.

{
  "NamePrefix" : "Specifying this limits the results to only those partner event sources with names that start with the specified prefix.",
  "NextToken" : "The token returned by a previous call to retrieve the next set of results.",
  "Limit" : "Specifying this limits the number of results returned by this operation. The operation also returns a NextToken that you can use in a subsequent operation to retrieve the next set of results."
}

list_partner_event_source_accounts#

An SaaS partner can use this operation to display the AWS account ID that a particular partner event source name is associated with.
This operation is used by SaaS partners, not by AWS customers.

{
  "NextToken" : "The token returned by a previous call to this operation. Specifying this retrieves the next set of results.",
  "EventSourceName" : "The name of the partner event source to display account information about.",
  "Limit" : "Specifying this limits the number of results returned by this operation. The operation also returns a NextToken that you can use in a subsequent operation to retrieve the next set of results."
}

list_partner_event_sources#

An SaaS partner can use this operation to list all the partner event source names that they have created.
This operation is not used by AWS customers.

{
  "NamePrefix" : "If you specify this, the results are limited to only those partner event sources that start with the string you specify.",
  "NextToken" : "The token returned by a previous call to this operation. Specifying this retrieves the next set of results.",
  "Limit" : "pecifying this limits the number of results returned by this operation. The operation also returns a NextToken that you can use in a subsequent operation to retrieve the next set of results."
}

list_rule_names_by_target#

Lists the rules for the specified target. You can see which rules can invoke a specific target in your account.

{
  "EventBusName" : "Limits the results to show only the rules associated with the specified event bus.",
  "TargetArn" : "The Amazon Resource Name (ARN) of the target resource."
}

list_rules#

Lists your EventBridge rules. You can either list all the rules or provide a prefix to match to the rule names.
ListRules doesn't list the targets of a rule. To see the targets associated with a rule, use ListTargetsByRule.

{
  "NamePrefix" : "The prefix matching the rule name.",
  "EventBusName" : "Limits the results to show only the rules associated with the specified event bus."
}

list_tags_for_resource#

Displays the tags associated with an EventBridge resource. In EventBridge, rules can be tagged.

{
  "ResourceARN" : "The ARN of the rule for which you want to view tags."
}

list_targets_by_rule#

Lists the targets assigned to the specified rule.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Rule" : "The name of the rule."
}

put_events#

Sends custom events to EventBridge so that they can be matched to rules. These events can be from your custom applications and services.

{
  "Entries" : [ {
    "EventBusName" : "The event bus that will receive the event. Only the rules that are associated with this event bus can match the event.",
    "DetailType" : "Free-form string used to decide which fields to expect in the event detail. This field is required.",
    "Time" : "The timestamp of the event, per RFC3339. If no timestamp is provided, the timestamp of the PutEvents call is used.",
    "Resources" : [ "string" ],
    "Source" : "The source of the event. This field is required.",
    "Detail" : "A valid JSON object. There is no other schema imposed. The JSON object can contain fields and nested subobjects. \nThis field is required."
  } ]
}

put_partner_events#

This is used by SaaS partners to write events to a customer's partner event bus.
AWS customers do not use this operation. Instead, AWS customers can use PutEvents to write custom events from their own applications to an event bus.

{
  "Entries" : [ {
    "DetailType" : "A free-form string used to decide which fields to expect in the event detail. This field is required.",
    "Time" : "The date and time of the event.",
    "Resources" : [ "string" ],
    "Source" : "The event source that is generating the evntry. This field is required.",
    "Detail" : "A valid JSON object. There is no other schema imposed. The JSON object can contain fields and nested subobjects. This field is required."
  } ]
}

put_permission#

Running PutPermission permits the specified AWS account or AWS organization to put events to the specified event bus. Rules in your account are triggered by these events arriving to an event bus in your account.
For another account to send events to your account, that external account must have a rule with your account's event bus as a target.
To enable multiple AWS accounts to put events to an event bus, run PutPermission once for each of these accounts. Or, if all the accounts are members of the same AWS organization, you can run PutPermission once specifying Principal as "*" and specifying the AWS organization ID in Condition, to grant permissions to all accounts in that organization.
If you grant permissions using an organization, then accounts in that organization must specify a RoleArn with proper permissions when they use PutTarget to add your account's event bus as a target. For more information, see Sending and Receiving Events Between AWS Accounts in the Amazon EventBridge User Guide.
The permission policy on an event bus can't exceed 10 KB in size.

{
  "EventBusName" : "The event bus associated with the rule. If you omit this, the default event bus is used.",
  "Condition" : {
    "Type" : "The type of condition. Currently, the only supported value is StringEquals.",
    "Value" : "The value for the key. Currently, this must be the ID of the organization.",
    "Key" : "The key for the condition. Currently, the only supported key is aws:PrincipalOrgID."
  },
  "Action" : "The action that you're enabling the other account to perform. Currently, this must be events:PutEvents.",
  "StatementId" : "An identifier string for the external account that you're granting permissions to. If you later want to revoke the permission for this external account, specify this StatementId when you run RemovePermission.",
  "Principal" : "The 12-digit AWS account ID that you are permitting to put events to your default event bus. Specify \"*\" to permit any account to put events to your default event bus. \nIf you specify \"*\" without specifying Condition, avoid creating rules that might match undesirable events. To create more secure rules, make sure that the event pattern for each rule contains an account field with a specific account ID to receive events from. Rules that have an account field match events sent only from accounts that are listed in the rule's account field."
}

put_rule#

Creates or updates the specified rule. Rules are enabled by default or based on value of the state. You can disable a rule using DisableRule.
A single rule watches for events from a single event bus. Events generated by AWS services go to your account's default event bus. Events generated by SaaS partner services or applications go to the matching partner event bus. If you have custom applications or services, you can specify whether their events go to your default event bus or a custom event bus that you have created. For more information, see CreateEventBus.
If you're updating an existing rule, the rule is replaced with what you specify in this PutRule command. If you omit arguments in PutRule, the old values for those arguments aren't kept. Instead, they're replaced with null values.
When you create or update a rule, incoming events might not immediately start matching to new or updated rules. Allow a short period of time for changes to take effect.
A rule must contain at least an EventPattern or ScheduleExpression. Rules with EventPatterns are triggered when a matching event is observed. Rules with ScheduleExpressions self-trigger based on the given schedule. A rule can have both an EventPattern and a ScheduleExpression, in which case the rule triggers on matching events as well as on a schedule.
When you initially create a rule, you can optionally assign one or more tags to the rule. Tags can help you organize and categorize your resources. You can also use them to scope user permissions, by granting a user permission to access or change only rules with certain tag values. To use the PutRule operation and assign tags, you must have both the events:PutRule and events:TagResource permissions.
If you are updating an existing rule, any tags you specify in the PutRule operation are ignored. To update the tags of an existing rule, use TagResource and UntagResource.
Most services in AWS treat : or / as the same character in Amazon Resource Names (ARNs). However, EventBridge uses an exact match in event patterns and rules. Be sure to use the correct ARN characters when creating event patterns so that they match the ARN syntax in the event that you want to match.
In EventBridge, you could create rules that lead to infinite loops, where a rule is fired repeatedly. For example, a rule might detect that ACLs have changed on an S3 bucket, and trigger software to change them to the desired state. If you don't write the rule carefully, the subsequent change to the ACLs fires the rule again, creating an infinite loop.
To prevent this, write the rules so that the triggered actions don't refire the same rule. For example, your rule could fire only if ACLs are found to be in a bad state, instead of after any change.
An infinite loop can quickly cause higher than expected charges. We recommend that you use budgeting, which alerts you when charges exceed your specified limit. For more information, see Managing Your Costs with Budgets.

{
  "EventBusName" : "The event bus to associate with this rule. If you omit this, the default event bus is used.",
  "ScheduleExpression" : "The scheduling expression: for example, \"cron(0 20 * * ? *)\" or \"rate(5 minutes)\".",
  "EventPattern" : "The event pattern. For more information, see Event Patterns in the Amazon EventBridge User Guide.",
  "Description" : "A description of the rule.",
  "State" : "Indicates whether the rule is enabled or disabled.",
  "RoleArn" : "The Amazon Resource Name (ARN) of the IAM role associated with the rule.",
  "Tags" : [ {
    "Value" : "The value for the specified tag key.",
    "Key" : "A string that you can use to assign a value. The combination of tag keys and values can help you organize and categorize your resources."
  } ],
  "Name" : "The name of the rule that you're creating or updating. \nA rule can't have the same name as another rule in the same Region or on the same event bus."
}

put_targets#

Adds the specified targets to the specified rule, or updates the targets if they're already associated with the rule.
Targets are the resources that are invoked when a rule is triggered.
You can configure the following as targets in EventBridge:
EC2 instances
SSM Run Command
SSM Automation
AWS Lambda functions
Data streams in Amazon Kinesis Data Streams
Data delivery streams in Amazon Kinesis Data Firehose
Amazon ECS tasks
AWS Step Functions state machines
AWS Batch jobs
AWS CodeBuild projects
Pipelines in AWS CodePipeline
Amazon Inspector assessment templates
Amazon SNS topics
Amazon SQS queues, including FIFO queues
The default event bus of another AWS account
Creating rules with built-in targets is supported only on the AWS Management Console. The built-in targets are EC2 CreateSnapshot API call, EC2 RebootInstances API call, EC2 StopInstances API call, and EC2 TerminateInstances API call.
For some target types, PutTargets provides target-specific parameters. If the target is a Kinesis data stream, you can optionally specify which shard the event goes to by using the KinesisParameters argument. To invoke a command on multiple EC2 instances with one rule, you can use the RunCommandParameters field.
To be able to make API calls against the resources that you own, Amazon EventBridge needs the appropriate permissions. For AWS Lambda and Amazon SNS resources, EventBridge relies on resource-based policies. For EC2 instances, Kinesis data streams, and AWS Step Functions state machines, EventBridge relies on IAM roles that you specify in the RoleARN argument in PutTargets. For more information, see Authentication and Access Control in the Amazon EventBridge User Guide.
If another AWS account is in the same Region and has granted you permission (using PutPermission), you can send events to that account. Set that account's event bus as a target of the rules in your account. To send the matched events to the other account, specify that account's event bus as the Arn value when you run PutTargets. If your account sends events to another account, your account is charged for each sent event. Each event sent to another account is charged as a custom event. The account receiving the event isn't charged. For more information, see Amazon EventBridge Pricing.
If you're setting an event bus in another account as the target and that account granted permission to your account through an organization instead of directly by the account ID, you must specify a RoleArn with proper permissions in the Target structure. For more information, see Sending and Receiving Events Between AWS Accounts in the Amazon EventBridge User Guide.
For more information about enabling cross-account events, see PutPermission.
Input, InputPath, and InputTransformer are mutually exclusive and optional parameters of a target. When a rule is triggered due to a matched event:
If none of the following arguments are specified for a target, the entire event is passed to the target in JSON format (unless the target is Amazon EC2 Run Command or Amazon ECS task, in which case nothing from the event is passed to the target).
If Input is specified in the form of valid JSON, then the matched event is overridden with this constant.
If InputPath is specified in the form of JSONPath (for example, $.detail), only the part of the event specified in the path is passed to the target (for example, only the detail part of the event is passed).
If InputTransformer is specified, one or more specified JSONPaths are extracted from the event and used as values in a template that you specify as the input to the target.
When you specify InputPath or InputTransformer, you must use JSON dot notation, not bracket notation.
When you add targets to a rule and the associated rule triggers soon after, new or updated targets might not be immediately invoked. Allow a short period of time for changes to take effect.
This action can partially fail if too many requests are made at the same time. If that happens, FailedEntryCount is nonzero in the response, and each entry in FailedEntries provides the ID of the failed target and the error code.

{
  "EventBusName" : "The name of the event bus associated with the rule. If you omit this, the default event bus is used.",
  "Targets" : [ {
    "InputPath" : "The value of the JSONPath that is used for extracting part of the matched event when passing it to the target. You must use JSON dot notation, not bracket notation. For more information about JSON paths, see JSONPath.",
    "Input" : "Valid JSON text passed to the target. In this case, nothing from the event itself is passed to the target. For more information, see The JavaScript Object Notation (JSON) Data Interchange Format.",
    "SqsParameters" : {
      "MessageGroupId" : "The FIFO message group ID to use as the target."
    },
    "EcsParameters" : {
      "PlatformVersion" : "Specifies the platform version for the task. Specify only the numeric portion of the platform version, such as 1.1.0. \nThis structure is used only if LaunchType is FARGATE. For more information about valid platform versions, see AWS Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.",
      "Group" : "Specifies an ECS task group for the task. The maximum length is 255 characters.",
      "TaskCount" : "The number of tasks to create based on TaskDefinition. The default is 1.",
      "NetworkConfiguration" : {
        "awsvpcConfiguration" : {
          "SecurityGroups" : [ "string" ],
          "Subnets" : [ "string" ],
          "AssignPublicIp" : "Specifies whether the task's elastic network interface receives a public IP address. You can specify ENABLED only when LaunchType in EcsParameters is set to FARGATE."
        }
      },
      "LaunchType" : "Specifies the launch type on which your task is running. The launch type that you specify here must match one of the launch type (compatibilities) of the target task. The FARGATE value is supported only in the Regions where AWS Fargate with Amazon ECS is supported. For more information, see AWS Fargate on Amazon ECS in the Amazon Elastic Container Service Developer Guide.",
      "TaskDefinitionArn" : "The ARN of the task definition to use if the event target is an Amazon ECS task. "
    },
    "RunCommandParameters" : {
      "RunCommandTargets" : [ {
        "Values" : [ "string" ],
        "Key" : "Can be either tag: tag-key or InstanceIds."
      } ]
    },
    "BatchParameters" : {
      "ArrayProperties" : {
        "Size" : "The size of the array, if this is an array batch job. Valid values are integers between 2 and 10,000."
      },
      "JobName" : "The name to use for this execution of the job, if the target is an AWS Batch job.",
      "RetryStrategy" : {
        "Attempts" : "The number of times to attempt to retry, if the job fails. Valid values are 1–10."
      },
      "JobDefinition" : "The ARN or name of the job definition to use if the event target is an AWS Batch job. This job definition must already exist."
    },
    "Id" : "A name for the target. Use a string that will help you identify the target. Each target associated with a rule must have an Id unique for that rule.",
    "Arn" : "The Amazon Resource Name (ARN) of the target.",
    "InputTransformer" : {
      "InputPathsMap" : "Map of JSON paths to be extracted from the event. You can then insert these in the template in InputTemplate to produce the output to be sent to the target. \n InputPathsMap is an array key-value pairs, where each value is a valid JSON path. You can have as many as 10 key-value pairs. You must use JSON dot notation, not bracket notation. \nThe keys can't start with \"AWS\".",
      "InputTemplate" : "Input template where you specify placeholders that will be filled with the values of the keys from InputPathsMap to customize the data sent to the target. Enclose each InputPathsMaps value in brackets: <value>. The InputTemplate must be valid JSON. \nIf InputTemplate is a JSON object (surrounded by curly braces), the following restrictions apply:  \n The placeholder can't be used as an object key  \n Object values can't include quote marks   \nThe following example shows the syntax for using InputPathsMap and InputTemplate. \n  \"InputTransformer\":  \n {  \n \"InputPathsMap\": {\"instance\": \"$.detail.instance\",\"status\": \"$.detail.status\"},  \n \"InputTemplate\": \"<instance> is in state <status>\"  \n }  \nTo have the InputTemplate include quote marks within a JSON string, escape each quote marks with a slash, as in the following example: \n  \"InputTransformer\":  \n {  \n \"InputPathsMap\": {\"instance\": \"$.detail.instance\",\"status\": \"$.detail.status\"},  \n \"InputTemplate\": \"<instance> is in state \\\"<status>\\\"\"  \n } "
    },
    "KinesisParameters" : {
      "PartitionKeyPath" : "The JSON path to be extracted from the event and used as the partition key. For more information, see Amazon Kinesis Streams Key Concepts in the Amazon Kinesis Streams Developer Guide."
    },
    "RoleArn" : "The Amazon Resource Name (ARN) of the IAM role to be used for this target when the rule is triggered. If one rule triggers multiple targets, you can use a different IAM role for each target."
  } ],
  "Rule" : "The name of the rule."
}

remove_permission#

Revokes the permission of another AWS account to be able to put events to the specified event bus. Specify the account to revoke by the StatementId value that you associated with the account when you granted it permission with PutPermission. You can find the StatementId by using DescribeEventBus.

{
  "EventBusName" : "The name of the event bus to revoke permissions for. If you omit this, the default event bus is used.",
  "StatementId" : "The statement ID corresponding to the account that is no longer allowed to put events to the default event bus."
}

remove_targets#

Removes the specified targets from the specified rule. When the rule is triggered, those targets are no longer be invoked.
When you remove a target, when the associated rule triggers, removed targets might continue to be invoked. Allow a short period of time for changes to take effect.
This action can partially fail if too many requests are made at the same time. If that happens, FailedEntryCount is non-zero in the response and each entry in FailedEntries provides the ID of the failed target and the error code.

{
  "EventBusName" : "The name of the event bus associated with the rule.",
  "Force" : "If this is a managed rule created by an AWS service on your behalf, you must specify Force as True to remove targets. This parameter is ignored for rules that aren't managed rules. You can check whether a rule is a managed rule by using DescribeRule or ListRules and checking the ManagedBy field of the response.",
  "Ids" : [ "string" ],
  "Rule" : "The name of the rule."
}

tag_resource#

Assigns one or more tags (key-value pairs) to the specified EventBridge resource. Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values. In EventBridge, rules can be tagged.
Tags don't have any semantic meaning to AWS and are interpreted strictly as strings of characters.
You can use the TagResource action with a rule that already has tags. If you specify a new tag key for the rule, this tag is appended to the list of tags associated with the rule. If you specify a tag key that is already associated with the rule, the new tag value that you specify replaces the previous value for that tag.
You can associate as many as 50 tags with a resource.

{
  "ResourceARN" : "The ARN of the rule that you're adding tags to.",
  "Tags" : [ {
    "Value" : "The value for the specified tag key.",
    "Key" : "A string that you can use to assign a value. The combination of tag keys and values can help you organize and categorize your resources."
  } ]
}

test_event_pattern#

Tests whether the specified event pattern matches the provided event.
Most services in AWS treat : or / as the same character in Amazon Resource Names (ARNs). However, EventBridge uses an exact match in event patterns and rules. Be sure to use the correct ARN characters when creating event patterns so that they match the ARN syntax in the event that you want to match.

{
  "EventPattern" : "The event pattern. For more information, see Event Patterns in the Amazon EventBridge User Guide.",
  "Event" : "The event, in JSON format, to test against the event pattern."
}

untag_resource#

Removes one or more tags from the specified EventBridge resource. In EventBridge, rules can be tagged.

{
  "ResourceARN" : "The ARN of the rule that you're removing tags from.",
  "TagKeys" : [ "string" ]
}