Tuesday, June 21, 2022
HomeCyber Securityimporting to S3 deadly error: Parameter validation failed | by Teri Radichel...

importing to S3 deadly error: Parameter validation failed | by Teri Radichel | Bugs That Chew | Jun, 2022


Invalid bucket title when the bucket exists

Let’s say you get this error making an attempt to add to an S3 bucket to a bucket already exists and also you’re certain the bucket title is appropriate. Can you see the error?

importing to S3deadly error: Parameter validation failed:Invalid bucket title ""yours3bucketnamehere"": Bucket title should match the regex "^[a-zA-Z0-9.-_]{1,255}$" or be an ARN matching the regex "^arn:(aws).*:(s3|s3-object-lambda):[a-z-0-9]*:[0-9]{12}:accesspoint[/:][a-zA-Z0-9-.]{1,63}$|^arn:(aws).*:s3-outposts:[a-z-0-9]+:[0-9]{12}:outpost[/:][a-zA-Z0-9-]{1,63}[/:]accesspoint[/:][a-zA-Z0-9-]{1,63}$"

That is associated to a different submit the place you find yourself with quotes round a price you’re making an attempt to make use of in a concatenated string or move into one other perform. It’s a widespread prevalence for me with AWS Methods Supervisor Parameter retailer. While you retrieve the parameter it at all times has double quotes round it and in some circumstances that leads to the worth. You’ll be able to’t see the quotes whenever you merely print out the parameter worth as I defined in one other submit, however you may if you happen to do one thing like this:

echo "'"$parameter_value"'"

Then you definitely’ll see the quotes:

'"the_value"'

In my case, I retrieved a bucket title from parameter retailer and concatenated it with another values to get the total bucket path:

bucket_repo_folder='s3://'$bucket'/repo'

Should you echo the worth of bucket_repo_folder you get:

s3://"bucket_name_value"/repo

You’ll want to take away these further double quotes earlier than you concatenate. I try this with sed:

bucket_repo_folder='s3://'$bucket'/repo' | sed 's/"//g"

Now your bucket title is appropriate:

s3://bucket_name_value/repo

Working AWS CLI instructions on packer

I received this error on an AMI the place I had IAM credentials working beforehand. The explanation was as a result of I moved my AMI constructing course of to a separate account for higher segregation of duties.

I used to be utilizing the choice iam_instance_profile after which setting the worth to the title of an occasion profile. I hadn’t but arrange the corresponding function profile for Packer in my new account.

This feature to make use of a task profile with Packer seems within the documentation right here:

That is an error you would possibly get associated to utilizing this feature:

Could not discover specified occasion profile: RequestError: ship request failed brought on by: Put up "https://iam.amazonaws.com/": Proxy Authentication Required

What occurred in my case is that once I got here again to repair it I couldn’t instantly discover the documentation for the iam_instance_profile possibility, however I discovered this feature for including an AWS IAM Position to the template. It permits you to add an exterior ID which is an added layer of safety with cross-account roles:

The issue with this new performance is that it appears it’s a must to present an AWS entry key and secret key in addition to a task to make use of this. The entire level of utilizing a task was to keep away from having the key key and entry key hanging round.

I went again to strive the IAM_INSTANCE_PROFILE possibility once more. I figured I have to be doing one thing flawed. At first I couldn’t get it to work, however then I noticed I didn’t take away the exterior ID used with the opposite IAM Position possibility once I reverted to the IAM_INSTANCE_PROFILE possibility.

I took the exterior ID out of the belief coverage (leaving the belief coverage that enables an EC2 occasion to imagine the function) in my IAM Position and it labored.

Repair: When the exterior ID is lacking give a extra applicable error message. The credentials are usually not lacking, they're simply misconfigured. Maybe that is by design to not give attackers further data but it surely makes it arduous to troubleshoot as effectively.

If this helped you otherwise you had this drawback, please clap!

Teri Radichel — Comply with me @teriradichel on Twitter

© 2nd Sight Lab 2022

____________________________________________

About this weblog:

Wish to be taught extra about Cybersecurity and Cloud Safety? Try: Cybersecurity for Executives within the Age of Cloud on Amazon

Want Cloud Safety Coaching? 2nd Sight Lab Cloud Safety Coaching

Is your cloud safe? Rent 2nd Sight Lab for a penetration check or safety evaluation.

Have a Cybersecurity or Cloud Safety Query? Ask Teri Radichel by scheduling a name with IANS Analysis.

Cybersecurity & Cloud Safety Assets by Teri Radichel: Cybersecurity and Cloud safety lessons, articles, white papers, shows, and podcasts



RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments