I have IAM roles like Editor/Cloud Run Admin in my gcp projects (multiple Projects) I am facing this issue,
When I am trying to deploy the container image from Cloud Run's "Edit & Deploy New Revision" screen.
It's not listing the Images in the Project and gives error refer this screenshot for the error message .
Its not only for me other users also facing same issue, but with the same editor and admin roles I am able to list all images in the other project. I have also checked with other developers
If the "Artifact Registry API" is enabled in GCP. then we can list the images from the project.
To enable this API, Search for 'Artifact Registry API' and click enable.
Only if you have this 'Service Usage Admin' IAM role, you can enable API.
Thanks to my Support Team in Project
Related
I am following this tutorial for creating a React app in AWS.
In step Initialize the Amplify app of section 3, I see the following error (i.e. Setting up Admin UI failed.) in the Backend environments tab:
I know that I have a limited account from our administration side, but I don't know what role is missing that I cannot create the backend for my app!
Does anyone have any idea that, how I can find out what role is missing that I am not allowed to create the Amplify Backend?
Also in the console tab no info is printed.
I had the same problem when I tried to deploy from the Admin UI sandbox app, as a ROOT user on my AWS account. I fixed it after I went to Billing and completed the payment info requirements.
Before that I couldn't even access DynamoDB tables (which are used by AWS Amplify and Admin UI).
If this doesn't work, you can try having Amplify and maybe DynamoDB related roles enabled in IAM for your user.
You can start with these roles:
AdministratorAccess-Amplify
AmazonDynamoDBFullAccess
I am a total GCP noob - I've literally just signed up to use one of the APIs.
I tried to follow these steps from here , but got stuck when trying to enable the APIs.
I came across this, which tells me: You need permission serviceusage.services.enable on the project and permission servicemanagement.services.bind on the API to enable it.
There is a link with information on it, but this means nothing to me. I have managed to find and IAM & Admin page for my project, but can't find a way to do the above.
All help is appreciated.
To enable the API on you GCP project follow the steps :-
I. Go to dashboard
II. From Navigation Menu go to "API and Services" dashboard and then click on “Enable API and Services”
III. Search for the APIs you need to enable(Cloud IOT, Dataflow API, Cloud Pub/Sub)
IV. Then click on enable API
From "IAM and Admin" page you get the service credentials key or json key which enables you to access you gcp project from command line interface.
To get the service credentials key follow the steps :-
I. Go to the link for getting service key : https://console.cloud.google.com/apis/credentials/serviceaccountkey
II. Under the heading of “Service Account” select a new service account and then give a name to your service account and select the role as owner{Project<Owner}.
III. Under the key type select JSON and click on ‘Create’
IV. A file will be automatically downloaded on your device.
I am the owner of a project and want to give Permissions to another user to view Logs of Google Cloud Build, but I can not figure out which Role / Permission this user needs.
Roles I've unsuccessfully tried are:
Cloud Build Editor,
Cloud Build Viewer,
Stackdriver Debugger Agent,
Stackdriver Debugger User,
Cloud Trace Admin,
Logging Admin,
Private Logs Viewer,
Logs Viewer,
Monitoring Admin
Google Cloud enterprise support confirmed to me that the only role that currently grants this is the project-level Viewer permission (or Editor/Owner).
One workaround is to set the --gcs-log-dir flag when submitting a build to a bucket you control (rather than the default Google-managed gs://[PROJECT_NUMBER].cloudbuild-logs.googleusercontent.com/ bucket).
They're tracking making a more granular permission in this feature request: https://issuetracker.google.com/issues/134928412, which you can subscribe to updates on.
If you add the project viewer role then this will resolve the issue. But, it seems like this is an issue (or maybe a feature request - to add the necessary permission to the Logs Viewer so that logs outside of the Stackdriver logging page can be viewed in other UIs as well), looking at the documentation it says "roles/viewer (Project Viewer) gives members the same permissions as roles/logging.viewer at the project level. " which means that by just assigning the Logs Viewer then it should have given the user the necessary permission to view the logs at the Cloud Build UI.
I am building an app with technologies I'm not familiar with (sails.js, AWS). I am trying to set up CI between Bitbucket and an AWS Ubuntu EC2 instance.
I have created a couple of repositories in Bitbucket and I am the owner of these repositories. The instructions I have found say that you need to log in to Bitbucket as an admin and click on the admin link. For some reason, I cannot see an admin link in Bitbucket.
Why is this? Do I need to create an admin account? Why can't the owner see the admin link in Bitbucket?
I am trying to create a Container Cluster in Google Container Engine using the console (UI).
I am getting the below error while creating a cluster of size - 3 of machine type "n1-standard-1"
"xxxxxxxxxxx#cloudservices.gserviceaccount.com" does not have edit permissions on project "xxxx-xxxxxx-xxxxxx".
I have already enabled the API's related to Container management :-
Google Cloud Container Builder API
Google Container Engine API
Also, I haven't created a service account as given in the error "xxxxxxxxxxx#cloudservices.gserviceaccount.com" . I don't know about this service-account? what is this used for? and who created it?
Though I have another service account, which is different from the one shown in error, it has all the edit permissions to my project.
The xxxxxxxxxxx#cloudservices.gserviceaccount.com is the service account that Google Container Engine uses to create the resources for your cluster. You'll need to make sure that it has "Editor" role in the permissions section of your GCP project.