Improved support for non standard AWS partitions (experimental)

The non standard AWS regions China (Beijing) and AWS GovCloud (US) have been enabled for use already. However, due to not being based in either China or the US, we are not in a position to test this add-on with those regions directly. Thanks to feedback from users with access to those regions we have identified some resulting inconsistencies and bugs, which have been addressed by being more explicit about the underlying AWS partition concept (see the info box below for some background) – here is what you need to know about this change:

Non standard AWS partitions and their regions are now disabled by default and must explicitly be opted into as outlined in Enabling Labs Features.
- If you are Providing AWS Security Credentials via Identity Federation for AWS, the non standard partition must be enabled in both add-ons!
- If you have been using the China (Beijing) region before, you need to opt-in again as outlined in Support for the AWS China partition – existing tasks are not affected at runtime, however, the China (Beijing) region is not offered in the region widget anymore by default.
Once enabled, you need to specify the appropriate partition when Configuring an AWS Access Key so that the add-on can use the partition specific AWS endpoints at runtime.
- Since most AWS users won't have access to non standard AWS regions, the Partition option is hidden until any non standard AWS partition is enabled.

What is an AWS partition?

The AWS partition concept pretty much lacks documentation so far and is only mentioned in passing here and there, most notably within Amazon Resource Names (ARNs) and AWS Service Namespaces:

”partition – The partition that the resource is in. For standard AWS regions, the partition is aws. If you have resources in other partitions, the partition is aws-partitionname. For example, the partition for resources in the China (Beijing) region is aws-cn.”

Browser not supported