- Newest
- Most votes
- Most comments
Based on the provided sources, there is no explicit mention of policy variables in the format ${aws:region} or ${aws:account:id}.
When specifying AWS regions and account IDs in resource policies, the documentation consistently shows that you should directly replace placeholders like <region>, <account-id>, or Region and Account with the actual values rather than using policy variables with the ${} syntax.
For example, in resource policies for AWS services like Lambda, Redshift, SMS/Voice, and Glue, the examples show that you need to manually substitute these values in the ARN format:
arn:aws:redshift:{region}:{account-id}:namespace:namespace-uuidarn:aws:sms-voice:Region:Account:sender-id/SenderID/ISOarn:aws:glue:<region>:<account-id>:catalog
None of the policy examples in the sources demonstrate the use of policy variables with the ${} syntax for region or account ID.
Sources
Managing cross-account permissions using both AWS Glue and Lake Formation - AWS Lake Formation
Lambda - AWS IoT Core
Simplify data integration using zero-ETL from Amazon RDS to Amazon Redshift | AWS Database Blog
"NO_ORIGINATION_IDENTITIES_FOUND" error when trying to send messages via SNS or Pinpoint even though the required origination identity is acquired in the account. | AWS re:Post
Access data in Amazon S3 Tables using PyIceberg through the AWS Glue Iceberg REST endpoint | AWS Storage Blog
answered a year ago
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
