vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Dallas (us-south) syslog://syslog-u.us-south.logging.cloud.ibm.com 52.116.247.173 <br>169.60.203.92 <br>67.228.102.116 
 Frankfurt (eu-de) syslog://syslog-u.eu-de.logging.cloud.ibm.com 161.156.78.139 <br>149.81.108.30 <br>158.177.143.26 
 London (eu-gb) syslog://syslog-u.eu-gb.logging.cloud.ibm.com 158.175.66.210 <br>158.176.163.156 <br>141.125.140.98 
 Osaka (jp-osa) syslog://syslog-u.jp-osa.logging.cloud.ibm.com 163.69.68.70 <br>163.73.68.46 <br>163.68.72.219 
 Sao Paulo (br-sao) syslog://syslog-u.br-sao.logging.cloud.ibm.com 169.57.152.196 <br>163.107.69.14 <br>163.109.68.100 
 Sydney (au-syd) syslog://syslog-u.au-syd.logging.cloud.ibm.com 135.90.92.253 <br>168.1.27.59 <br>130.198.71.30 
 Tokyo (jp-tok) syslog://syslog-u.jp-tok.logging.cloud.ibm.com 165.192.100.76 <br>169.56.11.252 <br>128.168.107.244 
 Toronto (ca-tor) syslog://syslog-u.ca-tor.logging.cloud.ibm.com 163.75.66.11 <br>169.55.135.29 <br>163.74.69.236
Osaka jp-osa osa22 10.9.32.255/25 10.9.32.129 
 Osaka jp-osa osa22 10.9.6.207/29 10.9.6.201 
 Osaka jp-osa osa22 10.9.6.215/29 10.9.6.209 
 Osaka jp-osa osa23 10.10.12.255/26 10.10.12.193 
 Osaka jp-osa osa23 10.10.28.255/25 10.10.28.129 
 Osaka jp-osa osa23 10.10.8.7/29 10.10.8.1 
 Osaka jp-osa osa23 10.10.8.15/29 10.10.8.9 









 us-east List 



 Public Subnets 



Table 15. us-east Public Subnets

 Location Region Data center Subnet First IP 

 Washington DC us-east wdc04 52.116.78.127/25 52.116.78.1 
 Washington DC us-east wdc04 52.116.115.255/24 52.116.115.1 
 Washington DC us-east wdc04 150.239.70.255/24 150.239.70.1 
 Washington DC us-east wdc04 150.239.101.255/24 150.239.101.1 
 Washington DC us-east wdc04 150.239.107.255/24 150.239.107.1 
 Washington DC us-east wdc04 169.47.179.63/26 169.47.179.1 
 Washington DC us-east wdc04 169.63.72.175/28 169.63.72.161 
 Washington DC us-east wdc04 169.63.83.255/24 169.63.83.1 
 Washington DC us-east wdc04 169.63.121.159/27 169.63.121.129 
 Washington DC us-east wdc04 52.116.73.231/29 52.116.73.225
Dallas (us-south) api.private.us-south.logging.cloud.ibm.com 166.9.16.11 <br>166.9.12.12 <br>166.9.14.2<br><br>166.9.90.41 () <br>166.9.85.89 () <br>166.9.61.79 () TCP 443 <br>TCP 80 
 Frankfurt (eu-de) api.private.eu-de.logging.cloud.ibm.com 166.9.32.7 <br>166.9.28.2 <br>166.9.30.231<br><br>166.9.30.45 () <br>166.9.28.159 () <br>166.9.32.117 () TCP 443 <br>TCP 80 
 London (eu-gb) api.private.eu-gb.logging.cloud.ibm.com 166.9.36.2 <br>166.9.38.4 <br>166.9.34.2<br><br>166.9.36.105 () <br>166.9.34.79 () <br>166.9.38.84 () TCP 443 <br>TCP 80 
 Osaka (jp-osa) api.private.jp-osa.logging.cloud.ibm.com 166.9.71.21 <br>166.9.72.19 <br>166.9.70.19<br><br>166.9.71.14 () <br>166.9.72.13 () <br>166.9.70.13 () TCP 443 <br>TCP 80 
 Sao Paulo (br-sao) api.private.br-sao.logging.cloud.ibm.com 166.9.83.24 <br>166.9.82.23 <br>166.9.84.25<br><br>166.9.83.12 () <br>166.9.82.12 () <br>166.9.84.12 () TCP 443 <br>TCP 80
<br><br> * [ibm_event_streams_schema](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/event_streams_schema)<br> * [ibm_event_streams_topic](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/event_streams_topic)<br><br><br> <br><br> * [ibm_event_streams_schema](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/event_streams_schema)<br> * [ibm_event_streams_topic](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/event_streams_topic)<br><br><br> 







 Functions 



 Resources Data sources
Dallas (us-south) syslog-tls://syslog-a.us-south.logging.cloud.ibm.com 52.116.247.170 <br>52.117.134.206 <br>67.228.102.117 
 Frankfurt (eu-de) syslog-tls://syslog-a.eu-de.logging.cloud.ibm.com 161.156.78.138 <br>158.177.157.70 <br>149.81.108.28 
 London (eu-gb) syslog-tls://syslog-a.eu-gb.logging.cloud.ibm.com 158.176.163.115 <br>141.125.102.148 <br>158.175.113.22 
 Osaka (jp-osa) syslog-tls://syslog-a.jp-osa.logging.cloud.ibm.com 163.69.67.210 <br>163.68.72.220 <br>163.73.68.45 
 Sao Paulo (br-sao) syslog-tls://syslog-a.br-sao.logging.cloud.ibm.com 169.57.254.118 <br>163.107.68.195 <br>163.109.68.109 
 Sydney (au-syd) syslog-tls://syslog-a.au-syd.logging.cloud.ibm.com 135.90.92.254 <br>168.1.202.76 <br>130.198.1.210 
 Tokyo (jp-tok) syslog-tls://syslog-a.jp-tok.logging.cloud.ibm.com 128.168.95.2 <br>161.202.248.162 <br>165.192.100.77 
 Toronto (ca-tor) syslog-tls://syslog-a.ca-tor.logging.cloud.ibm.com 163.75.66.13 <br>163.74.69.234 <br>169.53.186.154
Dallas us-south dal13 169.62.239.47/29 169.62.239.41 
 Dallas us-south dal13 169.62.240.223/29 169.62.240.217 
 Dallas us-south dal13 169.62.240.231/29 169.62.240.225 
 Dallas us-south dal13 174.36.70.143/29 174.36.70.137 







 Private Subnets 



Table 20. us-south Private Subnets

 Location Region Data center Subnet First IP 

 Dallas us-south dal10 10.5.5.255/24 10.5.5.1 
 Dallas us-south dal10 10.5.124.255/24 10.5.124.1 
 Dallas us-south dal10 10.5.204.255/24 10.5.204.1 
 Dallas us-south dal10 10.23.68.255/24 10.23.68.1 
 Dallas us-south dal10 10.38.177.255/24 10.38.177.1 
 Dallas us-south dal10 10.94.35.255/24 10.94.35.1 
 Dallas us-south dal10 10.95.108.191/26 10.95.108.129 
 Dallas us-south dal10 10.95.123.255/24 10.95.123.1 
 Dallas us-south dal10 10.95.170.255/25 10.95.170.129 
 Dallas us-south dal10 10.95.191.255/24 10.95.191.1 
 Dallas us-south dal10 10.95.225.255/24 10.95.225.1 
 Dallas us-south dal10 10.171.25.255/24 10.171.25.1 
 Dallas us-south dal10 10.171.186.255/24 10.171.186.1 
 Dallas us-south dal10 10.171.209.191/26 10.171.209.129 
 Dallas us-south dal10 10.177.109.127/25 10.177.109.1 
 Dallas us-south dal10 10.177.238.255/24 10.177.238.1
* The [Cloud Databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin) - the CLI interface to interact with the [Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-api/cloud-databases-api-v5introduction). For more information, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/databases-cli-plugin).
* A Cloud Databases deployment. For more information, see [Provisioning](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-provisioning).
* Review the [What are context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatis) docs to get an understanding of concepts of network zones and rules.
* Review the [Protecting Cloud Databases resources with context-based restrictions](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-cbr) docs to understand how you can leverage CBR for your Cloud Databases resources.







 Step 1: Creating your network zone in the CLI 

