Troubleshooting AWS CodeStar Notifications and AWS CodeStar Connections identity and access - Developer Tools console

Troubleshooting AWS CodeStar Notifications and AWS CodeStar Connections identity and access

Use the following information to help you diagnose and fix common issues that you might encounter when working with notifications and IAM.

I want to view my access keys

After you create your IAM user access keys, you can view your access key ID at any time. However, you can't view your secret access key again. If you lose your secret key, you must create a new access key pair.

Access keys consist of two parts: an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access key (for example, wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY). Like a user name and password, you must use both the access key ID and secret access key together to authenticate your requests. Manage your access keys as securely as you do your user name and password.


Do not provide your access keys to a third party, even to help find your canonical user ID. By doing this, you might give someone permanent access to your account.

When you create an access key pair, you are prompted to save the access key ID and secret access key in a secure location. The secret access key is available only at the time you create it. If you lose your secret access key, you must add new access keys to your IAM user. You can have a maximum of two access keys. If you already have two, you must delete one key pair before creating a new one. To view instructions, see Managing access keys in the IAM User Guide.

I'm an administrator and want to allow others to access notifications

To allow others to access AWS CodeStar Notifications and AWS CodeStar Connections, you must create an IAM entity (user or role) for the person or application that needs access. They will use the credentials for that entity to access AWS. You must then attach a policy to the entity that grants them the correct permissions in AWS CodeStar Notifications and AWS CodeStar Connections.

To get started right away, see Creating your first IAM delegated user and group in the IAM User Guide.

For AWS CodeStar Notifications specific information, see Permissions and examples for AWS CodeStar Notifications.

I created an Amazon SNS topic and added it as a notification rule target, but I am not receiving emails about events

In order to receive notifications about events, you must have a valid Amazon SNS topic subscribed as a target for the notification rule, and your email address must be subscribed to the Amazon SNS topic. To troubleshoot problems with the Amazon SNS topic, check the following:

  • Make sure that the Amazon SNS topic is in the same AWS Region as the notification rule.

  • Check to make sure that your email alias is subscribed to the correct topic, and that you have confirmed the subscription. For more information, see Subscribing an endpoint to an Amazon SNS topic.

  • Verify that the topic policy has been modified to allow AWS CodeStar Notifications to push notifications to that topic. The topic policy should include a statement similar to the following:

    { "Sid": "AWSCodeStarNotifications_publish", "Effect": "Allow", "Principal": { "Service": [ "" ] }, "Action": "SNS:Publish", "Resource": "arn:aws:sns:us-east-1:123456789012:MyNotificationTopicName", "Condition": { "StringEquals": { "aws:SourceAccount": "123456789012" } } }

    For more information, see Setting up.

I want to allow people outside of my AWS account to access my AWS CodeStar Notifications and AWS CodeStar Connections resources

You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.

To learn more, consult the following: