AWSのまとめ

[まとめページに戻る](https://qiita.com/Keiji_otsubo/items/60afc2a8d211b6f7d89f)
[まとめA～M](https://qiita.com/Keiji_otsubo/items/f3ddedee6793bf1576f8)


+ [Data Cloud でのAmazonS3 接続](https://qiita.com/Keiji_otsubo/items/33ddd7bfc09f3c9280b7)

+ [event relays : イベントリレー](https://qiita.com/Keiji_otsubo/items/3ff2e633e156f182071a)
+ [AWS を使用する製品の IP アドレスを許可リストに登録するより良い方法はありますか?](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007ZA9sl)

:::note
Looks like this is still an idea:

Publish all Salesforce IP Ranges available via a JSON endpoint
https://ideas.salesforce.com/s/idea/a0B8W00000GdZ2GUAV/publish-all-salesforce-ip-ranges-available-via-a-json-endpoint

AWS publishes its current IP address ranges in JSON format. With this information, you can identify traffic from AWS. You can also use this information to allow or deny traffic to or from some AWS services.

https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html
:::

+ [AWS S3 API Callout using Named Credentials Not Working And Gives Script Thrown Error As Output](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007epy6b)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/63f3877c-1085-b58f-b428-b8a8a1415e71.png)

:::note

Script-thrown exception" error on HTTP callouts to AWS as of Spring ’22
https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007epy6b
:::

# Endpoint needs to be in full URL form

+ [Does Event Relays to EventBridge requires Legacy Named Credentials? arn:aws URL from docs is rejected.](https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007cmLG7)

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/328136/7048ffe0-8478-6c0d-da57-90f475d74329.png)


# Please export all the three AWS credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN) and paste it to terminal (please use https://docs.aws.amazon.com/keyspaces/latest/devguide/access.credentials.html to generate it)

+ [【未解決】Unable to Create S3 file notification](https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000PW50G)

# 403 error

+ [Error while sending message to AWS SQS using Apex](https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000PX9gg)


:::note alert
ERROR: Status: Forbidden
Code  : 403
Body  : <?xml version="1.0"?><ErrorResponse xmlns="http://queue.amazonaws.com/doc/2012-11-05/

"><Error><Type>Sender</Type><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. 
:::

:::note
I can confirm that recreating my access keys until I got one without special characters in it, worked. What a ridiculous bug, wow. 

Seeing as this is such a long running issue, would it not be intelligent to update the error messaging to give users a link to a potential fix, like rebuilding your keys? Instead of something which makes out that the issue is far more complex than "yeah we error out when your keys have special chars in them, sorry!". 

Got the same error today, currently using Windows 10. However, when I use the same access key on another laptop (mac), it works fine for me. Then I tried the access key within WSL, which is also fine. Not sure the reason, and there is no special character in the aws key. 

https://github.com/aws/aws-cli/issues/602
:::