This class represents one of two things:

Arguments in a call to a service

Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.

As an example, if Att1 is expected to be a Paws::WAF::ByteMatchSet object:

  $service_obj->Method(Att1 => { ByteMatchSetId => $value, ..., Name => $value  });

Results returned from an API call

Use accessors for each attribute. If Att1 is expected to be an Paws::WAF::ByteMatchSet object:

  $result = $service_obj->Method(...);


In a GetByteMatchSet request, ByteMatchSet is a complex type that contains the ByteMatchSetId and Name of a ByteMatchSet, and the values that you specified when you updated the ByteMatchSet.

A complex type that contains ByteMatchTuple objects, which specify the parts of web requests that you want AWS WAF to inspect and the values that you want AWS WAF to search for. If a ByteMatchSet contains more than one ByteMatchTuple object, a request needs to match the settings in only one ByteMatchTuple to be considered a match.


REQUIRED ByteMatchSetId => Str

  The C<ByteMatchSetId> for a C<ByteMatchSet>. You use C<ByteMatchSetId>
to get information about a C<ByteMatchSet> (see GetByteMatchSet),
update a C<ByteMatchSet> (see UpdateByteMatchSet), insert a
C<ByteMatchSet> into a C<Rule> or delete one from a C<Rule> (see
UpdateRule), and delete a C<ByteMatchSet> from AWS WAF (see

ByteMatchSetId is returned by CreateByteMatchSet and by ListByteMatchSets.

REQUIRED ByteMatchTuples => ArrayRef[Paws::WAF::ByteMatchTuple]

  Specifies the bytes (typically a string that corresponds with ASCII
characters) that you want AWS WAF to search for in web requests, the
location in requests that you want AWS WAF to search, and other

Name => Str

  A friendly name or description of the ByteMatchSet. You can't change
C<Name> after you create a C<ByteMatchSet>.


This class forms part of Paws, describing an object used in Paws::WAF


The source code is located here:

Please report bugs to: