Launchpad AWS API keys not valid

l.carstens

I am currently trying to set up a DF instance via Launchpad.
After having done so once the instance was deleted, I believe because the relevant tagging is currently not supported in the Sandbox environment.

Trying to set-up again I am now unable to do so, getting a notification that my AWS API keys are not valid (I have entered the session key).

Re-generating the keys does not solve the problem.

Any advise on how to get set up would be much appreciated.

l.carstens

The issue seems to have been caused not because of invalid keys, but rather by the S3 bucket limit having been reached on the FR-Sandbox instance.

You can test for this by trying to create a test bucket with AWS CLI, using something like the following command:

aws --profile saml s3api create-bucket --bucket df-test.

The issue has been resolved by requesting an increase in the maximum bucket count (via the AWS support center).

l.carstens

Thanks for pointing that out, my apologies!

Eric.Helgeson

Launchpad validates keys by trying to create a S3 bucket - where it will store the state of the cluster in when it begins building with terraform. Could you validate you can use your keys via the AWS CLI tools and then try again? Another reason may be a errant space before or after the key (there is a fix going out shortly to trim keys).

l.carstens

I've made sure there are no trailing spaces anywhere.

The keys generated seem invalid, since I'm getting errors using the CLI as well.

As mentioned it has worked before using the process described on the Hub.

Eric.Helgeson

The keys only last 1 hour after created. You re-generated them correct? - I might suggest you reach out to the TR AWS team and see why they're not working.

l.carstens

Hi Eric,

Yes, I've re-generated them.

I will try and reach out to the TR AWS team.