{"title":"AWS S3 Signature Changes","slug":"aws-s3-signature-changes","body":"Hello PlanGrid developers,\n\nIn keeping up with industry standards, our infrastructure team will transition from AWS S3 SigV2 to SigV4 for all file uploads to PlanGrid. You can read more about Amazon’s transition plan to SigV4 [here](https://aws.amazon.com/blogs/aws/amazon-s3-update-sigv2-deprecation-period-extended-modified/).\n\nOur team will make the transition to adhere to Amazon’s recommendations on **August 1, 2020**. This transition will affect all file uploads to PlanGrid, including but not limited to sheets, documents, and photos.\n\n## Which integrations are affected?\nIf your integration uploads files to PlanGrid, please read the notes below to see if you may need to update your integration.\n\n## How does the transition affect the API?\nUploading files to PlanGrid entails a multi-step process that includes the following:\n\n1. POST the file attribute data and content type to PlanGrid’s API. A successful call will respond with a **File Upload Object**.\n\n2. The **File Upload Object** will contain an `aws_post_form_arguments.fields` array containing the key-value pairs used to POST the file to AWS S3.\n\nDuring step 2 of the upload process above, we recommend (*and continue to recommend*) using the key-value pairs _**as they are provided**_ in the File Upload Object to POST the file to AWS S3. We understand that some partners may have hard-coded the keys into their integration.\n\nWith the transition, the key-value pairs will change to those recommended by SigV4. Specifically, certain keys, such as `AWSAccessKeyId` and `Signature`, will no longer be valid.\n\n## Does this affect my integration?\nIf your integration __contains hard-coded keys when uploading to AWS S3__, including `AWSAccessKeyId` and `Signature`, __your integration will need instead to use the key-value pairs *as they are provided*__ within the File Upload Object.\n\nIf your integration does not contain any hard-coded keys when uploading to AWS S3 and is already built to use the key-value pairs as they are provided in the File Upload Object, your integration will not be affected and no further action is required.\n\n## We’re here to help!\nWe want to make this transition as easy as possible for customers and make sure your integrations are future-proof from infrastructure changes such as these.\n\nIf you are unsure how your integration is uploading files to PlanGrid, please reach out to us immediately at [[email protected]](mailto:[email protected]).","_id":"5e3d8a46773d5700579e9ee6","project":"55d2023b3c74062300aee506","initVersion":{"version":"1.16","_id":"5cdde55205114d005d1abf1e"},"user":{"name":"Sophat Sam","username":"","_id":"57db49de0678030e008a76f8"},"createdAt":"2020-02-07T16:03:18.109Z","changelog":[],"__v":0}

AWS S3 Signature Changes


Hello PlanGrid developers, In keeping up with industry standards, our infrastructure team will transition from AWS S3 SigV2 to SigV4 for all file uploads to PlanGrid. You can read more about Amazon’s transition plan to SigV4 [here](https://aws.amazon.com/blogs/aws/amazon-s3-update-sigv2-deprecation-period-extended-modified/). Our team will make the transition to adhere to Amazon’s recommendations on **August 1, 2020**. This transition will affect all file uploads to PlanGrid, including but not limited to sheets, documents, and photos. ## Which integrations are affected? If your integration uploads files to PlanGrid, please read the notes below to see if you may need to update your integration. ## How does the transition affect the API? Uploading files to PlanGrid entails a multi-step process that includes the following: 1. POST the file attribute data and content type to PlanGrid’s API. A successful call will respond with a **File Upload Object**. 2. The **File Upload Object** will contain an `aws_post_form_arguments.fields` array containing the key-value pairs used to POST the file to AWS S3. During step 2 of the upload process above, we recommend (*and continue to recommend*) using the key-value pairs _**as they are provided**_ in the File Upload Object to POST the file to AWS S3. We understand that some partners may have hard-coded the keys into their integration. With the transition, the key-value pairs will change to those recommended by SigV4. Specifically, certain keys, such as `AWSAccessKeyId` and `Signature`, will no longer be valid. ## Does this affect my integration? If your integration __contains hard-coded keys when uploading to AWS S3__, including `AWSAccessKeyId` and `Signature`, __your integration will need instead to use the key-value pairs *as they are provided*__ within the File Upload Object. If your integration does not contain any hard-coded keys when uploading to AWS S3 and is already built to use the key-value pairs as they are provided in the File Upload Object, your integration will not be affected and no further action is required. ## We’re here to help! We want to make this transition as easy as possible for customers and make sure your integrations are future-proof from infrastructure changes such as these. If you are unsure how your integration is uploading files to PlanGrid, please reach out to us immediately at [[email protected]](mailto:[email protected]).