Release v1.37.20 (2021-02-26)

===

### Service Client Updates
* `service/eks`: Updates service API and documentation
* `service/elasticmapreduce`: Updates service API and documentation
  * Added UpdateStudio API that allows updating a few attributes of an EMR Studio.
* `service/s3`: Updates service API, documentation, and examples
  * Add RequestPayer to GetObjectTagging and PutObjectTagging.
* `service/sso-admin`: Updates service API

CHANGELOG.md

@@ -1,3 +1,14 @@
+Release v1.37.20 (2021-02-26)
+===
+
+### Service Client Updates
+* `service/eks`: Updates service API and documentation
+* `service/elasticmapreduce`: Updates service API and documentation
+ * Added UpdateStudio API that allows updating a few attributes of an EMR Studio.
+* `service/s3`: Updates service API, documentation, and examples
+ * Add RequestPayer to GetObjectTagging and PutObjectTagging.
+* `service/sso-admin`: Updates service API
+
 Release v1.37.19 (2021-02-25)
 ===
 

aws/version.go

@@ -5,4 +5,4 @@ package aws
 const SDKName = "aws-sdk-go"
 
 // SDKVersion is the version of this SDK
-const SDKVersion = "1.37.19"
+const SDKVersion = "1.37.20"

models/apis/eks/2017-11-01/api-2.json

