Periodic update, May 2018, which includes support for custom build environments for the .NET framework

Author: markiver

doc_source/auth-and-access-control-iam-access-control-identity-based.md

@@ -65,7 +65,7 @@ A permissions policy describes who has access to which resources\.
 **Note**  
 This section discusses the use of IAM in AWS CodeBuild\. It doesn't provide detailed information about the IAM service\. For complete IAM documentation, see [What Is IAM?](http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) in the *IAM User Guide Guide*\. For information about IAM policy syntax and descriptions, see [AWS IAM Policy Reference](http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide Guide*\.
 
-Policies attached to an IAM identity are referred to as identity\-based policies \(IAM polices\)\. Policies attached to a resource are referred to as resource\-based policies\. AWS CodeBuild supports identity\-based \(IAM policies\) only\.
+Policies attached to an IAM identity are referred to as identity\-based policies \(IAM policies\)\. Policies attached to a resource are referred to as resource\-based policies\. AWS CodeBuild supports identity\-based \(IAM policies\) only\.
 
 ### Identity\-Based Policies \(IAM Policies\)<a name="identity-based-policies"></a>
 

doc_source/build-env-ref-available.md

@@ -31,6 +31,7 @@ If you do not find your image on this page, it most likely contains components t
 | Ubuntu 14\.04 | Ruby | 2\.2\.5 | aws/codebuild/ruby:2\.2\.5 | [ubuntu/ruby/2\.2\.5](https://github.com/aws/aws-codebuild-docker-images/tree/master/ubuntu/ruby/2.2.5) | 
 | Ubuntu 14\.04 | \.NET Core | 1\.1 | aws/codebuild/dot\-net:core\-1 | [ubuntu/dot\-net/core\-1](https://github.com/aws/aws-codebuild-docker-images/tree/master/ubuntu/dot-net/core-1) | 
 | Ubuntu 14\.04 | \.NET Core | 2\.0 | aws/codebuild/dot\-net:core\-2\.0 | [ubuntu/dot\-net/core\-2](https://github.com/aws/aws-codebuild-docker-images/tree/master/ubuntu/dot-net/core-2) | 
+| Windows Server Core 2016 | \(Base Image\) |  | aws/codebuild/windows\-base:1\.0 |  | 
 
 AWS CodeBuild also manages the following Docker images that are not in the AWS CodeBuild and AWS CodePipeline consoles\.
 
@@ -89,6 +90,8 @@ AWS CodeBuild frequently updates the list of Docker images\. To get the most cur
 + For the AWS SDKs, call the `ListCuratedEnvironmentImages` operation for your target programming language\. For more information, see the [AWS SDKs and Tools Reference](sdk-ref.md)\.
 
 To confirm the version of a component installed on a Docker image, you can run a command during a build\. The version number for the component will appear in the output\. For example, include one or more of the following commands in your build specification:
++ For the Microsoft \.NET Framework, run `reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP"`\.
++ For \.NET Core, run `dotnet --version`\.
 + For Apache Ant, run `ant -version`\.
 + For Apache Maven, run `mvn -version`\.
 + For the AWS CLI, run `aws --version`\.

doc_source/build-env-ref-env-vars.md

@@ -21,8 +21,8 @@ You can also provide build environments with your own environment variables\. Fo
 + [Run a Build](run-build.md)
 + [Build Spec Reference](build-spec-ref.md)
 
+To list all of the available environment variables in a build environment, you can run the `printenv` command \(for Linux\-based build environment\) or `"Get-ChildItem Env:"` \(for Windows\-based build environments\) during a build\. With the exception of those previously listed, environment variables that start with `CODEBUILD_` are for AWS CodeBuild internal use\. They should not be used in your build commands\.
+
 **Important**  
 We strongly discourage using environment variables to store sensitive values, especially AWS access key IDs and secret access keys\. Environment variables can be displayed in plain text using tools such as the AWS CodeBuild console and the AWS CLI\.  
-For sensitive values, we recommend you store them in the Amazon EC2 Systems Manager Parameter Store and then retrieve them from your build spec\. To store sensitive values, see [Systems Manager Parameter Store](http://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-paramstore.html) and [Systems Manager Parameter Store Console Walkthrough](http://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-walk.html#sysman-paramstore-console) in the *Amazon EC2 Systems Manager User Guide*\. To retrieve them, see the `parameter-store` mapping in [Build Spec Syntax](build-spec-ref.md#build-spec-ref-syntax)\.
-
-To list all of the available environment variables in a build environment, you can run the `printenv` command during a build\. With the exception of those previously listed, environment variables that start with `CODEBUILD_` are for AWS CodeBuild internal use\. They should not be used in your build commands\.
+For sensitive values, we recommend you store them in the Amazon EC2 Systems Manager Parameter Store and then retrieve them from your build spec\. To store sensitive values, see [Systems Manager Parameter Store](http://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-paramstore.html) and [Systems Manager Parameter Store Console Walkthrough](http://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-walk.html#sysman-paramstore-console) in the *Amazon EC2 Systems Manager User Guide*\. To retrieve them, see the `parameter-store` mapping in [Build Spec Syntax](build-spec-ref.md#build-spec-ref-syntax)\.

doc_source/how-to-create-pipeline.md

@@ -134,7 +134,7 @@ If you enable webhooks for an AWS CodeBuild project, and the project is used as
 
 1. For **Build specification**, do one of the following:
    + If your source code includes a build spec file, choose **Use the buildspec\.yml in the source code root directory**\. 
-   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment; for multiple commands, separate each command with `&&`\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline; for multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
+   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment; for multiple commands, separate each command with `&&` for Linux\-based build environments or `;` for Windows\-based build environments\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline; for multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
 
 1. For **AWS CodeBuild service role**, do one of the following:
    + If you do not have an AWS CodeBuild service role in your AWS account, choose **Create a service role in your account**\. In the **Role name** box, type a name for the service role or leave the suggested name\. \(Service role names must be unique across your AWS account\.\) 
@@ -434,7 +434,7 @@ If you enable webhooks for an AWS CodeBuild project, and the project is used as
 
 1. For **Build specification**, do one of the following:
    + If your source code includes a build spec file, choose **Use the buildspec\.yml in the source code root directory**\. 
-   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment; for multiple commands, separate each command with `&&`\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline; for multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
+   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment; for multiple commands, separate each command with `&&` for Linux\-based build environments or `;` for Windows\-based build environments\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline; for multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
 
 1. For **AWS CodeBuild service role**, do one of the following:
    + If you do not have an AWS CodeBuild service role in your AWS account, choose **Create a service role in your account**\. In the **Role name** box, type a name for the service role or leave the suggested name\. \(Service role names must be unique across your AWS account\.\) 
@@ -573,7 +573,7 @@ If you enable webhooks for an AWS CodeBuild project, and the project is used as
 
 1. For **Build specification**, do one of the following:
    + If your source code includes a build spec file, choose **Use the buildspec\.yml in the source code root directory**\. 
-   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment\. For multiple commands, separate each command with `&&`\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline\. For multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
+   + If your source code does not include a build spec file, choose **Insert build commands**\. For **Build command**, type the commands you want to run during the build phase in the build environment\. For multiple commands, separate each command with `&&` for Linux\-based build environments or `;` for Windows\-based build environments\. For **Output files**, type the paths to the build output files in the build environment that you want to send to AWS CodePipeline\. For multiple files, separate each file path with a comma\. For more information, see the tooltips in the console\.
 
 1. For **AWS CodeBuild service role**, do one of the following:
    + If you do not have an AWS CodeBuild service role in your AWS account, choose **Create a service role in your account**\. In the **Role name** box, type a name for the service role or leave the suggested name\. \(Service role names must be unique across your AWS account\.\) 

doc_source/index.md

@@ -18,6 +18,7 @@ Amazon's trademarks and trade dress may not be used in
    + [AWS CodeBuild Concepts](concepts.md)
 + [Getting Started with AWS CodeBuild](getting-started.md)
 + [AWS CodeBuild Samples](samples.md)
+   + [Microsoft Windows Samples for AWS CodeBuild](sample-windows.md)
    + [AWS CodeBuild Use Case-Based Samples](use-case-based-samples.md)
       + [Amazon ECR Sample for AWS CodeBuild](sample-ecr.md)
       + [Docker Sample for AWS CodeBuild](sample-docker.md)
@@ -82,5 +83,6 @@ Amazon's trademarks and trade dress may not be used in
    + [Logging AWS CodeBuild API Calls with AWS CloudTrail](cloudtrail.md)
 + [Troubleshooting AWS CodeBuild](troubleshooting.md)
 + [Limits for AWS CodeBuild](limits.md)
++ [AWS CodeBuild for Windows—Third Party Notices](notice.md)
 + [AWS CodeBuild User Guide Document History](history.md)
 + [AWS Glossary](glossary.md)