[Provision your service from the IBM Cloud Catalog](https://cloud.ibm.com/catalog/services/databases-for-mysql) and choose your IP addresses from the [Cloud Databases Allowlist page](https://cloud.ibm.com/docs/databases-for-mysql?topic=cloud-databases-allowlisting).



1. Run the following example command to create a network that includes a range of allowed IP addresses.
Frankfurt (eu-de) syslog-tls://syslog-a.private.eu-de.logging.cloud.ibm.com 166.9.28.5 <br>166.9.32.23 <br>166.9.30.236 
 London (eu-gb) syslog-tls://syslog-a.private.eu-gb.logging.cloud.ibm.com 166.9.34.18 <br>166.9.36.5 <br>166.9.38.20 
 Osaka (jp-osa) syslog-tls://syslog-a.private.jp-osa.logging.cloud.ibm.com 166.9.72.22 <br>166.9.71.22 <br>166.9.70.22 
 Sao Paulo (br-sao) syslog-tls://syslog-a.private.br-sao.logging.cloud.ibm.com 166.9.82.26 <br>166.9.83.22 <br>166.9.84.23 
 Sydney (au-syd) syslog-tls://syslog-a.private.au-syd.logging.cloud.ibm.com 166.9.52.8 <br>166.9.56.22 <br>166.9.54.124 
 Tokyo (jp-tok) syslog-tls://syslog-a.private.jp-tok.logging.cloud.ibm.com 166.9.40.23 <br>166.9.42.26 <br>166.9.44.67 
 Toronto (ca-tor) syslog-tls://syslog-a.private.ca-tor.logging.cloud.ibm.com 166.9.76.31 <br>166.9.78.29 <br>166.9.77.28 
 Washington (us-east) syslog-tls://syslog-a.private.us-east.logging.cloud.ibm.com 166.9.22.38 <br>166.9.20.76 <br>166.9.24.243
Sydney au-syd syd05 135.90.68.111/28 135.90.68.97 
 Sydney au-syd syd05 135.90.69.127/27 135.90.69.97 
 Sydney au-syd syd05 135.90.83.63/26 135.90.83.1 
 Sydney au-syd syd05 135.90.95.127/25 135.90.95.1 
 Sydney au-syd syd05 135.90.108.255/24 135.90.108.1 
 Sydney au-syd syd05 135.90.67.31/29 135.90.67.25 
 Sydney au-syd syd05 135.90.67.135/29 135.90.67.129 
 Sydney au-syd syd05 135.90.68.39/29 135.90.68.33 







 Private Subnets 



Table 10. au-syd Private Subnets

 Location Region Data center Subnet First IP 

 Sydney au-syd syd01 10.138.220.255/25 10.138.220.129 
 Sydney au-syd syd01 10.139.40.63/26 10.139.40.1 
 Sydney au-syd syd01 10.139.61.255/24 10.139.61.1 
 Sydney au-syd syd01 10.138.152.63/29 10.138.152.57 
 Sydney au-syd syd01 10.138.172.175/29 10.138.172.169 
 Sydney au-syd syd01 10.138.172.183/29 10.138.172.177 
 Sydney au-syd syd04 10.63.110.255/25 10.63.110.129 
 Sydney au-syd syd04 10.63.212.127/26 10.63.212.65 
 Sydney au-syd syd04 10.63.244.255/24 10.63.244.1 
 Sydney au-syd syd04 10.63.4.255/29 10.63.4.249
The following events are for working with Cloud connections in your Power Systems Virtual Server instance.



Table 13. List of events: Cloud connections

 Action Description 

 power-iaas.cloud-connection.read Read a Cloud Connection or all Cloud Connections 
 power-iaas.cloud-connection.create Create a Cloud Connection 
 power-iaas.cloud-connection.update Update a Cloud Connection 
 power-iaas.cloud-connection.delete Delete a Cloud Connection 







 List of events: Placement Groups 

The following events are for working with placement groups in your Power Systems Virtual Server instance.



Table 14. List of events: Placement groups

 Action Description 

 power-iaas.placement-groups.read Read a Placement Group or all Placement Groups 
 power-iaas.placement-groups.create Create a Placement Group 
 power-iaas.placement-groups.update Update a Placement Group 
 power-iaas.placement-groups.delete Delete a Placement Group 







 List of events: IKE Policy 

The following events are for working with IKE Policy in your Power Systems Virtual Server instance.



Table 15. List of events: IKE policy

 Action Description 

 power-iaas.ike-policy.read Read an IKE Policy 
 power-iaas.ike-policy.create Create an IKE Policy 
 power-iaas.ike-policy.update Update an IKE Policy 
 power-iaas.ike-policy.delete Delete an IKE Policy 







 List of events: IPSec Policy 

The following events are for working with IPsec Policy in your Power Systems Virtual Server instance.



Table 16. List of events: IPsec policy

 Action Description 

 power-iaas.ipsec-policy.read Read an IPsec Policy 
 power-iaas.ipsec-policy.create Create an IPsec Policy 
 power-iaas.ipsec-policy.update Update an IPsec Policy 
 power-iaas.ipsec-policy.delete Delete an IPsec Policy 







 List of events: VPN Connection 

The following events are for working with VPN Connection in your Power Systems Virtual Server instance.



Table 17. List of events: VPN Connection

 Action Description
"pools": [],
"private_ips": [
{
"address": "10.241.64.13"
},
{
"address": "10.241.64.14"
}
],
"provisioning_status": "active",
"public_ips": [],
"subnets": [
{
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"href": "https://us-east.iaas.cloud.ibm.com/v1/subnets/0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::subnet:0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"name": "nlb-subnet"
}
],
"resource_group": {
"id": "42c4f51adc3147b4b4049ad9826c30a1",
"href": "https://resource-controller.cloud.ibm.com/v1/resource_groups/42c4f51adc3147b4b4049ad9826c30a1",
"name": "Default"
},
"resource_type": "load_balancer",
"logging": {
"datapath": {
"active": false
}
},
"profile": {
Chennai (in-che) syslog://syslog-u.private.in-che.logging.cloud.ibm.com 166.9.60.10 
 Dallas (us-south) syslog://syslog-u.private.us-south.logging.cloud.ibm.com 166.9.14.6 <br>166.9.16.15 <br>166.9.12.16 
 Frankfurt (eu-de) syslog://syslog-u.private.eu-de.logging.cloud.ibm.com 166.9.28.7 <br>166.9.32.24 <br>166.9.30.239 
 London (eu-gb) syslog://syslog-u.private.eu-gb.logging.cloud.ibm.com 166.9.36.6 <br>166.9.38.21 <br>166.9.34.19 
 Osaka (jp-osa) syslog://syslog-u.private.jp-osa.logging.cloud.ibm.com 166.9.70.23 <br>166.9.72.23 <br>166.9.71.23 
 Sao Paulo (br-sao) syslog://syslog-u.private.br-sao.logging.cloud.ibm.com 166.9.83.26 <br>166.9.84.26 <br>166.9.82.27 
 Sydney (au-syd) syslog://syslog-u.private.au-syd.logging.cloud.ibm.com 166.9.56.23 <br>166.9.52.9 <br>166.9.54.115 
 Tokyo (jp-tok) syslog://syslog-u.private.jp-tok.logging.cloud.ibm.com 166.9.42.27 <br>166.9.40.24 <br>166.9.44.73
London (eu-gb) syslog-a.private.eu-gb.logging.cloud.ibm.com 166.9.38.20 <br>166.9.34.18 <br>166.9.36.5 
 Osaka (jp-osa) syslog-a.private.jp-osa.logging.cloud.ibm.com 166.9.70.22 <br>166.9.71.22 <br>166.9.72.22 
 Sao Paulo (br-sao) syslog-a.private.br-sao.logging.cloud.ibm.com 166.9.82.26 <br>166.9.83.22 <br>166.9.84.23 
 Sydney (au-syd) syslog-a.private.au-syd.logging.cloud.ibm.com 166.9.52.8 <br>166.9.56.22 <br>166.9.54.124 
 Tokyo (jp-tok) syslog-a.private.jp-tok.logging.cloud.ibm.com 166.9.42.26 <br>166.9.40.23 <br>166.9.44.67 
 Toronto (ca-tor) syslog-a.private.ca-tor.logging.cloud.ibm.com 166.9.76.31 <br>166.9.77.28 <br>166.9.78.29 
 Washington (us-east) syslog-a.private.us-east.logging.cloud.ibm.com 166.9.22.38 <br>166.9.20.76 <br>166.9.24.243 





Table 7. List of syslog-u public endpoints

 Region Public Endpoint IP addresses 

 Chennai (in-che) syslog://syslog-u.private.in-che.logging.cloud.ibm.com 166.9.60.10 
 Dallas (us-south) syslog://syslog-u.private.us-south.logging.cloud.ibm.com 166.9.14.6 <br>166.9.16.15 <br>166.9.12.16
* [Watch a particular resource in my Satellite Config version](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resourcessatconfig-enable-watchkeeper-specific)
* [Watch a particular resource that I label in my cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resourcessatconfig-enable-watchkeeper-label)



* [Review the resources from Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resourcessatconfig-review-resources)



* [Reviewing resources from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resourcessatconfig-review-resources-console)
* [Reviewing resources with the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resourcessatconfig-review-resources-cli)











 Connecting Satellite locations with external services by using Link endpoints 

[Understanding Link endpoints and Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-location-cloud)



* [Architecture](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-architecture)



* [Cloud endpoint](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-cloud-endpoint)
* [Location endpoint](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-location-endpoint)



* [External network requirements and security](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-security)



* [Do I need to allow any unique inbound traffic from internet-facing ports through firewalls to my location?](https://cloud.ibm.com/docs/satellite?topic=satellite-link-location-cloudlink-unique-inbound)
* Machine Data Analytics Splitter extractors have been removed and will disappear from the canvas. There is no substitute for these extractors that is provided by the new tokenizer.



* Generic Splitters:



* Date Time Splitter
* Day First Splitter
* Month First Splitter
* Year First Splitter



* Syslog Splitter:



* Date Time Splitter







: Cross-sentence relations (Experimental)



* English entities and relations workspaces can now support annotating relations between entities within spans of six sentences. To get started, see [Enabling cross-sentence relations](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-enabling-cross-sentence-relations).



: Full support for IBM Cloud IAM



* Knowledge Studio now supports the full implementation of IBM Cloud Identity and Access Management (IAM). API keys for Watson services are no longer limited to a single service instance. You can create access policies and API keys that apply to more than one service, and you can grant access between services.
* For more information about IAM, see [Authenticating to Watson services](https://cloud.ibm.com/docs/watson?topic=watson-iam).
* To support this change, the API service endpoints use a different domain and include the service instance ID. The pattern is api.{location}.{offering}.watson.cloud.ibm.com/instances/{instance_id}.

The previous public endpoint domain was watsonplatform.net.

These URLs do not introduce a breaking change. The new URLs work both for your existing service instances and for new instances. The original URLs continue to work on your existing service instances for at least one year (until December 2020).





 Region Old New 

 Dallas gateway.watsonplatform.net us-south.knowledge-studio.watson.cloud.ibm.com 
 Frankfurt gateway-fra.watsonplatform.net eu-de.knowledge-studio.watson.cloud.ibm.com 
 Sydney gateway-syd.watsonplatform.net au-syd.knowledge-studio.watson.cloud.ibm.com
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727",
"name": "example-balancer",
"created_at": "2018-07-13T22:22:24.489Z",
"hostname": "dd754295-e9e0-4c9d-bf6c-58fbc59e5727.lb.appdomain.cloud",
"is_public": true,
"logging": {
"datapath": {
"active": true
}
},
"listeners": [
{
"id": "0738-70294e14-4e61-11e8-bcf4-0242ac110004",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727/listeners/70294e14-4e61-11e8-bcf4-0242ac110004"
}
],
"operating_status": "online",
"pools": [
{
"id": "0738-70294e14-4e61-11e8-bcf4-0242ac110004",
"href": "https://us-south.iaas.cloud.ibm.com/v1/load_balancers/dd754295-e9e0-4c9d-bf6c-58fbc59e5727/pools/70294e14-4e61-11e8-bcf4-0242ac110004",
"name": "example-pool"
}
],
"private_ips": [
{
For example, you might use a [Virtual Private Network (VPN) for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-example) or [IBM Cloud® Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dlget-started-with-direct-link-connect).

Connect to other public clouds?
: Yes. With Satellite Link, you can create cloud endpoints for resources that run in other public clouds.





 Example: Connect from a Satellite location to a service in another cloud provider 

You want to send data from a server that runs on a host in your Satellite location to a service that runs in Amazon Web Services. The service must be publicly accessible so that the Satellite Link tunnel, which terminates within the IBM Cloud network, can access the service in the AWS network.

To establish this connection, you first create a cloud endpoint. You specify the service that runs in AWS as the destination resource. Then, the server on your on-location host connects directly to the host name of the Satellite Link connector on your location's control plane worker nodes. Satellite Link forwards this request to the cloud endpoint that you created for the service that runs in AWS.





 Example: Enable and audit limited access to a Satellite location from IBM Cloud 

You run a database in your Satellite location instead of in IBM Cloud, because the database has legal requirements to run in your on-premises data center in a specific country. However, you still need to connect to the database in your Satellite location from the IBM Cloud private network.

To establish this connection, you first create a location endpoint. You specify the database that runs in your Satellite location as the destination resource. Then, the client in the IBM Cloud private network connects directly to the host name of the Satellite Link tunnel server. Satellite Link forwards this request to the location endpoint that you created for your on-location database.

Finally, to maintain enterprise security and audit compliance, you specify a list of source IP ranges so that only trusted clients in the public cloud can access your on-location database through the endpoint.
--description DESCRIPTION
: Optional. A description of the Satellite location.

--ha-zone ZONE1_NAME --ha-zone ZONE2_NAME --ha-zone ZONE3_NAME
: Specify three names for high availability zones in your location. The names of the zones must match exactly the names of the corresponding zones in your infrastructure provider where you plan to create hosts, such as a cloud provider zone or on-prem rack. To retrieve the name of the zone, consult your infrastructure provider.



1. [Alibaba regions and zones](https://www.alibabacloud.com/help/en/elastic-compute-service/latest/regions-and-zones), such as us-east-1 and us-west-1.
2. [AWS regions and zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html), such as us-east-1a, us-east-1b, us-east-1c.
3. [Azure topology.kubernetes.io/zone labels](https://docs.microsoft.com/en-us/azure/aks/availability-zonesverify-node-distribution-across-zones), such as eastus-1, eastus-2, and eastus-3. Do not use only the location name (eastus) or the zone number (1).
4. [GCP regions and zones](https://cloud.google.com/compute/docs/regions-zones), such as us-west1-a, us-west1-b, and us-west1-c.



: Optional: If you use this option, zone names must be specified in three repeated options. If you do not use this option, the zones in your location are assigned names, such as zone-1.

--coreos-enabled
: Optional. Enable [Red Hat CoreOS](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os) features within the Satellite location.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Speech to Text ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 Power IaaS services 

Americas

Asia Pacific

Europe



Table 16. Power IaaS events in Americas locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 Images ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) Events are available through the Activity Tracker Dallas (us-south) instance. 
 Networks !
The following schema examples represent the data that you need to specify for some command options. These examples show the data structure and include placeholder values for the expected value types. When you run a command, replace these values with the values that apply to your environment as appropriate.



 KeyProperties 

The following example shows the format of the KeyProperties object.

{
"size" : "256",
"algorithm" : "aes",
"activation_date" : "P5Y1M1W2D",
"expiration_date" : "P1Y2M1W4D",
"state" : "active"
}





 KeyPropertiesUpdate 

The following example shows the format of the KeyPropertiesUpdate object.

{
"size" : "256",
"activation_date" : "P5Y1M1W2D",
"expiration_date" : "P1Y2M1W4D",
"state" : "active"
}





 KeystoreCreationRequest 

The following example shows the format of the KeystoreCreationRequest object.

{
"type" : "aws_kms",
"vault" : {
"id" : "5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"name" : "IBM Cloud Keystore Name",
"description" : "Azure keystore",
"groups" : [ "Production" ],
"aws_region" : "af_south_1",
"aws_access_key_id" : "BSDFWERUANLKJDN54AAS",
"aws_secret_access_key" : "6HSz234KBjMrASFasfg5PasAFGNasg87asdgQzgs"
}





 KeystoreUpdateRequest 

The following example shows the format of the KeystoreUpdateRequest object.

{
"name" : "IBM Cloud Keystore Name",