@@ -13,6 +13,23 @@
  "uid":"eks-2017-11-01"
  },
  "operations":{
+ "AssociateEncryptionConfig":{
+ "name":"AssociateEncryptionConfig",
+ "http":{
+ "method":"POST",
+ "requestUri":"/clusters/{name}/encryption-config/associate"
+ },
+ "input":{"shape":"AssociateEncryptionConfigRequest"},
+ "output":{"shape":"AssociateEncryptionConfigResponse"},
+ "errors":[
+ {"shape":"InvalidParameterException"},
+ {"shape":"ClientException"},
+ {"shape":"ServerException"},
+ {"shape":"ResourceInUseException"},
+ {"shape":"ResourceNotFoundException"},
+ {"shape":"InvalidRequestException"}
+ ]
+ },
  "AssociateIdentityProviderConfig":{
  "name":"AssociateIdentityProviderConfig",
  "http":{
@@ -594,6 +611,31 @@
  "type":"list",
  "member":{"shape":"AddonInfo"}
  },
+ "AssociateEncryptionConfigRequest":{
+ "type":"structure",
+ "required":[
+ "clusterName",
+ "encryptionConfig"
+ ],
+ "members":{
+ "clusterName":{
+ "shape":"String",
+ "location":"uri",
+ "locationName":"name"
+ },
+ "encryptionConfig":{"shape":"EncryptionConfigList"},
+ "clientRequestToken":{
+ "shape":"String",
+ "idempotencyToken":true
+ }
+ }
+ },
+ "AssociateEncryptionConfigResponse":{
+ "type":"structure",
+ "members":{
+ "update":{"shape":"Update"}
+ }
+ },
  "AssociateIdentityProviderConfigRequest":{
  "type":"structure",
  "required":[
@@ -2055,6 +2097,7 @@
  "ReleaseVersion",
  "PublicAccessCidrs",
  "IdentityProviderConfig",
+ "EncryptionConfig",
  "AddonVersion",
  "ServiceAccountRoleArn",
  "ResolveConflicts"
@@ -2082,6 +2125,7 @@
  "ConfigUpdate",
  "AssociateIdentityProviderConfig",
  "DisassociateIdentityProviderConfig",
+ "AssociateEncryptionConfig",
  "AddonUpdate"
  ]
  },

models/apis/eks/2017-11-01/docs-2.json

@@ -2,9 +2,10 @@
  "version": "2.0",
  "service": "<p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to stand up or maintain your own Kubernetes control plane. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications. </p> <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS are fully compatible with applications running on any standard Kubernetes environment, whether running in on-premises data centers or public clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS without any code modification required.</p>",
  "operations": {
+ "AssociateEncryptionConfig": "<p>Associate encryption configuration to an existing cluster.</p> <p>You can use this API to enable encryption on existing clusters which do not have encryption already enabled. This allows you to implement a defense-in-depth security strategy without migrating applications to new EKS clusters.</p>",
  "AssociateIdentityProviderConfig": "<p>Associate an identity provider configuration to a cluster.</p> <p>If you want to authenticate identities using an identity provider, you can create an identity provider configuration and associate it to your cluster. After configuring authentication to your cluster you can create Kubernetes <code>roles</code> and <code>clusterroles</code> to assign permissions to the roles, and then bind the roles to the identities using Kubernetes <code>rolebindings</code> and <code>clusterrolebindings</code>. For more information see <a href=\"https://kubernetes.io/docs/reference/access-authn-authz/rbac/\">Using RBAC Authorization</a> in the Kubernetes documentation.</p>",
  "CreateAddon": "<p>Creates an Amazon EKS add-on.</p> <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management of common operational software for Amazon EKS clusters. Amazon EKS add-ons can only be used with Amazon EKS clusters running version 1.18 with platform version <code>eks.3</code> or later because add-ons rely on the Server-side Apply Kubernetes feature, which is only available in Kubernetes 1.18 and later.</p>",
- "CreateCluster": "<p>Creates an Amazon EKS control plane. </p> <p>The Amazon EKS control plane consists of control plane instances that run the Kubernetes software, such as <code>etcd</code> and the API server. The control plane runs in an account managed by AWS, and the Kubernetes API is exposed via the Amazon EKS API server endpoint. Each Amazon EKS cluster control plane is single-tenant and unique and runs on its own set of Amazon EC2 instances.</p> <p>The cluster control plane is provisioned across multiple Availability Zones and fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC subnets to provide connectivity from the control plane instances to the nodes (for example, to support <code>kubectl exec</code>, <code>logs</code>, and <code>proxy</code> data flows).</p> <p>Amazon EKS nodes run in your AWS account and connect to your cluster's control plane via the Kubernetes API server endpoint and a certificate file that is created for your cluster.</p> <p>You can use the <code>endpointPublicAccess</code> and <code>endpointPrivateAccess</code> parameters to enable or disable public and private access to your cluster's Kubernetes API server endpoint. By default, public access is enabled, and private access is disabled. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html\">Amazon EKS Cluster Endpoint Access Control</a> in the <i> <i>Amazon EKS User Guide</i> </i>. </p> <p>You can use the <code>logging</code> parameter to enable or disable exporting the Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster control plane logs aren't exported to CloudWatch Logs. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html\">Amazon EKS Cluster Control Plane Logs</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p> <note> <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see <a href=\"http:https://aws.amazon.com/cloudwatch/pricing/\">Amazon CloudWatch Pricing</a>.</p> </note> <p>Cluster creation typically takes between 10 and 15 minutes. After you create an Amazon EKS cluster, you must configure your Kubernetes tooling to communicate with the API server and launch nodes into your cluster. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/managing-auth.html\">Managing Cluster Authentication</a> and <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html\">Launching Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>",
+ "CreateCluster": "<p>Creates an Amazon EKS control plane. </p> <p>The Amazon EKS control plane consists of control plane instances that run the Kubernetes software, such as <code>etcd</code> and the API server. The control plane runs in an account managed by AWS, and the Kubernetes API is exposed via the Amazon EKS API server endpoint. Each Amazon EKS cluster control plane is single-tenant and unique and runs on its own set of Amazon EC2 instances.</p> <p>The cluster control plane is provisioned across multiple Availability Zones and fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC subnets to provide connectivity from the control plane instances to the nodes (for example, to support <code>kubectl exec</code>, <code>logs</code>, and <code>proxy</code> data flows).</p> <p>Amazon EKS nodes run in your AWS account and connect to your cluster's control plane via the Kubernetes API server endpoint and a certificate file that is created for your cluster.</p> <p>Cluster creation typically takes several minutes. After you create an Amazon EKS cluster, you must configure your Kubernetes tooling to communicate with the API server and launch nodes into your cluster. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/managing-auth.html\">Managing Cluster Authentication</a> and <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html\">Launching Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>",
  "CreateFargateProfile": "<p>Creates an AWS Fargate profile for your Amazon EKS cluster. You must have at least one Fargate profile in a cluster to be able to run pods on Fargate.</p> <p>The Fargate profile allows an administrator to declare which pods run on Fargate and specify which pods run on which Fargate profile. This declaration is done through the profile’s selectors. Each profile can have up to five selectors that contain a namespace and labels. A namespace is required for every selector. The label field consists of multiple optional key-value pairs. Pods that match the selectors are scheduled on Fargate. If a to-be-scheduled pod matches any of the selectors in the Fargate profile, then that pod is run on Fargate.</p> <p>When you create a Fargate profile, you must specify a pod execution role to use with the pods that are scheduled with the profile. This role is added to the cluster's Kubernetes <a href=\"https://kubernetes.io/docs/admin/authorization/rbac/\">Role Based Access Control</a> (RBAC) for authorization so that the <code>kubelet</code> that is running on the Fargate infrastructure can register with your Amazon EKS cluster so that it can appear in your cluster as a node. The pod execution role also provides IAM permissions to the Fargate infrastructure to allow read access to Amazon ECR image repositories. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html\">Pod Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p> <p>Fargate profiles are immutable. However, you can create a new updated profile to replace an existing profile and then delete the original after the updated profile has finished creating.</p> <p>If any Fargate profiles in a cluster are in the <code>DELETING</code> status, you must wait for that Fargate profile to finish deleting before you can create any other profiles in that cluster.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html\">AWS Fargate Profile</a> in the <i>Amazon EKS User Guide</i>.</p>",
  "CreateNodegroup": "<p>Creates a managed node group for an Amazon EKS cluster. You can only create a node group for your cluster that is equal to the current Kubernetes version for the cluster. All node groups are created with the latest AMI release version for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using a launch template. For more information about using launch templates, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a>.</p> <p>An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that are managed by AWS for an Amazon EKS cluster. Each node group uses a version of the Amazon EKS optimized Amazon Linux 2 AMI. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html\">Managed Node Groups</a> in the <i>Amazon EKS User Guide</i>. </p>",
  "DeleteAddon": "<p>Delete an Amazon EKS add-on.</p> <p>When you remove the add-on, it will also be deleted from the cluster. You can always manually start an add-on on the cluster using the Kubernetes API.</p>",
@@ -104,6 +105,16 @@
  "DescribeAddonVersionsResponse$addons": "<p>The list of available versions with Kubernetes version compatibility.</p>"
  }
  },
+ "AssociateEncryptionConfigRequest": {
+ "base": null,
+ "refs": {
+ }
+ },
+ "AssociateEncryptionConfigResponse": {
+ "base": null,
+ "refs": {
+ }
+ },
  "AssociateIdentityProviderConfigRequest": {
  "base": null,
  "refs": {
@@ -394,6 +405,7 @@
  "EncryptionConfigList": {
  "base": null,
  "refs": {
+ "AssociateEncryptionConfigRequest$encryptionConfig": "<p>The configuration you are using for encryption.</p>",
  "Cluster$encryptionConfig": "<p>The encryption configuration for the cluster.</p>",
  "CreateClusterRequest$encryptionConfig": "<p>The encryption configuration for the cluster.</p>"
  }
@@ -781,6 +793,8 @@
  "AddonInfo$type": "<p>The type of the add-on.</p>",
  "AddonIssue$message": "<p>A message that provides details about the issue and what might cause it.</p>",
  "AddonVersionInfo$addonVersion": "<p>The version of the add-on.</p>",
+ "AssociateEncryptionConfigRequest$clusterName": "<p>The name of the cluster that you are associating with encryption configuration.</p>",
+ "AssociateEncryptionConfigRequest$clientRequestToken": "<p>The client request token you are using with the encryption configuration.</p>",
  "AssociateIdentityProviderConfigRequest$clusterName": "<p>The name of the cluster to associate the configuration to.</p>",
  "AssociateIdentityProviderConfigRequest$clientRequestToken": "<p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the request.</p>",
  "AutoScalingGroup$name": "<p>The name of the Auto Scaling group associated with an Amazon EKS managed node group.</p>",
@@ -1061,6 +1075,7 @@
  "Update": {
  "base": "<p>An object representing an asynchronous update.</p>",
  "refs": {
+ "AssociateEncryptionConfigResponse$update": null,
  "AssociateIdentityProviderConfigResponse$update": null,
  "DescribeUpdateResponse$update": "<p>The full description of the specified update.</p>",
  "DisassociateIdentityProviderConfigResponse$update": null,

models/apis/elasticmapreduce/2009-03-31/api-2.json

@@ -562,6 +562,18 @@
  {"shape":"InternalServerError"}
  ]
  },
+ "UpdateStudio":{
+ "name":"UpdateStudio",
+ "http":{
+ "method":"POST",
+ "requestUri":"/"
+ },
+ "input":{"shape":"UpdateStudioInput"},
+ "errors":[
+ {"shape":"InternalServerException"},
+ {"shape":"InvalidRequestException"}
+ ]
+ },
  "UpdateStudioSessionMapping":{
  "name":"UpdateStudioSessionMapping",
  "http":{
@@ -1035,7 +1047,8 @@
  "ServiceRole",
  "UserRole",
  "WorkspaceSecurityGroupId",
- "EngineSecurityGroupId"
+ "EngineSecurityGroupId",
+ "DefaultS3Location"
  ],
  "members":{
  "Name":{"shape":"XmlStringMaxLen256"},
@@ -2836,6 +2849,17 @@
  "COUNT_PER_SECOND"
  ]
  },
+ "UpdateStudioInput":{
+ "type":"structure",
+ "required":["StudioId"],
+ "members":{
+ "StudioId":{"shape":"XmlStringMaxLen256"},
+ "Name":{"shape":"XmlStringMaxLen256"},
+ "Description":{"shape":"XmlStringMaxLen256"},
+ "SubnetIds":{"shape":"SubnetIdList"},
+ "DefaultS3Location":{"shape":"XmlString"}
+ }
+ },
  "UpdateStudioSessionMappingInput":{
  "type":"structure",
  "required":[