Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

aws-cloudfront-invalidate got error IncompleteSignature

Hiroki Shiotsuka
Hiroki Shiotsuka Dec 20, 2022
  • the version of the pipe
    atlassian/aws-cloudfront-invalidate:0.6.0
  • relevant logs and error messages
    ERROR: Error creating a cloudfront invalidation
    ✖ Failed to create a cloudfront invalidation: An error occurred (IncompleteSignature) when calling the CreateInvalidation operation: 'AKIA4LZ7CWVXOKZ3RLXH/20221221/us-east-1/cloudfront/aws4_request' not a valid key=value pair (missing equal-sign) in Authorization header: 'AWS4-HMAC-SHA256 Credential=$AWS_ACCESS_KEY_ID/20221221/us-east-1/cloudfront/aws4_request, SignedHeaders=host;x-amz-date, Signature=9049558d7c9cb5c790b5cc51638a91add394d385128dae6e37300bae62680891'.
  • steps to reproduce
    - pipe: atlassian/aws-cloudfront-invalidate:0.6.0
      variables:
        AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
        AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
        AWS_DEFAULT_REGION: 'us-east-1'
        DISTRIBUTION_ID: '{my-distribution-id}'
        PATHS: '/*'

    Please help.

Answer
Watch
Like Be the first to like this
321 views

1 answer

0 votes
Igor Stoyanov
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 23, 2022 • edited

@Hiroki Shiotsuka  hi. Thanks for your question. Please, check this issue.

Maybe there is a whitespace in the KEY value.

 

Seems like the same problem here.

 

Regards, Igor

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events