I am working on aws cloud and using codecommit service. I want to set up git-remote-codecommit tool on my ubuntu OS. but it give me error.
Here I was trying to follow following document.
https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-git-remote-codecommit.html as federated user.
I added version information about OS and other required tools.
But after doing all this when try to execute
git clone codecommit: command it throws fatal error.
Can someone help me, what is root cause for this and how can I solve this issue.
Welcome to AWS Codecommit, it is a great service but has its quirks.
First question for you is have you configured your IAM role properly to have STS Assume role access? If you have not done that this role will not work with the federation. I would need to see a sample of your IAM role before I can help you debug the issue.
Additionally i am providing this link which walks you through the setup for federated roles: https://aws.amazon.com/blogs/devops/using-federated-identities-with-aws-codecommit/
Related
How to set up multiple account code commit?
I am able to set for the only single user.
I am getting below error
Please make sure you have the correct access rights and the repository
exists
Sorry to hear about that. Can you describe more about the workflow you're trying to achieve through multi account access?
In the meantime, here's a link that explains how to achieve cross account access to CodeCommit if that helps: https://docs.aws.amazon.com/codecommit/latest/userguide/cross-account.html
Hopefully someone has an answer to my question.
I'm trying to connect to another instance of drupal using deploy and relaxed web services.
However, I keep getting this error
{"message":"The following permissions are required: \u0027restful get relaxed:root\u0027 OR \u0027perform push replication\u0027 OR \u0027perform pull replication\u0027."}
Does anyone have any idea why?
It's a local windows version of drupal (bitnami stack) that i have installed, trying to connect to another drupal version on a linux server.
Can this be the problem?
oversight on my part. There is a replicator role that i forgot to check which solved this issue.
Be sure that passwords are saved correctly in "Config > Web services > Relaxed settings" and for the replicator user role. Check that for both environment (staging and live).
It solved my case.
(If needed, delete the before saved data and create new ones.)
I'm trying to use the boxr package to link my box account to R-Server.
I get as far in the box_auth() instructions as step 3 from the box pdf https://cran.r-project.org/web/packages/boxr/boxr.pdf
A window pops up and I authorise connection then I get the error 'Safari can't connect to the server'.
I have no knowledge of how apache or web development works so forgive my naivety, I've come to understand the problem is I don't have localhost set up on my Mac.
I'm unable to turn these features on because it requires admin rights and my company won't allow users to have this.
Is there something else I can put in the redirect_uri box apart from localhost that will allow this to authenticate?
Thanks
The issue i had was mostly that authenticating box through R-Server isn't supported. https://github.com/brendan-r/boxr/issues/23
To get around this I used my personal laptop to authenticate locally then uploaded the .Renviron and .boxr-oauth files to R server (which is the advice in the github post)
This was slightly tricky as R wasn't showing the .boxr-oauth file but I managed to copy it to a folder, zip the folder, then upload that to R-Server.
Now running the box_auth() function authenticates as it should.
As of v0.3.5 (November 2019) boxr has a new alternative authentication method designed for remote servers, box_auth_service(), that closes issue 23. It's slightly is different than the oAuth way, because it uses "Service" accounts as the actors instead of the "User" account. But the "Service" accounts are what's needed to maintain security within a organization, so we opted for that. Please open an issue on the repo if you run into any issues.
While deploying WordPress in azure,I had met with an Failed Notification specifying the following:
Type:SuccessBricks.ClearDB/databases
Status:Bad Request
Properties:
statusCode:BadRequest
serviceRequestId:
statusMessage:{"error":{"code":"MissingMarketplacePlanPublisher","message":"The marketplace resource plan is missing required \"publisher\" property."}}
I have tried deploying new wordpress app,but still the same failed message is shown.
Try deploying it from the classic Azure services manager instead https://manage.windowsazure.com. I was having the same problem. It might be related to your database name. The classic interface required my database name be less than 16 characters, while the Azure portal let me type over that, but failed during deployment.
Also, make sure you're not using a VS MSDN subscription. I don't think you can use your free credits towards ClearDB MySQL. Alternatively, you could install MySQL on a linux server and pay for compute time out of your MSDN subscription.
Edited: FYI, I contacted CloudSQL about the error and received the following:
Thanks for contacting us, and our apologies for the inconvenience. There
currently is an issue that the Azure Marketplace is experiencing that is
causing this to happen. The Azure UI team is aware of the problem and is
working to resolve it today.
Thanks very much for your patience - this should be resolved soon.
My CodeDeploy deployment is failing. Usually I'm able to see the event list on each instances, and see which ones failed/passed.
This no longer works, and the event list is empty. What could be causing this?
As Jonathan Turpie mentions, you should probably troubleshoot if the instance is taking care of your deployment.
You could first try to troubleshoot via AWS CLI, aws deploy get-deployment --deployment-id d-USUAELQEX. It might return error codes that will help you to tweak your setting and succeed with your deployment. See http://docs.aws.amazon.com/cli/latest/reference/deploy/get-deployment.html
If your EC2 instance actually handles the deployment. Edit the /etc/codedeploy-agent/conf/codedeployagent.yml and set :verbose: to true on your EC2 instance.
Try to deploy again and open codedeploy-agent.log at /var/log/aws/codedeploy-agent and see if you are able to see anything there. Read more here: http://docs.aws.amazon.com/codedeploy/latest/userguide/host-cleanup.html
You may not be able to see events if the deployment didn't get far enough. For example, there was a problem getting the list of instances due to IAM configuration or your instance isn't responding to commands.
Check the codedeploy-agent-log.txt file. it might have some more info about the underground issue. in a windows machine you find it under
C:\ProgramData\Amazon\CodeDeploy\log
As mentioned by Jonathan, you might not have the right configuration for your IAM configurations. Check that your IAM role has the policy "AWSCodeDeployRole".
This happens when the code deploy agent is not running. Make sure the code deploy agent is running:
sudo service codedeploy-agent status