Skip to content

Commit

Permalink
Merge branch 'release-1.34.101' into develop
Browse files Browse the repository at this point in the history
* release-1.34.101:
  Bumping version to 1.34.101
  Update to latest models
  • Loading branch information
aws-sdk-python-automation committed May 8, 2024
2 parents 53e2903 + 98b1a71 commit d85b98d
Show file tree
Hide file tree
Showing 10 changed files with 101 additions and 29 deletions.
32 changes: 32 additions & 0 deletions .changes/1.34.101.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
[
{
"category": "``cognito-idp``",
"description": "Add EXTERNAL_PROVIDER enum value to UserStatusType.",
"type": "api-change"
},
{
"category": "``ec2``",
"description": "Adding Precision Hardware Clock (PHC) to public API DescribeInstanceTypes",
"type": "api-change"
},
{
"category": "``ecr``",
"description": "This release adds pull through cache rules support for GitLab container registry in Amazon ECR.",
"type": "api-change"
},
{
"category": "``fms``",
"description": "The policy scope resource tag is always a string value, either a non-empty string or an empty string.",
"type": "api-change"
},
{
"category": "``polly``",
"description": "Add new engine - generative - that builds the most expressive conversational voices.",
"type": "api-change"
},
{
"category": "``sqs``",
"description": "This release adds MessageSystemAttributeNames to ReceiveMessageRequest to replace AttributeNames.",
"type": "api-change"
}
]
11 changes: 11 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,17 @@
CHANGELOG
=========

1.34.101
========

* api-change:``cognito-idp``: Add EXTERNAL_PROVIDER enum value to UserStatusType.
* api-change:``ec2``: Adding Precision Hardware Clock (PHC) to public API DescribeInstanceTypes
* api-change:``ecr``: This release adds pull through cache rules support for GitLab container registry in Amazon ECR.
* api-change:``fms``: The policy scope resource tag is always a string value, either a non-empty string or an empty string.
* api-change:``polly``: Add new engine - generative - that builds the most expressive conversational voices.
* api-change:``sqs``: This release adds MessageSystemAttributeNames to ReceiveMessageRequest to replace AttributeNames.


1.34.100
========

Expand Down
2 changes: 1 addition & 1 deletion botocore/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
import os
import re

__version__ = '1.34.100'
__version__ = '1.34.101'


