public String getRegion() {
        return this.region;
    }
<p>
The stack's Amazon Web Services Region, such as <code>ap-south-1</code>. For more information about Amazon Web
Services Regions, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html">Regions and
Endpoints</a>.
</p>
<note>
<p>
In the CLI, this API maps to the <code>--stack-region</code> parameter. If the <code>--stack-region</code>
parameter and the CLI common parameter <code>--region</code> are set to the same value, the stack uses a
<i>regional</i> endpoint. If the <code>--stack-region</code> parameter is not set, but the CLI
<code>--region</code> parameter is, this also results in a stack with a <i>regional</i> endpoint. However, if the
<code>--region</code> parameter is set to <code>us-east-1</code>, and the <code>--stack-region</code> parameter
is set to one of the following, then the stack uses a legacy or <i>classic</i> region:
<code>us-west-1, us-west-2, sa-east-1, eu-central-1, eu-west-1, ap-northeast-1, ap-southeast-1, ap-southeast-2</code>
. In this case, the actual API endpoint of the stack is in <code>us-east-1</code>. Only the preceding regions are
supported as classic regions in the <code>us-east-1</code> API endpoint. Because it is a best practice to choose
the regional endpoint that is closest to where you manage Amazon Web Services, we recommend that you use regional
endpoints for new stacks. The CLI common <code>--region</code> parameter always specifies a regional API
endpoint; it cannot be used to specify a classic OpsWorks Stacks region.
</p>
</note>

@return The stack's Amazon Web Services Region, such as <code>ap-south-1</code>. For more information about
        Amazon Web Services Regions, see <a
        href="https://docs.aws.amazon.com/general/latest/gr/rande.html">Regions and Endpoints</a>.</p> <note>
        <p>
        In the CLI, this API maps to the <code>--stack-region</code> parameter. If the
        <code>--stack-region</code> parameter and the CLI common parameter <code>--region</code> are set to the
        same value, the stack uses a <i>regional</i> endpoint. If the <code>--stack-region</code> parameter is
        not set, but the CLI <code>--region</code> parameter is, this also results in a stack with a
        <i>regional</i> endpoint. However, if the <code>--region</code> parameter is set to
        <code>us-east-1</code>, and the <code>--stack-region</code> parameter is set to one of the following,
        then the stack uses a legacy or <i>classic</i> region:
        <code>us-west-1, us-west-2, sa-east-1, eu-central-1, eu-west-1, ap-northeast-1, ap-southeast-1, ap-southeast-2</code>
        . In this case, the actual API endpoint of the stack is in <code>us-east-1</code>. Only the preceding
        regions are supported as classic regions in the <code>us-east-1</code> API endpoint. Because it is a best
        practice to choose the regional endpoint that is closest to where you manage Amazon Web Services, we
        recommend that you use regional endpoints for new stacks. The CLI common <code>--region</code> parameter
        always specifies a regional API endpoint; it cannot be used to specify a classic OpsWorks Stacks region.
        </p>
aws-java-sdk-opsworks/src/main/java/com/amazonaws/services/opsworks/model/CreateStackRequest.java