terraform/website/docs/configuration/functions/base64sha512.html.md

---
layout: "language"
page_title: "base64sha512 - Functions - Configuration Language"
sidebar_current: "docs-funcs-crypto-base64sha512"
description: |-
  The base64sha512 function computes the SHA512 hash of a given string and
  encodes it with Base64.
---

# `base64sha512` Function

-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
earlier, see
[0.11 Configuration Language: Interpolation Syntax](../../configuration-0-11/interpolation.html).

`base64sha512` computes the SHA512 hash of a given string and encodes it with
Base64. This is not equivalent to `base64encode(sha512("test"))` since `sha512()`
returns hexadecimal representation. 

The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
then encoded with Base64 before returning. Terraform uses the "standard" Base64
alphabet as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).

## Examples

```
> base64sha512("hello world")
MJ7MSJwS1utMxA9QyQLytNDtd+5RGnx6m808qG1M2G+YndNbxf9JlnDaNCVbRbDP2DDoH2Bdz33FVC6TrpzXbw==
```

## Related Functions

* [`filebase64sha512`](./filebase64sha512.html) calculates the same hash from
  the contents of a file rather than from a string value.
* [`sha512`](./sha512.html) calculates the same hash but returns the result
  in a more-verbose hexadecimal encoding.
website: Docs for all of the hash/crypto functions 2018-05-13 22:48:45 +02:00			`---`
website: Adopt a ton of pages into the "language" layout As of this commit, that layout doesn't exist yet, but I'm isolating the one-line changes to their own commit to try and keep your eyes from glazing over. 2020-08-15 03:51:06 +02:00			`layout: "language"`
website: Update functions section page titles 2018-12-20 05:35:11 +01:00			`page_title: "base64sha512 - Functions - Configuration Language"`
website: Docs for all of the hash/crypto functions 2018-05-13 22:48:45 +02:00			`sidebar_current: "docs-funcs-crypto-base64sha512"`
			`description: \|-`
			`The base64sha512 function computes the SHA512 hash of a given string and`
			`encodes it with Base64.`
			`---`

			# `base64sha512` Function

website: Version notes: Add new -> old links to 0.12 language docs (function pages) 2019-01-17 01:33:57 +01:00			`-> Note: This page is about Terraform 0.12 and later. For Terraform 0.11 and`
			`earlier, see`
			`[0.11 Configuration Language: Interpolation Syntax](../../configuration-0-11/interpolation.html).`

website: Docs for all of the hash/crypto functions 2018-05-13 22:48:45 +02:00			`base64sha512` computes the SHA512 hash of a given string and encodes it with
website: Fix typographical errors in the docs for base64sha256/512 2019-11-08 18:43:27 +01:00			Base64. This is not equivalent to `base64encode(sha512("test"))` since `sha512()`
porting crypto functions 2018-05-23 18:16:42 +02:00			`returns hexadecimal representation.`
website: Docs for all of the hash/crypto functions 2018-05-13 22:48:45 +02:00
			`The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied`
			`as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is`
			`then encoded with Base64 before returning. Terraform uses the "standard" Base64`
			`alphabet as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).`

			`## Examples`

			```
			`> base64sha512("hello world")`
			`MJ7MSJwS1utMxA9QyQLytNDtd+5RGnx6m808qG1M2G+YndNbxf9JlnDaNCVbRbDP2DDoH2Bdz33FVC6TrpzXbw==`
			```

			`## Related Functions`

lang: New file-hashing functions In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation. 2019-01-25 18:16:43 +01:00			* [`filebase64sha512`](./filebase64sha512.html) calculates the same hash from
			`the contents of a file rather than from a string value.`
website: Docs for all of the hash/crypto functions 2018-05-13 22:48:45 +02:00			* [`sha512`](./sha512.html) calculates the same hash but returns the result
			`in a more-verbose hexadecimal encoding.`