search

awslabs / fargatecli

CLI for AWS Fargate
Apache License 2.0
893 stars 114 forks source link

Creating a service fails with previously working setup #38

Closed edipetres closed 6 years ago

edipetres commented 6 years ago

I have been successfully using fargate for a while now, an awesome tool by the way!

However, yesterday it started throwing an error as if my credentials were not set up right:

[!] Could not create Cloudwatch Logs log group
SubscriptionRequiredException: The AWS Access Key Id needs a subscription for the service
    status code: 400, request id: 7f6464c9-16fe-11e8-b99d-2d585cda5bb0

I checked that the permissions on the AWS account did not change and the environment variables are available (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY) in the shell.

Since I have not changed anything in the environment where I ran the commands, I'm not sure what went wrong. Do you have any idea where else could the issue lie?

jpignata commented 6 years ago

Hmm, I haven't seen that before. That API error appears to indicate an account issue. Can you ensure your account is in good standing by logging in and looking on the billing panel for any kind of alert?

On Wed, Feb 21, 2018 at 7:05 AM Edmond Petres notifications@github.com wrote:

I have been successfully using fargate for a while now, an awesome tool by the way!

However, yesterday it started throwing an error as if my credentials were not set up right:

[!] Could not create Cloudwatch Logs log group SubscriptionRequiredException: The AWS Access Key Id needs a subscription for the service status code: 400, request id: 7f6464c9-16fe-11e8-b99d-2d585cda5bb0

I checked that the permissions on the AWS account did not change and the environment variables are available (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY) in the shell.

Since I have not changed anything in the environment where I ran the commands, I'm not sure what went wrong. Do you have any idea where else could the issue lie?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jpignata/fargate/issues/38, or mute the thread https://github.com/notifications/unsubscribe-auth/AABNP4wIKg0c3QN4Y0LPJRvhNJ4rkntKks5tXAadgaJpZM4SNhiM .

edipetres commented 6 years ago

Thank you for the quick response. The problem went away now, but could not trace back the exact issue, but I'm guessing it might have had something to do with the policies. Anyway, closing this for now, keep up the good work!