class NullHandler(logging.Handler):
Expand Down
4 changes: 3 additions & 1 deletion botocore/data/cognito-idp/2016-04-18/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
"endpointPrefix":"cognito-idp",
"jsonVersion":"1.1",
"protocol":"json",
"protocols":["json"],
"serviceFullName":"Amazon Cognito Identity Provider",
"serviceId":"Cognito Identity Provider",
"signatureVersion":"v4",
Expand Down Expand Up @@ -8445,7 +8446,8 @@
"COMPROMISED",
"UNKNOWN",
"RESET_REQUIRED",
"FORCE_CHANGE_PASSWORD"
"FORCE_CHANGE_PASSWORD",
"EXTERNAL_PROVIDER"
]
},
"UserType":{
Expand Down
12 changes: 12 additions & 0 deletions botocore/data/ec2/2016-11-15/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -37277,6 +37277,11 @@
"shape":"NeuronInfo",
"documentation":"<p>Describes the Neuron accelerator settings for the instance type.</p>",
"locationName":"neuronInfo"
},
"PhcSupport":{
"shape":"PhcSupport",
"documentation":"<p>Indicates whether a local Precision Time Protocol (PTP) hardware clock (PHC) is supported.</p>",
"locationName":"phcSupport"
}
},
"documentation":"<p>Describes the instance type.</p>"
Expand Down Expand Up @@ -47150,6 +47155,13 @@
},
"documentation":"<p>Specifies the integrity algorithm for the VPN tunnel for phase 2 IKE negotiations.</p>"
},
"PhcSupport":{
"type":"string",
"enum":[
"unsupported",
"supported"
]
},
"Placement":{
"type":"structure",
"members":{
Expand Down
6 changes: 4 additions & 2 deletions botocore/data/ecr/2015-09-21/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
"endpointPrefix":"api.ecr",
"jsonVersion":"1.1",
"protocol":"json",
"protocols":["json"],
"serviceAbbreviation":"Amazon ECR",
"serviceFullName":"Amazon EC2 Container Registry",
"serviceId":"ECR",
Expand Down Expand Up @@ -1032,7 +1033,7 @@
},
"upstreamRegistryUrl":{
"shape":"Url",
"documentation":"<p>The registry URL of the upstream public registry to use as the source for the pull through cache rule. The following is the syntax to use for each supported upstream registry.</p> <ul> <li> <p>Amazon ECR Public (<code>ecr-public</code>) - <code>public.ecr.aws</code> </p> </li> <li> <p>Docker Hub (<code>docker-hub</code>) - <code>registry-1.docker.io</code> </p> </li> <li> <p>Quay (<code>quay</code>) - <code>quay.io</code> </p> </li> <li> <p>Kubernetes (<code>k8s</code>) - <code>registry.k8s.io</code> </p> </li> <li> <p>GitHub Container Registry (<code>github-container-registry</code>) - <code>ghcr.io</code> </p> </li> <li> <p>Microsoft Azure Container Registry (<code>azure-container-registry</code>) - <code>&lt;custom&gt;.azurecr.io</code> </p> </li> </ul>"
"documentation":"<p>The registry URL of the upstream public registry to use as the source for the pull through cache rule. The following is the syntax to use for each supported upstream registry.</p> <ul> <li> <p>Amazon ECR Public (<code>ecr-public</code>) - <code>public.ecr.aws</code> </p> </li> <li> <p>Docker Hub (<code>docker-hub</code>) - <code>registry-1.docker.io</code> </p> </li> <li> <p>Quay (<code>quay</code>) - <code>quay.io</code> </p> </li> <li> <p>Kubernetes (<code>k8s</code>) - <code>registry.k8s.io</code> </p> </li> <li> <p>GitHub Container Registry (<code>github-container-registry</code>) - <code>ghcr.io</code> </p> </li> <li> <p>Microsoft Azure Container Registry (<code>azure-container-registry</code>) - <code>&lt;custom&gt;.azurecr.io</code> </p> </li> <li> <p>GitLab Container Registry (<code>gitlab-container-registry</code>) - <code>registry.gitlab.com</code> </p> </li> </ul>"
},
"registryId":{
"shape":"RegistryId",
Expand Down Expand Up @@ -3924,7 +3925,8 @@
"k8s",
"docker-hub",
"github-container-registry",
"azure-container-registry"
"azure-container-registry",
"gitlab-container-registry"
]
},
"Url":{"type":"string"},
Expand Down
12 changes: 6 additions & 6 deletions botocore/data/fms/2018-01-01/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -599,7 +599,7 @@
{"shape":"InternalErrorException"},
{"shape":"InvalidTypeException"}
],
"documentation":"<p>Creates an Firewall Manager policy.</p> <p>A Firewall Manager policy is specific to the individual policy type. If you want to enforce multiple policy types across accounts, you can create multiple policies. You can create more than one policy for each type. </p> <p>If you add a new account to an organization that you created with Organizations, Firewall Manager automatically applies the policy to the resources in that account that are within scope of the policy. </p> <p>Firewall Manager provides the following types of policies: </p> <ul> <li> <p> <b>WAF policy</b> - This policy applies WAF web ACL protections to specified accounts and resources. </p> </li> <li> <p> <b>Shield Advanced policy</b> - This policy applies Shield Advanced protection to specified accounts and resources. </p> </li> <li> <p> <b>Security Groups policy</b> - This type of policy gives you control over security groups that are in use throughout your organization in Organizations and lets you enforce a baseline set of rules across your organization. </p> </li> <li> <p> <b>Network ACL policy</b> - This type of policy gives you control over the network ACLs that are in use throughout your organization in Organizations and lets you enforce a baseline set of first and last network ACL rules across your organization. </p> </li> <li> <p> <b>Network Firewall policy</b> - This policy applies Network Firewall protection to your organization's VPCs. </p> </li> <li> <p> <b>DNS Firewall policy</b> - This policy applies Amazon Route 53 Resolver DNS Firewall protections to your organization's VPCs. </p> </li> <li> <p> <b>Third-party firewall policy</b> - This policy applies third-party firewall protections. Third-party firewalls are available by subscription through the Amazon Web Services Marketplace console at <a href=\"https://aws.amazon.com/marketplace\">Amazon Web Services Marketplace</a>.</p> <ul> <li> <p> <b>Palo Alto Networks Cloud NGFW policy</b> - This policy applies Palo Alto Networks Cloud Next Generation Firewall (NGFW) protections and Palo Alto Networks Cloud NGFW rulestacks to your organization's VPCs.</p> </li> <li> <p> <b>Fortigate CNF policy</b> - This policy applies Fortigate Cloud Native Firewall (CNF) protections. Fortigate CNF is a cloud-centered solution that blocks Zero-Day threats and secures cloud infrastructures with industry-leading advanced threat prevention, smart web application firewalls (WAF), and API protection.</p> </li> </ul> </li> </ul>"
"documentation":"<p>Creates an Firewall Manager policy.</p> <p>A Firewall Manager policy is specific to the individual policy type. If you want to enforce multiple policy types across accounts, you can create multiple policies. You can create more than one policy for each type. </p> <p>If you add a new account to an organization that you created with Organizations, Firewall Manager automatically applies the policy to the resources in that account that are within scope of the policy. </p> <p>Firewall Manager provides the following types of policies: </p> <ul> <li> <p> <b>WAF policy</b> - This policy applies WAF web ACL protections to specified accounts and resources. </p> </li> <li> <p> <b>Shield Advanced policy</b> - This policy applies Shield Advanced protection to specified accounts and resources. </p> </li> <li> <p> <b>Security Groups policy</b> - This type of policy gives you control over security groups that are in use throughout your organization in Organizations and lets you enforce a baseline set of rules across your organization. </p> </li> <li> <p> <b>Network ACL policy</b> - This type of policy gives you control over the network ACLs that are in use throughout your organization in Organizations and lets you enforce a baseline set of first and last network ACL rules across your organization. </p> </li> <li> <p> <b>Network Firewall policy</b> - This policy applies Network Firewall protection to your organization's VPCs. </p> </li> <li> <p> <b>DNS Firewall policy</b> - This policy applies Amazon Route 53 Resolver DNS Firewall protections to your organization's VPCs. </p> </li> <li> <p> <b>Third-party firewall policy</b> - This policy applies third-party firewall protections. Third-party firewalls are available by subscription through the Amazon Web Services Marketplace console at <a href=\"http://aws.amazon.com/marketplace\">Amazon Web Services Marketplace</a>.</p> <ul> <li> <p> <b>Palo Alto Networks Cloud NGFW policy</b> - This policy applies Palo Alto Networks Cloud Next Generation Firewall (NGFW) protections and Palo Alto Networks Cloud NGFW rulestacks to your organization's VPCs.</p> </li> <li> <p> <b>Fortigate CNF policy</b> - This policy applies Fortigate Cloud Native Firewall (CNF) protections. Fortigate CNF is a cloud-centered solution that blocks Zero-Day threats and secures cloud infrastructures with industry-leading advanced threat prevention, smart web application firewalls (WAF), and API protection.</p> </li> </ul> </li> </ul>"
},
"PutProtocolsList":{
"name":"PutProtocolsList",
Expand Down Expand Up @@ -2637,15 +2637,15 @@
},
"ForceRemediateForFirstEntries":{
"shape":"BooleanObject",
"documentation":"<p>Applies only when remediation is enabled for the policy as a whole. Firewall Manager uses this setting when it finds policy violations that involve conflicts between the custom entries and the policy entries. </p> <p>If forced remediation is disabled, Firewall Manager marks the network ACL as noncompliant and does not try to remediate. For more information about the remediation behavior, see <a href=\"https://docs.aws.amazon.com/waf/latest/developerguide/network-acl-policies.html\">Network access control list (ACL) policies</a> in the <i>Firewall Manager Developer Guide</i>.</p>"
"documentation":"<p>Applies only when remediation is enabled for the policy as a whole. Firewall Manager uses this setting when it finds policy violations that involve conflicts between the custom entries and the policy entries. </p> <p>If forced remediation is disabled, Firewall Manager marks the network ACL as noncompliant and does not try to remediate. For more information about the remediation behavior, see <a href=\"https://docs.aws.amazon.com/waf/latest/developerguide/network-acl-policies.html#network-acls-remediation\">Remediation for managed network ACLs</a> in the <i>Firewall Manager Developer Guide</i>.</p>"
},
"LastEntries":{
"shape":"NetworkAclEntries",
"documentation":"<p>The rules that you want to run last in the Firewall Manager managed network ACLs. </p> <note> <p>Provide these in the order in which you want them to run. Firewall Manager will assign the specific rule numbers for you, in the network ACLs that it creates. </p> </note> <p>You must specify at least one first entry or one last entry in any network ACL policy. </p>"
},
"ForceRemediateForLastEntries":{
"shape":"BooleanObject",
"documentation":"<p>Applies only when remediation is enabled for the policy as a whole. Firewall Manager uses this setting when it finds policy violations that involve conflicts between the custom entries and the policy entries. </p> <p>If forced remediation is disabled, Firewall Manager marks the network ACL as noncompliant and does not try to remediate. For more information about the remediation behavior, see <a href=\"https://docs.aws.amazon.com/waf/latest/developerguide/network-acl-policies.html\">Network access control list (ACL) policies</a> in the <i>Firewall Manager Developer Guide</i>.</p>"
"documentation":"<p>Applies only when remediation is enabled for the policy as a whole. Firewall Manager uses this setting when it finds policy violations that involve conflicts between the custom entries and the policy entries. </p> <p>If forced remediation is disabled, Firewall Manager marks the network ACL as noncompliant and does not try to remediate. For more information about the remediation behavior, see <a href=\"https://docs.aws.amazon.com/waf/latest/developerguide/network-acl-policies.html#network-acls-remediation\">Remediation for managed network ACLs</a> in the <i>Firewall Manager Developer Guide</i>.</p>"
}
},
"documentation":"<p>The configuration of the first and last rules for the network ACL policy, and the remediation settings for each. </p>"
Expand Down Expand Up @@ -3205,7 +3205,7 @@
},
"PolicyDescription":{
"shape":"ResourceDescription",
"documentation":"<p>The definition of the Network Firewall firewall policy.</p>"
"documentation":"<p>Your description of the Firewall Manager policy.</p>"
},
"PolicyStatus":{
"shape":"CustomerPolicyStatus",
Expand Down Expand Up @@ -3917,10 +3917,10 @@
},
"Value":{
"shape":"ResourceTagValue",
"documentation":"<p>The resource tag value.</p>"
"documentation":"<p>The resource tag value. To specify an empty string value, either don't provide this or specify it as \"\". </p>"
}
},
"documentation":"<p>The resource tags that Firewall Manager uses to determine if a particular resource should be included or excluded from the Firewall Manager policy. Tags enable you to categorize your Amazon Web Services resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value. Firewall Manager combines the tags with \"AND\" so that, if you add more than one tag to a policy scope, a resource must have all the specified tags to be included or excluded. For more information, see <a href=\"https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/tag-editor.html\">Working with Tag Editor</a>.</p>"
"documentation":"<p>The resource tags that Firewall Manager uses to determine if a particular resource should be included or excluded from the Firewall Manager policy. Tags enable you to categorize your Amazon Web Services resources in different ways, for example, by purpose, owner, or environment. Each tag consists of a key and an optional value. Firewall Manager combines the tags with \"AND\" so that, if you add more than one tag to a policy scope, a resource must have all the specified tags to be included or excluded. For more information, see <a href=\"https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/tag-editor.html\">Working with Tag Editor</a>.</p> <p>Every resource tag must have a string value, either a non-empty string or an empty string. If you don't provide a value for a resource tag, Firewall Manager saves the value as an empty string: \"\". When Firewall Manager compares tags, it only matches two tags if they have the same key and the same value. A tag with an empty string value only matches with tags that also have an empty string value. </p>"
},
"ResourceTagKey":{
"type":"string",
Expand Down
Loading

0 comments on commit d85b98d

Please sign in to comment.