Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,044
Community Members
 
Community Events
176
Community Groups

aws-cloudfront-invalidate got error IncompleteSignature

  • 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.

1 answer

@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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events